- Release Notes and Announcements
- Announcements
- Price Adjustment of Global SMS in Certain Countries/Regions on September 1, 2024
- Price Adjustment of Global SMS in Certain Countries/Regions
- Optimization of Tencent Cloud SMS Template Types
- SMSes in Malaysia prohibited from containing URLs, phone numbers and requests for personal numbers
- Prohibition on Sending Non-compliant Messages
- Adjustment of Calculation Rule for Global SMS Message Length
- Price Adjustment of Global SMS
- Announcements
- Product Introduction
- Review Standards
- Global SMS
- Console Guide
- Practical Tutorial
- API Documentation
- SDK Documentation
- FAQ
- Service Agreement
- Contact Us
- Release Notes and Announcements
- Announcements
- Price Adjustment of Global SMS in Certain Countries/Regions on September 1, 2024
- Price Adjustment of Global SMS in Certain Countries/Regions
- Optimization of Tencent Cloud SMS Template Types
- SMSes in Malaysia prohibited from containing URLs, phone numbers and requests for personal numbers
- Prohibition on Sending Non-compliant Messages
- Adjustment of Calculation Rule for Global SMS Message Length
- Price Adjustment of Global SMS
- Announcements
- Product Introduction
- Review Standards
- Global SMS
- Console Guide
- Practical Tutorial
- API Documentation
- SDK Documentation
- FAQ
- Service Agreement
- Contact Us
Note:
This document describes the access management feature of SMS. For more information on access management for other Tencent Cloud services, please see CAM-Enabled Products.
SMS access management essentially binds sub-accounts to policies or grants policies to sub-accounts. You can use default policies directly in the console to implement some simple authorization operations. For more complicated authorization operations, please see Custom Policies.
Currently, SMS provides the following default policies:
Policy Name | Description |
QcloudSMSFullAccess | Full access permission |
QcloudSMSReadonlyAccess | Read-Only access permission |
Default Policy Use Cases
Creating sub-accounts with full access permission
1. Access the User List page in the CAM Console using the Tencent Cloud root account and click Create User.
2. On the "Create User" page, select Custom Creation to enter the "Create Sub-user" page.
Note:
3. On the "User Permissions" page:
3.1 Search for and select the default policy
QcloudSMSFullAccess.3.2 Click Next.
4. Click Complete in the "Review" column. After the sub-user is created successfully, download the login link and security credentials as shown below and keep them private.
Information | Source | Description | Storage Required |
Login link | Copy it on the page | Makes it easier to log in to the console without having to enter the root account | No |
Username | Security credential file in CSV format | Needed for console login | Yes |
Password | Security credential file in CSV format | Needed for console login | Yes |
SecretId | Security credential file in CSV format | Needed for calling server APIs. For more information, please see "Access Key" | Yes |
SecretKey | Security credential file in CSV format | Needed for calling server APIs. For more information, please see "Access Key" | Yes |
5. With the above login link and security credentials, you can use this sub-user to perform all operations in SMS (such as accessing the SMS console and calling SMS server APIs).
Granting Existing Sub-account Full Access to SMS
1. Access the User List in the CAM console using a Tencent Cloud root account and click the target sub-account.
2. Click Add Policy under the "Permissions" tab on the "User Details" page. If the permission of a sub-account is not empty, click Associate Policy.
3. Click Select policies from the policy list, search for and check the preset policy
QcloudSMSFullAccess, and complete the authorization as prompted.Removing a Sub-account’s Full Access to SMS
1. Access the User List in the CAM console using a Tencent Cloud root account and click the target sub-account.
2. Find the preset policy
QcloudSMSFullAccess under the "Permissions" tab on the "User Details" page, click Disassociate on the right, and complete deauthorization as prompted.
Yes
No
Was this page helpful?