Manage access to Secrets Manager
Access to Secrets Manager is governed by:
- projects — define access within an isolated group of resources;
- roles — define access of control panel users, service users, and groups within an account and a project.
Access within projects
All secrets in Secrets Manager are added to a specific project. You can group secrets by different projects and configure user permissions based on which projects they need access to.
Access within roles
Access to Secrets Manager is granted by Secrets Manager roles and global roles. For more information about role types, see the Role reference guide.
Secrets Manager roles
secrets.admin
The secrets.admin role gives access to managing secrets in Secrets Manager.
secrets.viewer
The secrets.viewer role gives access to viewing everything managed by secrets.admin.
secrets.consumer
The secrets.consumer role gives access to viewing and using secrets in Secrets Manager.
Global roles
member
The member role gives full access to all services. Does not give access to managing control panel users, service users, user groups, and federations.
iam.admin
The iam.admin role gives access to managing users and does not give access to managing the product and billing. It does not allow managing your own account: changing permissions, managing notifications, deleting the user. The first user with the iam.admin role is created by the Account Owner.
iam.viewer
The iam.viewer role gives access to viewing everything managed by iam.admin.
reader
The reader role gives access to viewing everything managed by member in the same scope.