...
System and 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.
...
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.
...