Managing CLOVA AiCall permissions
- Print
- PDF
Managing CLOVA AiCall permissions
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
The latest service changes have not yet been reflected in this content. We will update the content as soon as possible. Please refer to the Korean version for information on the latest updates.
Available in Classic and VPC
By using Sub Account, which is NAVER Cloud Platform's account management service, you can set various access permissions for CLOVA AiCall. Sub Account provides System Managed policies and User Created policies for setting management and administration permissions.
Note
The Sub Account service is provided free of charge upon subscription request. For more information on Sub Account, refer to the Service > Management & Governance > Sub Account menu in the NAVER Cloud Platform portal, as well as the Sub Account Guide.
System Managed policies
System Managed policies are role-based policies defined by NAVER Cloud Platform for user convenience. Once System Managed policies are granted to a sub account created in Sub Account, that sub account can use CLOVA AiCall. The following is a brief description about System Managed policies of CLOVA AiCall.
| Policy Name | Policy Description |
|---|---|
| NCP_ADMINISTRATOR | Permission to access the portal and console in NAVER Cloud Platform in the same manner as main accounts |
| NCP_INFRA_MANAGER | Permission to use all services in NAVER Cloud Platform and access My Page > Manage notifications in the portal |
| NCP_CLOVA_AI_CALL_MANAGER | Permission to use all features of CLOVA AiCall |
| NCP_CLOVA_AI_CALL_VIEWER | Permission to only use the View List and Search features in CLOVA AiCall |
User-defined policy
User-defined policies are policies that users can create. Once User-defined policies are granted to a sub account created in Sub Account, that sub account can only use the user-assigned action combinations. The following is a brief description about User-defined policies of CLOVA AiCall.
| Type | Action Name | Related action(s) | Resource type | Group by resource type | Action Description |
|---|---|---|---|---|---|
| View | View/executeBuilder | View/getContactCenterList | ContactCenter | ContactCenter | Execute contact center builder |
| View | View/getContactCenterDetail | View/getContactCenterList | ContactCenter | ContactCenter | View contact center details |
| View | View/getContactCenterList | - | * | ContactCenter | View contact center list |
| View | View/getContactCenterUsage | View/getContactCenterList | ContactCenter | ContactCenter | View contact center usage |
| Change | Change/createContactCenter | View/getContactCenterList | * | ContactCenter | Create contact center |
| Change | Change/deleteContactCenter | View/getContactCenterList | ContactCenter | ContactCenter | Delete contact center |
| Change | Change/subscribeProduct | - | * | * | Request or cancel subscription to CLOVA AiCall |
| Change | Change/updateContactCenter | View/getContactCenterDetail View/getContactCenterList | ContactCenter | ContactCenter | Modify contact center |
Caution
Even when you are granted permission for a specific action, if you are not also granted permissions for the related actions that are required, then you won't be able to perform jobs properly. To prevent such issues, Sub Account provides a feature that automatically grants permissions for related actions when granting action permissions. However, if you deselect related actions that are automatically granted, then the system determines that it was done intentionally by the main account user and won't forcibly include them. So, be careful when setting permissions.
Was this article helpful?