After creating a sub-user/collaborator, you can click Username on the User List management page in the CAM console to disable or enable the console access for the current user in User Details.
Note:
The sub-user/collaborator denied access to the console will not be able to log in to the Tencent Cloud console with the current account, but they can still log in to the Tencent Cloud console with their own accounts; in other words, access grant/revocation by the current account does not affect their use of their own Tencent Cloud account.
Your API key represents your account identity and granted permissions, which is equivalent to your login password. Do not disclose it to others.
Step 3. Authorize a sub-user/collaborator
Grant access to CMS services
CAM allows you to grant sub-users/collaborators the access permissions of specific CMS services. It can be combined with access method authorization (console/API access) for refined permission management.
Policy authorization process
1. Log in to the console with the root account or a sub-user/collaborator with admin permissions and enter the User List page.
2. On the User List page, select the target sub-user/collaborator and click Authorize to pop up the Associate Policy page.
3. On the Associate Policy page, configure the access permissions of CMS services for the sub-user/collaborator as needed.
Note:
Currently, you can configure full access/read-only access to the AMS, VM, IMS, and TMS services under CMS.
4. Click OK.
Description of CAM policies for CMS services
The preset policies for CMS services are as listed below:
Service
Preset Policies
Permission Description
TMS
QcloudTMSFullAccess
Full access
QcloudTMSReadOnlyAccess
Read-Only access
IMS
QcloudIMSFullAccess
Full access
QcloudIMSFullAccess
Read-Only access
AMS
QcloudAMSFullAccess
Full access
QcloudAMSReadOnlyAccess
Read-Only access
VM
QcloudVMFullAccess
Full access
QcloudVMReadOnlyAccess
Read-Only access
Note:
The above preset policies can be used to associate different access permissions of the corresponding CMS services with a sub-user/collaborator. After you assign a preset policy to a sub-user/collaborator as instructed in Authorization Management, the sub-user/collaborator can access or use the corresponding service according to the permissions granted by the policy.
Notes
By default, a root account is the resource owner and has full access to all resources under it, while a sub-user/collaborator does not have access to any resources. A resource creator does not automatically possess the access to the created resource and should be authorized by the resource owner instead.
A policy is a syntax rule that defines and describes one or more permissions. There are two policy types: preset policy and custom policy.
Note:
A preset policy is a set of common permissions that are frequently used by users, such as super admin and full resource access. Preset policies cover a wide range of operation objects at a coarse operation granularity. They are preset by the system and cannot be edited by users.
A custom policy is a set of user-defined permissions that describes resource management in a more refined way. It allows fine-grained permission division and can flexibly meet your differentiated permission management needs.
You can set user permissions by selecting a policy in the policy list for association, reusing the existing user policy, or adding the user to a group to get the permissions of the group.
CAM needs to be properly configured and continuously managed to maximize its value. For the security suggestions on the configuration and management of CAM, see Security Setting Policy.
Yes
No
Was this page helpful?