What roles and allowed actions are
Within the Aruba Cloud Management Platform, one or more roles can be assigned to each management user. Each role determines the set of allowed actions that the user can perform on resources (for example, viewing, creating, or modifying services).
The scope to which these actions apply (
Folder >
Project >
Region) is defined separately through the configuration of
permissions, which specify where the user can operate.
What they are for
Roles and allowed actions are used to precisely control who can do what within the Aruba Cloud Management Platform, avoiding unnecessary access or unwanted actions. They allow you to delegate operational or read-only activities securely, while maintaining control over the infrastructure.
Available roles
The available roles for management users are:
- Editor: can view and modify resources, but not manage users or configurations.
- Viewer: can only view resources, without making changes.
What each role can do
The roles that can be assigned to a management user can be of two types:
- operational on elements: Editor and Viewer;
- administrative / management: Audit, Global, IAM, ReportDisponibilità.
The following table summarizes the actions allowed on the individual resource/service:
| Operations |
Editor |
Viewer |
| Service creation |
● |
— |
| Service modification |
● |
— |
| Service deletion |
● |
— |
| Viewing the list of services |
● |
● |
| Viewing the details of a service |
● |
● |
The following table summarizes the available roles and the related resource:
| role |
allows you to |
| Global |
have full powers over all resources and includes Audit, IAM and ReportDisponibilità. |
| IAM |
have full access to user management and assigned roles;
to function correctly it is necessary to set ALL for Folder, Project and Region. |
| Audit |
view the activity log. |
| Report Availability |
view the SLA report and performance. |
ResourceName
[e.g. PublicCloud.DBaaS] |
have the Editor role on the specified element. |
ResourceName_Viewer
[ex. PublicCloud.DBaaS_Viewer] |
have the Viewer role on the specified element. |
How they are assigned
The role is assigned during the
creation of the management user or can be updated later, if the user making the change has the appropriate permissions. It is possible to assign multiple roles to the same user, across folders and projects.
What permissions are
Permissions determine on which resources (
Folder >
Project >
Region) a management user can apply the actions allowed by their role.
For example, a user with the
Editor role can modify resources, but only within the resources for which they have permissions
Permissions are configured during user creation and can be
updated at any time by a user with the appropriate rights.