...
This page is an overview of the BSN.Cloud permissions system. System Roles, Custom Roles, and Object Permissions Aspects of the system are described in more depth on these child pages:
...
System and
...
You can view operations and object permissions while logged into BSN.Cloud.
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:
...
Custom Roles
Each user must have a role. When you create a user, you must specify that role but you can change the role later. All bsn.Control and bsn.Content networks have the same System Roles: there are two in bsn.Control and six in bsn.Content. These roles are maintained by us and updated during BSN.Cloud releases. Each System Role has a set of operations permissions and their main purpose is to represent different job responsibilities within a company. If the default set of roles does not cover your needs, you can add Custom Roles, as described in Custom Roles and then manage their permissions as shown in the image below.
You must be a bsn.Content user to view this page. It is available in under the Admin tab in the Roles section.
...
Image 1 shows a table where each row represents operations that users can execute in bsn.Content. Each operation is associated with one specific entity type (for example, Content or Presentation), on the first level you can see Full Control operations and when expanding the rows, you can find the child operations linked to them. System and Custom Roles are shown in the columns. You can choose which System Roles to display, or delete Custom Roles by clicking the gear button and choosing Delete Role.
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 permissionscopy permissions from any existing role and adjust them for your needs. In order to edit Custom Role permissions, you can expand the rows of this table to find the specific operation you are looking for. Each time you click on a checkbox in the main area, a system creates a new permission for an operation in that current row and a role in that current column. When the checkbox is set, members of the current role are given permission to execute that operation. When the checkbox is unchecked, the permission to execute that operation is denied. Both allowing and denying permissions are inherited by child from the parent operation and may be overridden. 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.
When reviewing the check boxes in the main area, you may notice the following statuses:
Active checkbox with a check means that permission has been granted for this operation
Active checkbox with a dash means that some permissions have been granted for child operations but not this operation
Grey checkbox with a check means that permission have been granted for this operation and are not editable
Grey checkbox with a dash means that some permissions have been granted for the child operations and are not editable
Grey checkbox without a check means that permission is denied for this operation and this cannot be changed
No check at all means that permission is denied for this operation
| Note |
|---|
Unfortunately Player Activation, Setup Package, and Provisioning cannot be controlled by user permissions. This means that any user, regardless of their role, will be able to see all setup packages, create and manage provisions, and register players. If this is not appropriate for your needs, consider creating separate networks for users who should not share this functionality. |
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.
...
To get more information about object permission management, see Object Permissions.