- Print
- PDF
Managing API Workflow permissions
- Print
- PDF
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 API Workflow. Sub Account provides System Managed policies and User Created policies for setting management and administration permissions.
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 API Workflow. The following is a brief description about System Managed policies of API Workflow.
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_API_WORKFLOW_MANAGER | Permission to use all features of API Workflow |
NCP_API_WORKFLOW_VIEWER | Permission to only use the View list and Search features of API Workflow |
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 API Workflow.
Type | Action Name | Related action(s) | Resource type | Group by resource type | Action Description |
---|---|---|---|---|---|
View | View/getApiTemplateList | - | - | API Template | View API template |
View | View/getWorkflowList | - | - | Workflow | View workflow |
View | View/getWorkflowDetail | View/getWorkflowList | Workflow | Workflow | View workflow details |
View | View/getAuthorityList | - | - | Authority | View authority |
Change | Change/createApiTemplate | View/getApiTemplateList | - | API Template | Create API template |
Change | Change/updateApiTemplate | View/getApiTemplateList | - | API Template | Modify API template |
Change | Change/deleteApiTemplate | View/getApiTemplateList | - | API Template | Delete API template |
Change | Change/createWorkflow | View/getWorkflowList View/getWorkflowDetail | - | Workflow | Create workflow |
Change | Change/updateWorkflow | View/getWorkflowList View/getWorkflowDetail | Workflow | Workflow | Modify workflow |
Change | Change/deleteWorkflow | View/getWorkflowList View/getWorkflowDetail | Workflow | Workflow | Delete workflow |
Change | Change/createAuthority | View/getAuthorityList | - | Authority | Create authority |
Change | Change/updateAuthority | View/getAuthorityList | Authority | Authority | Modify authority |
Change | Change/deleteAuthority | View/getAuthorityList | Authority | Authority | Delete authority |
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.