Role reference
A role is a set of permitted operations on specific resource types.
Roles are assigned within permissions. The scope of a role is defined by the access scope specified in the permission; for more details, see the General Information on Access Management in Selectel Products guide.
Some roles can only be assigned within a specific access scope and may have different sets of managed resources across different access scopes.
Depending on the resources and settings they provide access to, roles are divided into:
- global roles — define access to resources of all products within the selected access scope (except for products that do not support access management), as well as to account, billing, and access settings;
- and product roles — define access to resources of one or more products within the selected access scope. They do not allow managing other products, account settings, billing, or accesses.
Full access to account and resource management, as well as exclusive permissions, is held by the Account Owner — the user who registered the account. The Account Owner status is not a role and cannot be changed or assigned to anyone.
List of roles
Global roles
member
The member role provides full access to managing all products and resources. It does not have access to managing panel users, service users, user groups, or federations.
billing
The billing role provides access to billing management without access to service management.
iam.admin
The iam.admin role provides access to user management without access to services and billing. It cannot manage its own account: change permissions, manage notifications, or delete the user. The first user with the iam.admin role can only be created by the Account Owner.
iam.viewer
The iam.viewer role provides viewing access to everything managed by iam.admin.
reader
The reader role provides access to view everything managed by member within the same access scope.
Audit_logs roles
audit_logs.admin
The audit_logs.admin role grants access to audit logs; learn more in the instructions Manage access to audit logs.
Certificates roles
certificates.admin
The certificates.admin role grants access to manage certificates in Certificates Manager; learn more in the instructions Manage access to Certificates Manager.
certificates.viewer
The certificates.viewer role grants access to view everything managed by certificates.admin; learn more in the instructions Manage access to Certificates Manager.
certificates.consumer
The certificates.consumer role grants access to view and use certificates in Certificates Manager; learn more in the instructions Manage access to Certificates Manager.
Compute roles
compute.admin
The compute.admin role provides management access to:
- cloud servers and flavors; for more information, see the instructions Manage access to cloud servers and flavors;
- placement groups; for more information, see the instructions Manage access to cloud server placement groups.
* Managing cloud servers additionally requires a role with access to managing cloud platform networks.
compute.viewer
The compute.viewer role grants view access to everything managed by compute.admin.
compute.server.user
The compute.server.user role grants access to manage cloud servers; learn more in the instructions Manage access to cloud servers and flavors.
* Managing cloud servers additionally requires a role with access to manage cloud platform networks, network disks, images, and backups.
compute.server.viewer
The compute.server.viewer role grants permission to view everything managed by compute.server.user.
compute.flavor.admin
The compute.flavor.admin role grants access to manage cloud server flavors; for details, see Manage access to cloud servers and flavors.
compute.flavor.viewer
The compute.flavor.viewer role grants access to view everything managed by compute.flavor.admin.
compute.server_group.admin
The compute.server_group.admin role grants access to manage cloud server placement groups; for details, see Manage access to cloud server placement groups.
compute.server_group.viewer
The compute.server_group.viewer role grants access to view everything managed by compute.server_group.admin.
compute.volume.admin
The compute.volume.admin role grants access to manage cloud server network disks; for details, see Manage access to cloud server network disks and snapshots.
compute.volume.user
The compute.volume.user role grants access to manage cloud server network disks; for details, see the Manage access to cloud server network disks and snapshots guide.
compute.volume.viewer
The compute.volume.viewer role grants access to view everything managed by compute.volume.user.
compute.snapshot.admin
The compute.snapshot.admin role grants access to manage network disk snapshots; for details, see the Manage access to cloud server network disks and snapshots guide.
compute.snapshot.viewer
The compute.snapshot.viewer role grants permission to view everything managed by compute.snapshot.admin.
compute.image.admin
The compute.image.admin role grants access to image management and image sharing configuration; learn more in the instructions Manage access to cloud server images.
compute.image.user
The compute.image.user role grants access to image management; learn more in the instructions Manage access to cloud server images.
compute.backup.admin
The compute.backup.admin role grants access to manage network disk backups and backup plans; learn more in the instructions Manage access to cloud server network disk backups.
compute.backup.viewer
The compute.backup.viewer role grants access to view everything managed by compute.backup.admin.
Dedicated roles
dedicated.admin
The dedicated.admin role grants access to manage:
- dedicated servers, for more details see the Manage access to dedicated servers guide;
- colocated equipment, for more details see the Manage access to colocated equipment guide;
- firewalls, for more details see the Manage access to firewalls guide;
- basic firewall, for more details see the Manage access to basic firewall guide;
- data storage system, for more details see the Manage access to DSS guide;
- network disks for dedicated servers, for more details see the Manage access to network disks guide;
- rented network equipment, for more details see the Manage access to rented network equipment.
dedicated.viewer
A user with permission to view everything managed by dedicated.admin in the same access scope.
Filestorage roles
filestorage.admin
The filestorage.admin role grants access to manage file storage; learn more in the instructions Manage access to file storage.
* Working with file storage additionally requires a role with access to managing cloud platform networks to connect the file storage network.
filestorage.viewer
The filestorage.viewer role grants view access to everything managed by filestorage.admin.
Global_router roles
global_router.admin
The global_router.admin role grants access to manage global routers in the account; for details, see the Manage access to global router guide.
* Managing network connections to the global router additionally requires the member role in the Project or Account access scope.
global_router.viewer
The global_router.viewer role grants access to view everything managed by global_router.admin.
Go1c roles
go1c.admin
The go1c.admin role grants access to manage 1C Ready Cloud resources; for details, see the Manage access to 1C Ready Cloud guide.
* To manage the connection of backup storage, cluster data storage, and uploading an infobase from a .dt file, you also need the combination of the s3.admin and iam.admin roles.
** To manage connecting the cluster to a private network already created in the project, you additionally need the vpc.private_network.viewer role.
go1c.viewer
The go1c.viewer role grants view access to everything managed by go1c.admin; for details, see Manage access to Managed 1C Cloud.
Logs roles
logs.admin
The logs.admin role grants access to manage logs; for details, see Manage access to logs.
logs.writer
The logs.writer role grants access to add logs to the Logs service; for details, see Manage access to logs.
logs.viewer
The logs.viewer role grants access to view logs; for details, see Manage access to logs.
Metrics roles
metrics.admin
The metrics.admin role grants access to manage metrics; for details, see Manage access to metrics.
Mobile_farm roles
mobile_farm.admin
The mobile_farm.admin role grants access to manage Mobile Farm in your project; for details, see the instructions on managing Mobile Farm access.
mobile_farm.user
The mobile_farm.user role grants access to use mobile farm devices in your project. For more details, see the Manage access to the mobile farm guide.
mobile_farm.viewer
The mobile_farm.viewer role grants access to view everything managed by mobile_farm.admin.
Secrets roles
secrets.admin
The secrets.admin role grants access to manage secrets in Secrets Manager; for details, see the Manage access to Secrets Manager guide.
secrets.viewer
The secrets.viewer role grants view access to everything managed by secrets.admin; for details, see Manage access to Secrets Manager.
secrets.consumer
The secrets.consumer role grants access to view and use secrets in Secrets Manager; for details, see Manage access to Secrets Manager.
s3, data_migration, and object_storage roles
s3.admin
The s3.admin role grants access to manage S3 within the project; for details, see the Manage access to S3 guide.
s3.user
The s3.user role grants access to viewing the list of buckets in a project and managing an S3 bucket, provided that an access policy is configured in the bucket that allows this user access to the bucket. For more details, see the Managing access in S3 guide. The level of access to the bucket is determined by the access policy settings. If no access policy is created, the user has no access to the bucket.
Differs from the user with the s3.bucket.user role only in that they have access to view the list of buckets in the project.
s3.bucket.user
The s3.bucket.user role grants access to an S3 bucket, provided that an access policy is configured in the bucket that allows this user access to the bucket. For more details, see the Managing access in S3 guide. The level of access to the bucket is determined by the access policy settings. If no access policy is created, the user has no access to the bucket.
Differs from the user with the s3.user role only in that they do not have access to view the list of buckets in the project.
data_migration.admin
The data_migration.admin role provides access to managing migrations in S3. For more information, see the Managing access to S3 guide.
data_migration.user
The data_migration.user role provides access to viewing created migrations in S3 and managing their execution. For more information, see the Managing access to S3 guide.
data_migration.viewer
The data_migration.viewer role grants access to view everything managed by data_migration.admin; learn more in the instructions Manage access in S3.
object_storage:admin
The object_storage:admin role will be deprecated soon and cannot be assigned to new users. Existing users with the object_storage:admin role can continue working.
Legacy version of the s3.admin role. It has identical permissions.
object_storage_user
The object_storage_user role will be deprecated soon and cannot be assigned to new users. Existing users with the object_storage_user role can continue working.
Legacy version of the s3.user role. It has identical permissions.
VPC roles
vpc.admin
The vpc.admin role provides access to manage:
- cloud platform networks (private networks and subnets, public subnets and public IP addresses, cloud routers), for more details see the guide Manage access to cloud platform networks;
- cloud firewalls, for more details see the guide Manage access to cloud firewalls;
- security groups, for more details see the guide Manage access to security groups;
- cloud load balancers, for more details see the guide Manage access to cloud load balancers.
Adding ports to a cloud server and deleting ports added to a cloud server are not available; this requires the compute.admin or compute.server.user role.
* To manage the connection of a subnet to the global router, the global_router.admin role is additionally required.
vpc.viewer
The vpc.viewer role grants view access to everything managed by vpc.admin in the same scope.
vpc.private_network.admin
The vpc.private_network.admin role grants access to manage:
- cloud platform networks (private networks, subnets, and ports); for details, see the Manage access to cloud platform networks guide;
- private DNS, for more details see the Manage access to private DNS guide.
Adding ports to a cloud server and removing ports added to a cloud server are not available; this requires the member role.
* Managing subnet connection to a cloud router additionally requires the vpc.external_access.admin role. Connecting to a global router requires the global_router.admin role.
vpc.private_network.viewer
The vpc.private_network.viewer role provides access to view everything managed by vpc.private_network.admin in the same access scope.
vpc.external_access.admin
The vpc.external_access.admin role grants access to managing internet access objects, such as public subnets, direct public IP addresses, public floating IP addresses, and cloud routers. For more details, see the guide Managing access to cloud platform networks.
Adding ports to a cloud server and deleting ports added to a cloud server are not available; this requires the compute.admin or compute.server.user role.
* Managing the connection of a private subnet to a cloud router additionally requires the vpc.private_network.admin role.
vpc.external_access.user
The vpc.external_access.user role provides access:
- to view everything managed by vpc.external_access.admin in the same access scope;
- to manage public floating IP addresses; for more details, see the instructions on Managing access to cloud platform networks.
Adding ports to a cloud server and deleting ports added to a cloud server are not available; the compute.admin or compute.server.user role is required for this.
vpc.external_access.viewer
The vpc.external_access.viewer role grants permission to view everything managed by vpc.external_access.admin within the same access scope.
vpc.network_security.admin
The vpc.network_security.admin role grants permission to manage traffic restriction tools:
- cloud firewalls, for details see the Manage access to cloud firewall guide;
- security groups, for details see the Manage access to security groups guide.
* To view security groups and manage port assignments, the vpc.private_network.viewer or vpc.external_access.viewer role is additionally required.
** To download the report, a combination of the vpc.private_network.viewer and vpc.external_access.viewer roles, or the vpc.viewer role, is additionally required.
vpc.network_security.user
The vpc.network_security.user role grants access:
- to view everything managed by vpc.network_security.admin within the same access scope;
- to manage security group ports in a private or public network; for more information, see the Manage access to security groups guide.
* Downloading the report additionally requires a combination of the vpc.private_network.viewer and vpc.external_access.viewer roles, or the vpc.viewer role.
vpc.network_security.viewer
The vpc.network_security.viewer role grants access to view everything managed by vpc.network_security.admin within the same access scope.
* Downloading the report additionally requires a combination of the vpc.private_network.viewer and vpc.external_access.viewer roles, or the vpc.viewer role.
vpc.load_balancer.admin
The vpc.load_balancer.admin role grants access to manage the cloud load balancer; learn more in the instructions Manage access to the cloud load balancer.
* Creating a load balancer additionally requires one or more roles. Additional roles depend on the network where the load balancer will be created:
- vpc.admin for creating a load balancer in any subnet;
- vpc.private_network.admin for creating a load balancer in a private subnet;
- vpc.external_access.admin for creating a load balancer in a public subnet;
- a combination of the vpc.private_network.admin and vpc.external_access.admin roles for creating a load balancer in a private subnet with a public IP address;
vpc.load_balancer.viewer
The vpc.load_balancer.viewer role grants access to view everything managed by vpc.load_balancer.admin within the same access scope.