Improvements to managing access and permissions of Service Accounts
Great news! Based on customer feedback, we've made improvements to how you manage access and permissions for Service Accounts, improving their usability and extending the capabilities of what a Service Account can do.
What's changed?
With this release, there are two key feature improvements.
First, Service Accounts can now be assigned a manager role for an organization, allowing that Service Account to perform organizational actions, such as creating and updating repositories, allocating user and team permissions on those repositories, creating and deleting teams, and more.
Second, Service Accounts can now be explicitly granted repository access without needing to be added to a team first. While granting a Service Account access to a repository, you will also specify the permission level for that Service Account for that particular repository.
Service Accounts via the API
In addition to the feature improvements described above, we've also extended the Cloudsmith API to support managing Services within your organization. We've added a Services endpoint, and Services are now also supported within the Repository Access Controls API.
Learn more about these types of requests in our API documentation.
As always, we would love to hear your feedback. We hope these improvements make Service Accounts more functional and usable for you.