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.
...
An editable permission for a specific principal, entity, or business operation has an enabled/disabled active colored toggle switch and a "remove" button.
For example, a custom Content Managers role and with allowing/denying permission to execute just the Content - View Content operation under the selected Media File
An editable permission for a specific principal, entity, or parent business operation has an enabled/disabled active colored toggle switch but without the "remove" button.
For example, a custom Content Managers role and with allowing/denying permission to execute the Content (Full Control) operation under the selected Media File. In this case, the permission to execute the Content - View Content business operation is inherited from Content (Full Control).
An editable permission is defined for a specific principal, parent entity. These permissions are displayed with enabled/disabled active but the toggle switch is grey and does not have a "remove" button.
For example, you created a custom Content Managers role and granted an allowing/denying permission has allow/deny permissions to execute any business operation under any new content folder. In this case the permissions to execute all business operations under all content folders and media files down the hierarchy These permissions are inherited from the parent content folder and are displayed with enabled/disabled active but grey toggle switch without the "remove" button.
An editable permission is defined for a parent principal.
For example, you created a custom Content Managers role and granted an allowing/denying permission has allow/deny permissions to execute any business operation under any new content folder or media file. Then If you assign a new user to this role and view his permissions. In this case their permissions, the permissions to execute all business operations under all content folders (except of his personal folder) and media files are inherited from his their role and are displayed with enabled/disabled active but grey toggle switch without the "remove" button, as in the previous case.
Permission is If permissions are defined for this or a parent principal, business operation, or parent entity and is are not editable (has '[bool] IsFixed' flag set). These are permissions defined for System Roles, Personal Folders, Special Groups, etc. They must , they will be displayed with enabled/disabled but inactive and a grey toggle switch without the "remove" button. I think the mouse cursor also should be changing to denying icon when it is over the toggle switch.
These are permissions defined for System Roles, Personal Folders, Special Groups, etc.
If permission is permissions are not defined for the a parent principal, business operation, or parent entity., the toggle switch is disabled and grey. There is no "remove" button.
For example, if you have An example would be a role with incompletely defined permissions and a user who doesn't extend and override them.
...