Visibility

Manage the visibility of your content by specifying the regions or audiences authorized to access it, ensuring compliance with licensing agreements and target audience restrictions.

About Visibility

BlendVision One offers three privacy levels for viewing content: Public, Password, and Token. These privacy tiers ensure that users have control over who can access their content, providing options for different levels of security based on their needs.

Public

This is the most accessible level. Viewers can access the content without any requests for information, whether they're using an iframe, showroom, or other methods.

Password

This level offers a light layer of protection. Users are required to set a password for their upcoming live events. The password must be between 8 to 20 characters long. This protection is available via iframe, SDK, or Showroom.

When selecting this option, ensuring the text input is filled before saving is important. All viewers will use the same password and be prompted to enter it before viewing the content.

Token

This level offers a more secure protection mechanism. Users must request a token delivered via API integration when embedding an iframe. If a user hosts an event via Showroom, viewers will be asked for a redeem code when logging in.

The number of concurrent devices per token should be set and checked when saving the event. When setting up the showroom, users can generate a certain number of redeem codes, up to 1000.

Set Visibility

The privacy object is a required field that specifies the visibility of your content. The following table represents the attributes of privacy settings:

Field	Type	Required	Description
type	string	Yes	Indicates the security privacy type. Allowed values: SECURITY_PRIVACY_TYPE_PUBLIC SECURITY_PRIVACY_TYPE_TOKEN Default:SECURITY_PRIVACY_TYPE_PUBLIC
token	object	Optional	Required if the type is SECURITY_PRIVACY_TYPE_TOKEN

To make the content become private, you can enable privacy control to protect your content using redeem codes by setting the type field in the privacy object to SECURITY_PRIVACY_TYPE_TOKEN and specifying the number of device limitations to the device_limit field in the token object.

Here's an example of the request body that sets the privacy type to token-based and limits the number of devices that can access the content to 100.

"privacy":{
  "type":"SECURITY_PRIVACY_TYPE_TOKEN",
  "token":{
    "device_limit":100
  }
}