Manage access to cloud servers and flavors
Access to cloud servers and flavors is regulated by a role model that defines access within an account and a project. For more information, see the Access management in Selectel products instructions.
member
A user with full access to all services. Has no access to managing: users, service users, user groups, and federations.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
reader
A user with access to view everything managed by member in the same scope.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
billing
A user with access to billing management and no access to service management.
| Access scopes | Account |
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers |
|
iam.admin
A user with access to user management and without access to services and billing. Cannot manage their own account: change permissions, manage notifications, or delete the user. The first user with the iam.admin role is created by the Account Owner.
| Access scopes | Account |
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors |
|
iam.viewer
A user with access to view everything managed by iam.admin.
| Access scopes | Account |
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors |
|
compute.admin
User with access to manage cloud servers, flavors, and placement groups. Does not have access to other products.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
* In addition to the compute.admin role, the user must have a role with access to managing cloud platform networks.
compute.viewer
User with access to view cloud servers, flavors, and placement groups. Does not have access to other products.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
compute.server.user
User with access to manage cloud servers. Does not have access to other products.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
* In addition to the compute.server.user role, the user must have a role with access to managing cloud platform networks, network drives, images, and backups.
compute.server.viewer
User with access to view cloud servers. Does not have access to other products.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
compute.flavor.admin
User with access to manage cloud server flavors. Does not have access to other products.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|
compute.flavor.viewer
User with access to view cloud server flavors. Does not have access to other products.
| Access scopes |
|
|---|---|
| Who can be assigned |
|
| Available operations with cloud servers and flavors | In the Account access scope:
|
In the Project access scope:
|