...
This page describes the BSN.Cloud permissions system and how to use defaultSystem roles. By default, you will see only six predefined system roles having fixed permissions which you cannot edit. A separate Custom Roles page describes how to create a custom role additional roles with custom permissions.
The access of the selected Selected role or user instance access to execute the specific Business Operation under the specific securable Entity a business operation under an entity may be in one of the following states:
Permission Types
...
Permission is defined for this A permission for a specific Principal, Entity, or Business Operation and that is editable. :
For example, you created a custom Content Managers role and granted allowing/denying permission to execute just the Content - View Content business operation under the selected Media File - such permission is displayed with enabled/disabled active colored toggle switch and a "remove" button
Permission is defined for this A permission for a specific Principal, Entity, or parent Business Operation and that is editable. :
For example, you created a custom Content Managers role and granted allowing/denying permission to execute the Content (Full Control) business 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) and is displayed with enabled/disabled active colored toggle switch but without the "remove" button
Color Indicators
...
Permission is defined for this specific Principal, parent Entity and is editable.
For example, you created a custom "Content Managers" Role and granted allowing/denying Permission 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 are inherited from the parent Content Folder and must be displayed with enabled/disabled active but grey toggle switch without the "remove" button
Permission is defined for the parent Principal and is editable.
For example, you created a custom "Content Managers" Role and granted allowing/denying Permission to execute any Business Operation under any new Content Folder or Media File. Then you assign a new User to this Role and view his Permissions. In this case the Permissions to execute all Business Operations under all Content Folders (except of his Personal Folder) and Media Files are inherited from his Role and must be displayed with enabled/disabled active but grey toggle switch without the "remove" button, same as in previous case
Permission is defined for this or parent Principal, this or parent Business Operation, this or parent Entity and is not editable (has '[bool] IsFixed' flag set). These are Permissions defined for System Roles, Personal Folders, Special Groups, etc. They must be displayed with enabled/disabled but inactive and 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
Permission is not defined neither for this nor for parent Principal, neither this nor parent Business Operation, neither this nor parent Entity. This is possible in case when you have a Role with incompletely defined Permissions permissions and a User user which dondoesn't extend and override them. Such state must be represented with disabled active grey toggle switch and without the "remove" button.
...