BSN.Cloud offers a robust set of permissions features that allow you to protect your content and maintain the efficiency of your digital signage system—no matter how large it gets. These security features are scalable: you can choose exactly how complex you want your permissions system to be depending on the needs of your organization.
This page is an overview of the BSN.Cloud permissions system. Aspects of the system are described in more depth on these child pages:
System and Custom Roles
Image 1 shows both System and Custom Roles and the permissions granted to them. The permissions granted to System Roles are not editable and are updated automatically as BrightSign adds new features to bsn.Content. Custom Roles have no permissions by default, but you can grant full control under some operations by entity or you can expand the roles in the table to grant more granular permissions. For example, you can give Presentation (Full Control) permissions to a content publishing role but ensure that they cannot delete presentations by unchecking Delete Presentations.
Operations Permissions Structure and States
bsn.Content operations are organized in a tree structure that lets parent permissions be either inherited or overridden on child operations in the BrightAuthor:connected Admin > Roles page. You must be logged into BSN.Cloud to view this page.
Operation permissions states are:
Active checkbox with a check: Permissions have been granted for this operation
Active checkbox with a dash: Some permissions have been granted for this operation category
Grey checkbox with a check: Permissions have been granted for this operation and are not editable
Grey checkbox with a dash: Some permissions have been granted for the child operations in this category and are not editable
Grey checkbox without a check: Permissions have not been granted for this operation and are not editable
No check at all: Permissions have not been granted for this operation
Operation and Object Permissions
Operation permissions affect all entities of a given type, but have lower priority than object permissions. They are useful for defining a baseline security policy which then can be adjusted by more granular object permissions.
Object permissions are accessible in the object Properties (under Security). For example, you can select the Network, Content, or Presentations tab, chose a player, content, or presentation, and view or change the permissions as shown in Image 2.
