B2B PRISM Live Studio resource management
- Print
- PDF
B2B PRISM Live Studio resource management
- Print
- PDF
Article Summary
Share feedback
Thanks for sharing your feedback!
Available in Classic and VPC
Check the resource information of B2B PRISM Live Studio. All activities that you can perform in B2B PRISM Live Studio are mapped with the resource type and task history by resource type (action) defined in Resource Manager. Based on the value mapped, the task history actually performed by users is collected in Cloud Activity Tracer, and the admin can use it when monitoring the users' activities or creating audit reports. In addition, the resource type is used as a standard for usage permissions by user in Sub Account.
The description of the resource and task history by resource type is as follows:
- Resource
- Unit of key information managed by each service
- Object that can be created, changed, and deleted by the user
- Unique value by each service of NAVER Cloud Platform
- Task history by resource type (action)
- History of tasks performed by the user through the console and API
- Act of creating, changing, or deleting resources
The description of B2B PRISM Live Studio's resource type and task history information by resource type is as follows:
Service name (product code) | Resource type | Task history by resource type |
---|---|---|
B2B PRISM Live Studio(PrismLiveStudio) | Service | Block Channel |
Create Channel | ||
Create Service | ||
Delete Service | ||
Download Channel Log | ||
Download Service Log | ||
Off Service | ||
On Service | ||
Paid Service | ||
Unblock Channel | ||
Update Service |
Note
- Resource Manager: it is a service provided by NAVER Cloud Platform for free. For more information on how to use the service, see the Resource Manager user guide.
- Cloud Activity Tracer: it is a service provided by NAVER Cloud Platform for free. For more information on how to use the service, see the Cloud Activity Tracer user guide.
- Sub Account: it is a service provided by NAVER Cloud Platform for free. The permissions are designed based on the resource type defined in Resource Manager. However, because the resource type group and the action by resource type are configured in Sub Account, they differ from the group and action values defined in Resource Manager.
Was this article helpful?