Skip to main content

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

Role groupList of rolesManaged resources
Global rolesmemberAll products, account, billing, projects
billingBilling
iam.adminAccess settings
iam.viewerView access settings only
readerAll products, account, billing, projects (view only)
audit_logsaudit_logs.adminAudit logs
certificatesSecrets manager
compute
  • cloud servers and flavors;
  • cloud server placement groups;
  • cloud server network volumes and snapshots;
  • cloud server images;
  • cloud server network volume backups
dedicated
  • dedicated servers;
  • colocation;
  • firewalls;
  • basic firewall;
  • storage system;
  • network volumes for dedicated servers;
  • rented network equipment
filestorageFile storage
global_routerGlobal router
go1cCloud for 1C
logsLogs
metricsmetrics.adminMetrics
mobile_farmMobile Farm
secretsSecrets manager
s3, data_migration, and object_storageS3
vpc
  • cloud platform networks;
  • cloud firewalls;
  • security groups;
  • cloud load balancers;
  • private DNS

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.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • management of projects, their limits, and quotas;
  • billing management;
  • resource management in all projects;
  • resource management outside of projects;
  • working with audit logs

In the Project access scope:

  • management of resources of the selected project

billing

The billing role provides access to billing management without access to service management.

Access scopesAccount
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations
  • Billing management:

    • balance top-ups and transferring funds between balances;
    • management of autobills, monthly payments, payment deferrals;
    • balance notification management;
    • bank card management;
    • viewing reporting documents;
    • partner program and payout management;
  • viewing connected services and service statuses

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.

Access scopesAccount
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations
  • management of users, service users, user groups;
  • federation management;
  • issuing keys to users;
  • managing other users' notifications;
  • configuring account access restrictions

iam.viewer

The iam.viewer role provides viewing access to everything managed by iam.admin.

Access scopesAccount
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations
  • viewing users, service users, user group;
  • viewing federations;
  • viewing user keys;
  • viewing other users' notifications;
  • viewing account access restrictions

reader

The reader role provides access to view everything managed by member within the same access scope.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing resources in all projects, as well as resources that are not attached to a project;
  • viewing settings of all projects, their limits and quotas;
  • viewing billing data (balance, bank cards, report documents, partner program, etc.)

In the Project access scope:

  • viewing resources of the selected project

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.

Access scopes

Account

Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

Exporting 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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • managing custom certificates (adding, updating, deleting) across all projects;
  • managing Let’s Encrypt® certificates (issuing, downloading, deleting) across all projects;
  • managing certificate consumers across all projects;
  • viewing public and private parts of certificates across all projects

In the Project scope:

  • managing custom certificates (adding, updating, deleting) in their project;
  • managing Let’s Encrypt® certificates (issuing, downloading, deleting) in their project;
  • managing certificate consumers (adding, deleting) in their project;
  • viewing public and private parts of certificates in their project

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.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • viewing the list of custom certificates and information about them across all projects;
  • viewing the list of Let’s Encrypt® certificates and information about them across all projects;
  • viewing certificate consumers across all projects;
  • viewing public parts of certificates across all projects

In the Project scope:

  • viewing the list of custom certificates and information about them in your project;
  • viewing the list of Let’s Encrypt® certificates and information about them in your project;
  • viewing certificate consumers in your project;
  • viewing the public parts of certificates in your project

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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of custom certificates and information about them in all projects;
  • viewing the list of Let’s Encrypt® certificates and information about them in all projects;
  • managing certificate consumers in all projects;
  • viewing the public and private parts of certificates in all projects

In the Project access scope:

  • viewing the list of custom certificates and information about them in your project;
  • viewing the list of Let’s Encrypt® certificates and information about them in your project;
  • managing certificate consumers in your project;
  • viewing the public and private parts of certificates in your project

Compute roles

compute.admin

The compute.admin role provides management access to:

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas of all projects (default quotas, modified quota values, and used quotas);
  • managing cloud servers (creation, modification, deletion) * across all projects;
  • using the console;
  • managing flavors (creation, modification, deletion) across all projects;
  • managing SSH keys (adding, deleting) across all projects;
  • managing placement groups (creation, deletion) across all projects

In the Project access scope:

  • viewing project quotas (default quotas, modified quota values, and used quotas);
  • managing cloud servers (creation, modification, deletion) * within your project;
  • using the console;
  • managing flavors (creation of private flavors, modification, deletion) within your project;
  • managing SSH keys (adding, deleting) within your project;
  • managing placement groups (creation, deletion) in your project

* 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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas for all projects (default quotas, modified quota values, and used quotas);
  • viewing the list of cloud servers and information about them (server type, configuration type, number of vCPUs, memory size, attached disks, security groups, network settings, tags) across all projects;
  • viewing statistics for cloud servers across all projects;
  • viewing the list of flavors and information about them (flavor name, number of vCPUs, RAM, and local disk size) across all projects;
  • viewing the list of SSH keys and information about them across all projects;
  • viewing the list of placement groups and information about them (group name, placement policy condition) across all projects

In the Project access scope:

  • viewing project quotas (default quotas, modified quota values, and used quotas);
  • viewing the list of cloud servers and information about them (server type, configuration type, number of vCPUs, memory size, attached disks, security groups, network settings, tags) in your project;
  • viewing statistics for cloud servers in your project;
  • viewing the list of flavors and information about them (flavor name, number of vCPUs, RAM, and local disk size) in your project;
  • viewing the list of SSH keys and information about them in your project;
  • viewing the list of placement groups and their information (group name, placement policy condition) in your project

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.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas of all projects (default quotas, modified quota values, and used quotas);
  • managing cloud servers (creation, modification) * across all projects;
  • using the console;
  • viewing the list of flavors and their information across all projects: flavor name, number of vCPUs, RAM, and local disk size across all projects;
  • managing SSH keys (addition, deletion) across all projects

In the Project access scope:

  • viewing project quotas (default quotas, modified quota values, and used quotas);
  • managing cloud servers (creation, modification) * in your project;
  • using the console;
  • viewing the list of flavors and their information in your project: flavor name, number of vCPUs, RAM, and local disk size;
  • managing SSH keys (addition, deletion) in your project

* 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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas of all projects (default quotas, modified quota values, and used quotas);
  • viewing the list of cloud servers and information about them across all projects: server type, configuration type, number of vCPUs, memory size, attached disks, security groups, network settings, tags;
  • viewing cloud server statistics across all projects;
  • viewing the list of flavors and information about them across all projects: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them across all projects

In the Project access scope:

  • viewing project quotas (default quotas, modified quota values, and used quotas);
  • viewing the list of cloud servers and information about them in your project: server type, configuration type, number of vCPUs, memory size, attached disks, security groups, network settings, tags;
  • viewing cloud server statistics in your project;
  • viewing the list of flavors and information about them in your project: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in your project

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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas of all projects (default quotas) in all projects;
  • managing flavors (creating private flavors, modifying, deleting) in all projects;
  • viewing the list of SSH keys and information about them in all projects

In the Project access scope:

  • viewing project quotas (default quotas) in your project;
  • managing flavors (creating private flavors, modifying, deleting) in your project;
  • viewing the list of SSH keys and information about them in your project

compute.flavor.viewer

The compute.flavor.viewer role grants access to view everything managed by compute.flavor.admin.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas of all projects (default quotas);
  • viewing the list of flavors and information about them in all projects: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in all projects

In the Project access scope:

  • viewing project quotas (default quotas);
  • viewing the list of flavors and information about them in your project: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in your project

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.

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing quotas of all projects (default quotas);
  • managing placement groups (creation, deletion) in all projects;
  • viewing the list of flavors and information about them in all projects: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in all projects

In the Project access scope:

  • viewing project quotas (default quotas) in your project;
  • managing placement groups (creation, deletion) in your project;
  • viewing the list of flavors and information about them in your project: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in your project

compute.server_group.viewer

The compute.server_group.viewer role grants access to view everything managed by compute.server_group.admin.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • retrieving quotas for all projects;
  • viewing the list of placement groups and information about them in all projects: group name, placement policy condition;
  • viewing the list of flavors and information about them in all projects: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in all projects

In the Project access scope:

  • retrieving project quotas;
  • viewing the list of placement groups and information about them in your project: group name, placement policy condition;
  • viewing the list of flavors and information about them in your project: flavor name, number of vCPUs, RAM, and local disk size;
  • viewing the list of SSH keys and information about them in your project

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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • view a list of all network disks and information about them across all projects: disk type, disk size;
  • manage disks (create, modify, delete) across all projects;
  • move disks between projects;
  • view information about disk movement across all projects

In the Project scope:

  • view a list of all network disks and information about them within your project: disk type, disk size;
  • manage disks (create, modify, delete) within your project;
  • transfer disks from your project to another;
  • view information about disk movement within your project

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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing a list of all network disks and information about them (disk type, disk size) in all projects;
  • managing disks (creating, modifying, deleting) in all projects

In the Project access scope:

  • viewing a list of all network disks and information about them (disk type, disk size) in your project;
  • managing disks (creating, modifying, deleting) in your project

compute.volume.viewer

The compute.volume.viewer role grants access to view everything managed by compute.volume.user.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing a list of network disks and information about them (disk type, disk size) in all projects

In the Project access scope:

  • viewing a list of network disks and information about them (disk type, disk size) in your project

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.

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • viewing the list of snapshots and snapshot information (snapshot size, creation date, and status) across all projects;
  • managing snapshots (creation, deletion) across all projects

In the Project scope:

  • viewing the list of snapshots and snapshot information (snapshot size, creation date, and status) within your project;
  • managing snapshots (creation, deletion) within your project

compute.snapshot.viewer

The compute.snapshot.viewer role grants permission to view everything managed by compute.snapshot.admin.

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • viewing the list of snapshots and snapshot information (snapshot size, creation date, and status) across all projects

In the Project access scope:

  • viewing the list of snapshots and their information (snapshot size, creation date, and status) within your project

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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of images and information about them across all projects: image size, image format and container, minimum image requirements;
  • image management (uploading, creation, modification, deletion) across all projects;
  • configuring image sharing in projects from the same account or from other accounts

In the Project access scope:

  • viewing the list of images and information about them in your project: image size, image format and container, minimum image requirements;
  • image management (uploading, creation, modification, deletion) in your project;
  • configuring image sharing in projects from the same account or from other accounts

compute.image.user

The compute.image.user role grants access to image management; learn more in the instructions Manage access to cloud server images.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of images and information about them across all projects: image size, image format and container, minimum image requirements;
  • managing images (uploading, creating, modifying, deleting) across all projects

In the Project access scope:

  • viewing the list of images and information about them in your project: image size, image format and container, minimum image requirements;
  • managing images (uploading, creating, modifying, deleting) in your project

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.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of backups and information about them (backup type, size, connected backup plans, status) across all projects;
  • managing backups (creating, deleting) across all projects;
  • viewing the list of backup plans across all projects;
  • managing backup plans (creating, modifying, deleting) across all projects

In the Project scope:

  • viewing the list of backups and information about them (backup type, size, connected backup plans, status) in your project;
  • managing backups (creating, deleting) in your project;
  • viewing the list of all backup plans in your project;
  • managing backup plans (creating, modifying, deleting) in your project

compute.backup.viewer

The compute.backup.viewer role grants access to view everything managed by compute.backup.admin.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • viewing the list of backups and information about them (backup type, size, connected backup plans, status) across all projects;
  • viewing the list of backup plans across all projects

In the Project scope:

  • viewing the list of backups and information about them (backup type, size, connected backup plans, status) in your project;
  • viewing the list of backup plans in your project

Dedicated roles

dedicated.admin

The dedicated.admin role grants access to manage:

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

Within the Account access scope:

  • viewing the project list;
  • managing dedicated servers (ordering, modifying, canceling) across all projects;
  • managing colocated equipment (ordering, modifying, canceling) across all projects;
  • managing networks;
  • enabling and disabling additional services;
  • viewing the list of SSH keys, adding SSH keys to storage, and managing added SSH keys;
  • managing firewalls (ordering, modifying, canceling);
  • managing network disks (creating, modifying, deleting);
  • managing data storage systems (ordering, modifying, canceling);
  • basic firewall management (creation, modification, deletion);
  • management of leased equipment (ordering, modification, cancellation)

In the Project access scope:

  • management of dedicated servers (ordering, modification, cancellation) within your project;

  • management of collocated equipment (ordering, modification, cancellation) within your project;

  • enabling and disabling additional services;

  • viewing the list of SSH keys added to the storage and information about them;

  • viewing and management are not available for:

    • networks;
    • firewalls;
    • network volumes and storage systems;
    • basic firewall;
    • leased network equipment

dedicated.viewer

A user with permission to view everything managed by dedicated.admin in the same access scope.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of all dedicated servers and information about them in all projects;
  • viewing the list of collocated equipment and information about it in all projects;
  • viewing the list of all VLANs, public and private subnets, SANs, and information about them;
  • viewing the list of network disks and storage devices and information about them;
  • viewing the list of firewalls and information about them;
  • viewing the list of basic firewalls and information about them;
  • viewing the list of leased network equipment and information about it;
  • viewing the list of SSH keys added to the storage and information about them

In the Project access scope:

  • viewing the list of dedicated servers and information about them in your project;

  • viewing the list of collocated equipment and information about it in your project;

  • viewing the list of SSH keys added to the storage and information about them;

  • viewing and management are not available for:

    • networks;
    • network disks and storage systems;
    • firewalls;
    • basic firewall;
    • leased network equipment

Filestorage roles

filestorage.admin

The filestorage.admin role grants access to manage file storage; learn more in the instructions Manage access to file storage.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of file storages and their information across all projects: name, size, storage type and protocol, IP and network name, status;
  • viewing file storage access rules across all projects;
  • creating and managing file storages * across all projects;
  • creating and managing access rules across all projects

In the Project access scope:

  • viewing the list of file storages and their information in your project: name, size, storage type and protocol, IP and network name, status;
  • viewing file storage access rules in your project;
  • creating and managing file storages * in your project;
  • creating and managing access rules in your project

* 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.

Access scopes
  • account;
  • project
Assignees
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of file storages and information about them across all projects: name, size, storage type and protocol, IP and network name, status;
  • viewing file storage access rules across all projects

In the Project scope:

  • viewing the list of file storages and information about them in your project: name, size, storage type and protocol, IP and network name, status;
  • viewing file storage access rules in your project

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.

Access scopesAccount
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations
  • viewing the list of global routers, networks and subnets connected to them, and the list of static routes on the router;
  • managing global routers (creation, modification, deletion);
  • adding, modifying, and deleting static routes on a global router;
  • modifying the names of networks and subnets connected to the global router;
  • connecting an existing or new Cloud Platform network and subnet to the global router *;
  • connecting an existing or new Dedicated Servers network and subnet to the global router *;
  • removing a Cloud Platform network or subnet from the global router's network, including deleting the Cloud Platform network or subnet itself *;
  • removing a Dedicated Servers network or subnet from the global router's network *

* 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.

ScopesAccount
Assignable to
  • users;
  • service users;
  • user groups
Available operationsViewing the list of global routers, connected networks and subnets, and the list of static routes on the router

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.

Scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • managing 1C server clusters in all projects * **;
  • managing infobases in all projects *;
  • managing databases in all projects;
  • managing backups in all projects *;
  • manage Prometheus tokens to collect metrics across all projects

In the Project scope:

  • manage 1C server clusters in your project * **;
  • manage infobases in your project;
  • manage databases in your project *;
  • manage backups in your project *;
  • manage Prometheus tokens to collect metrics in your project

* 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.

Scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account scope:

  • view 1C server clusters in all projects;
  • view infobases in all projects;
  • view databases in all projects;
  • view backups in all projects;
  • view the list of generated Prometheus tokens for collecting metrics across all projects

Within the Project access scope:

  • view 1C server clusters in your project;
  • view databases in your project;
  • view database instances in your project;
  • view backups in your project;
  • view the list of generated Prometheus tokens for collecting metrics in your project

Logs roles

logs.admin

The logs.admin role grants access to manage logs; for details, see Manage access to logs.

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

Within the Account access scope:

  • view logs in the control panel and using available tools across all projects;
  • manage custom logs across all projects;
  • manage log groups and event streams across all projects

Within the Project access scope:

  • view logs in the control panel and using available tools in your project;
  • manage custom logs in your project;
  • manage log groups and event streams in your project

logs.writer

The logs.writer role grants access to add logs to the Logs service; for details, see Manage access to logs.

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • adding logs from a user storage using available tools across all projects;
  • creating log groups and event streams in all projects

In the Project access scope:

  • adding logs from a user storage using available tools within your project;
  • creating log groups and event streams within your project

logs.viewer

The logs.viewer role grants access to view logs; for details, see Manage access to logs.

Access scopes
  • account;
  • project
Assignable to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • view logs in the control panel and using available tools across all projects

In the Project access scope:

  • view logs in the control panel and using available tools within your project

Metrics roles

metrics.admin

The metrics.admin role grants access to manage metrics; for details, see Manage access to metrics.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • collect metrics across all projects

In the Project access scope:

  • collect metrics in your project

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.

Access scopesProject
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations
  • view mobile farm usage in your project;
  • add and remove mobile farm devices in your project;
  • use mobile farm devices in your project;
  • modify mobile farm device pricing plans in your project;
  • add ADB and proxy keys to your profile;
  • modify mobile farm firewall rules

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.

Access scopesProject
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations
  • view mobile farm usage in your project;
  • use mobile farm devices in your project;
  • add ADB and proxy keys to your profile;
  • view mobile farm firewall rules

mobile_farm.viewer

The mobile_farm.viewer role grants access to view everything managed by mobile_farm.admin.

Access scopesProject
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations
  • view mobile farm consumption in your project;
  • view mobile farm devices in your project;
  • add ADB and Proxy keys to your profile;
  • view mobile farm firewall rules

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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • manage secrets (add, delete) across all projects;
  • secret version management (adding, modifying the current version, deleting) across all projects;
  • view secret contents across all projects

In the Project access scope:

  • secret management (adding, deleting) within your project;
  • secret version management (adding, modifying the current version, deleting) within your project;
  • view secret contents within your project

secrets.viewer

The secrets.viewer role grants view access to everything managed by secrets.admin; for details, see Manage access to Secrets Manager.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of secrets and information about them, excluding secret contents, across all projects

In the Project access scope:

  • viewing the list of secrets and information about them, excluding secret contents, within your project

secrets.consumer

The secrets.consumer role grants access to view and use secrets in Secrets Manager; for details, see Manage access to Secrets Manager.

Access scopes
  • account;
  • project
Assignees
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of secrets and information about them across all projects;
  • viewing the contents of secrets across all projects

In the Project access scope:

  • viewing the list of secrets and information about them in your project;
  • viewing the contents of secrets in your project

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.

Access scopesProject
Assignees
  • panel users;
  • service users
Available operations
  • view the list of buckets in your project;
  • view the contents of buckets in your project;
  • manage bucket objects (upload, modify, delete) in your project;
  • change bucket settings in your project;
  • configure the bucket access policy in your project

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.

Access scopesProject
Can be assigned toService users
Available operations
  • view the list of buckets in your project;
  • operations in a specific bucket allowed by its access policy

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.

Access scopesProject
Can be assigned toService users
Available operationsOperations in a specific bucket that are allowed by its access policy

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.

Access scopes
  • account;
  • project
Who can be assigned
  • control panel users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • managing migrations (creation, modification, deletion) across all projects;
  • viewing the list of migrations and information about each migration across all projects;
  • checking connections to source and destination buckets across all projects;
  • managing migration execution (starting, stopping) across all projects

In the Project access scope:

  • managing migrations (creation, modification, deletion) within your project;
  • viewing the list of migrations and information about each migration within your project;
  • checking connections to source and destination buckets within your project;
  • managing migration execution (starting, stopping) within your project

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.

Access scopes
  • account;
  • project
Can be assigned to
  • management console users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of migrations and information about each migration across all projects;
  • checking connections to source buckets and destination buckets across all projects;
  • managing migration execution (start, stop) across all projects

In the Project access scope:

  • viewing the list of migrations and information about each migration within your project;
  • checking connections to source buckets and destination buckets within your project;
  • managing migration execution (start, stop) within your project

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.

Access scopes
  • account;
  • project
Can be assigned to
  • management console users;
  • service users;
  • user groups
Available operations in S3

In the Account access scope:

  • viewing the list of migrations and information about each migration across all projects

In the Project access scope:

  • viewing the list of migrations and information about each migration within your project

object_storage:admin

For your information

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

For your information

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:

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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of:

    • all network resources in the cloud platform and information about them in all projects;
    • all load balancer objects and information about them in all projects: load balancers, rules and HTTP policies, target groups and servers within them, health monitors;
    • cloud firewalls and information about them in all projects;
    • security groups and information about them in all projects;
  • management of private networks, subnets, and ports in all projects *;

  • management of public subnets, direct public IP addresses, and public floating IP addresses in all projects;

  • management of cloud routers in all projects;

  • management of load balancers, rules and HTTP policies, target groups, health monitors, load balancer logging in all projects, as well as viewing load balancer statistics in all projects;

  • management of cloud firewalls in all projects;

  • management of security groups, rules, and ports in all projects, as well as downloading the security group report in all projects

In the Project access scope:

  • viewing the list of:

    • all network resources in the cloud platform and information about them in your project;
    • all load balancer objects and information about them in your project: load balancers, rules and HTTP policies, target groups and servers within them, health monitors;
    • cloud firewalls and information about them in your project;
    • security groups and information about them in your project;
  • management of private networks, subnets, and ports in your project *;

  • management of public subnets, direct public IP addresses, and public floating IP addresses in your project;

  • management of cloud routers in your project;

  • management of load balancers, rules and HTTP policies, target groups, health monitors, load balancer logging in your project, as well as viewing load balancer statistics in your project;

  • management of cloud firewalls in your project;

  • management of security groups, rules, and ports in your project, as well as downloading the security group report in your project

* 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.

Access scopesAccount
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of:

    • all cloud platform network resources and information about them across all projects;
    • cloud firewalls and information about them across all projects;
    • security groups and information about them across all projects;
  • downloading the security group report across all projects

In the Project access scope:

  • viewing the list of:
    • all cloud platform network resources and information about them in your project
    • cloud firewalls and information about them in your project;
    • security groups and information about them in your project;
  • downloading the security group report in your project

vpc.private_network.admin

The vpc.private_network.admin role grants access to manage:

Adding ports to a cloud server and removing ports added to a cloud server are not available; this requires the member role.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing:

    • list of private networks, subnets, ports, and information about them across all projects;
    • information about connecting a network to a private DNS resolver, viewing the list of zones and resource records in zones across all projects;
  • managing private networks, subnets, and ports across all projects *;

  • managing private DNS across all projects

In the Project access scope:

  • viewing:

    • list of private networks, subnets, ports, and information about them in your project;
    • information about connecting a network to a private DNS resolver, viewing the list of zones and resource records in zones in your project;
  • managing private networks, subnets, and ports in your project *;

  • managing private DNS in your project

* 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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of private networks, subnets, ports, and information about them in all projects;
  • viewing information about connecting a network to a private DNS resolver, viewing the list of zones and resource records in zones across all projects

In the Project access scope:

  • viewing the list of private networks, subnets, ports, and information about them within your project;
  • viewing information about connecting a network to a private DNS resolver, viewing the list of zones, resource records, and information about them within your project

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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of public subnets, public IP addresses, ports in public networks, cloud routers, and information about them across all projects;
  • managing public subnets across all projects;
  • managing direct public IP addresses across all projects;
  • managing public floating IP addresses across all projects;
  • managing cloud routers across all projects *

In the Project access scope:

  • viewing the list of public subnets, public IP addresses, ports in public networks, cloud routers, and information about them within your project;
  • managing public subnets within your project;
  • managing direct public IP addresses within your project;
  • managing public floating IP addresses within your project;
  • managing cloud routers within your project *

* 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:

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.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of public subnets, direct public IP addresses and public floating IP addresses, ports in public networks, cloud routers, and information about them across all projects;
  • managing public floating IP addresses, except for creating and deleting public floating IP addresses, across all projects

In the Project access scope:

  • viewing the list of public subnets, direct public IP addresses and public floating IP addresses, ports in public networks, cloud routers, and information about them within your project;
  • managing public floating IP addresses, except for creating and deleting public floating IP addresses, within your project

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.

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of public subnets, direct public IP addresses and public floating IP addresses, ports in public networks, cloud routers, and information about them across all projects

In the Project access scope:

  • viewing the list of public subnets, direct public IP addresses and public floating IP addresses, ports in public networks, cloud routers, and information about them within your project

vpc.network_security.admin

The vpc.network_security.admin role grants permission to manage traffic restriction tools:

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • view list of:

    • cloud firewalls and their information across all projects;
    • security groups and their information across all projects *;
  • management of cloud firewalls across all projects;

  • management of security groups, rules, and ports across all projects *;

  • downloading the security groups report across all projects **

In the Project access scope:

  • view list of:

    • cloud firewalls and their information within your project;
    • security groups and their information within your project *;
  • management of cloud firewalls within your project;

  • management of security groups, rules, and ports within your project *;

  • downloading the security groups report within your project **

* 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:

Access scopes
  • account;
  • project
Who can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of:

    • cloud firewalls and information about them across all projects;
    • security groups and information about them across all projects;
  • managing security group ports across all projects. In the control panel, this action is available for the role only via the security group page (in the top menu, click Products → Cloud servers → Security groups → group page);

  • downloading the security group report across all projects *

In the Project access scope:

  • viewing the list of:

    • cloud firewalls and information about them in your project;
    • security groups and information about them in your project;
  • managing security group ports in your project. In the control panel, this action is available for the role only via the security group page (in the top menu, click Products → Cloud servers → Security groups → group page);

  • downloading the security group report in your project *

* 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.

Access scopes
  • account;
  • project
Can be assigned to
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of:

    • cloud firewalls and information about them across all projects;
    • security groups and information about them across all projects;
  • downloading the security group report across all projects *

In the Project access scope:

  • viewing the list of:

    • cloud firewalls and information about them within your project;
    • security groups and information about them within your project;
  • downloading the security group report within your project *

* 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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of all load balancer objects and information about them across all projects: load balancers, rules and HTTP policies, target groups and servers within them, and health checks;
  • viewing load balancer statistics across all projects;
  • managing load balancer objects across all projects, except for creating a load balancer *;
  • enabling and disabling load balancer logging across all projects

In the Project access scope:

  • viewing the list of all load balancer objects and information about them within your project: load balancers, rules and HTTP policies, target groups and servers within them, and health checks;
  • viewing load balancer statistics within your project;
  • managing load balancer objects within your project, except for creating a load balancer *;
  • enabling and disabling load balancer logging within your project

* Creating a load balancer additionally requires one or more roles. Additional roles depend on the network where the load balancer will be created:

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.

Access scopes
  • account;
  • project
Who can be assigned
  • users;
  • service users;
  • user groups
Available operations

In the Account access scope:

  • viewing the list of all balancer objects and information about them across all projects: load balancers, rules and HTTP policies, target groups and their servers, health checks

In the Project access scope:

  • viewing the list of all balancer objects and information about them in your project: load balancers, rules and HTTP policies, target groups and their servers, health checks