Content Permission Management

BlendVision's Content Permission Management is designed to control access to media streaming content within an organization. It allows administrators to define and manage permissions at granular levels, ensuring that users and groups have appropriate access to Video on Demand (VOD) resources and individual videos.

Roles and Permissions

Understanding the roles and their associated permissions is crucial for effective permission management.

General Roles:

Role	Description
Super Editor	Full control over content, including editing and assigning roles. Default role for organization owners.
Editor	Can edit content and perform limited actions but cannot delete or assign roles.
Viewer	Can only view content without any modification or assignment capabilities.
Limited Access	Restricted access, typically view-only with minimal permissions.

Detailed Permissions:

Permission	Super Editor	Editor	Viewer	Limited Access
View content on the list	✔️	✔️	✔️	❌
Edit content configuration	✔️	✔️	❌	❌
Delete content	✔️	❌	❌	❌
Assign ACL roles to users	✔️	❌	❌	❌
Download mp4 file	✔️	✔️	❌	❌

注記

Organization owners inherently possess the Super Editor role for all content by default, and this cannot be modified.

API Integration

To control the permission of your content, configure the associated API request body during creation or update it later.

• Create: POST /bv/cms/v1/vods

• Update: PUT /bv/cms/v1/vods/:id

Configure the permission request body with the following options:

Permission Object Structure:

Field	Type	Required	Description
default_access_role	string	No	Updates the default access role for the VOD. Possible values: ACCESS_ROLE_DENY, ACCESS_ROLE_SUPER_EDITOR, ACCESS_ROLE_EDITOR, ACCESS_ROLE_VIEWER.
assignments	object[]	No	Array of specific user/group assignments with defined access roles to be added or updated.

Assignments Array Structure: Each object in the assignments array should include:

Field	Type	Required	Description
id	string	Yes	If assigned_type is ASSIGNED_TYPE_USER, this is the user ID. If ASSIGNED_TYPE_GROUP, this is the group ID.
assigned_type	string	Yes	Type of assignment. Possible values: ASSIGNED_TYPE_USER, ASSIGNED_TYPE_GROUP. Cannot be ASSIGNED_TYPE_OWNER.
access_role	string	Yes	Defines the access role. Possible values: ACCESS_ROLE_SUPER_EDITOR, ACCESS_ROLE_EDITOR, ACCESS_ROLE_VIEWER. Cannot be ACCESS_ROLE_DENY.

Here's the sample of request body that assigns the Super Editor role to a user:

{
  "name": "Sample VOD",
  "profile_set_id": "profile_set_123",
  "source": {
    "type": "SOURCE_TYPE_LIBRARY",
    "library": {
      "id": "video_file_456"
    }
  },
  "permission": {
    "default_access_role": "ACCESS_ROLE_EDITOR",
    "assignments": [
      {
        "id": "user_789",
        "assigned_type": "ASSIGNED_TYPE_USER",
        "access_role": "ACCESS_ROLE_SUPER_EDITOR"
      }
    ]
  }
}