Permissions Management

If you need to assign different permissions to employees in your enterprise to access your CBR resources on the cloud, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your cloud resources.

With IAM, you can use your cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use CBR resources but should not be allowed to delete the resources or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using CBR resources.

If your cloud account does not require individual IAM users for permissions management, skip this section.

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see Identity and Access Management User Guide.

CBR Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

CBR is a project-level service deployed and accessed in specific physical regions. To assign CBR permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing CBR, the users need to switch to a region where they have been authorized to use this service.

You can grant users permissions by using roles and policies.

Roles: A type of coarse-grained authorization mechanism that defines permissions related to users responsibilities. Only a limited number of service-level roles for authorization are available. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant ECS users only the permissions for managing a certain type of ECSs. Most policies define permissions based on APIs. For the API actions supported by CBR, see "Permissions Policies and Supported Actions".

Table 1 lists all the system-defined roles and policies supported by CBR.

**Table 1** System-defined policies supported by CBR
Policy Name	Description	Type
CBR FullAccess	Administrator permissions for CBR. Users granted these permissions can operate and use all vaults, backups, and policies.	System-defined policy
CBR BackupsAndVaultsFullAccess	Common user permissions for CBR. Users granted these permissions can create, view, and delete vaults and backups, but cannot create, update, or delete policies.	System-defined policy
CBR ReadOnlyAccess	Read-only permissions for CBR. Users granted these permissions can only view CBR data.	System-defined policy

Table 2 lists the common operations supported by each system-defined policy or role of CBR. Select the policies or roles as required.

**Table 2** Common operations supported by each system-defined policy or role of CBR
Operation	CBR FullAccess	CBR BackupsAndVaultsFullAccess	CBR ReadOnlyAccess
Querying vaults	√	√	√
Creating vaults	√	√	×
Listing vaults	√	√	√
Updating vaults	√	√	×
Deleting vaults	√	√	×
Associating resources	√	√	×
Dissociating resources	√	√	×
Creating policies	√	×	×
Updating policies	√	×	×
Applying policies to a vault	√	√	×
Removing policies from a vault	√	√	×
Deleting policies	√	×	×
Performing backups	√	√	×
Updating subscriptions	√	√	×
Querying the Agent status	√	√	×
Deleting backups	√	√	×
Restoring data using backups	√	√	×
Associating vaults	√	√	×
Batch adding or deleting vault tags	√	√	×
Adding vault tags	√	√	×
Editing tags	√	√	×