Page Comparison

...

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 additional roles with custom permissions.

Role and user access can be in one of the following states:

...

• An editable permission is defined for this specific principal, parent entity.

  • For example, you created a custom Content Managers role and granted an 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 are displayed with enabled/disabled active but grey toggle switch without the "remove" button

• An editable permission is defined for the parent principal.

  • For example, you created a custom Content Managers role and granted an 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 are displayed with enabled/disabled active but grey toggle switch without the "remove" button, as in the 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 the parent Principal, neither this nor parent Business Operation, neither this nor parent Entity. This is possible in case when you have a Role principal, business operation, or parent entity.

  • For example, if you have a role with incompletely defined permissions and a user

  which

  • who doesn't extend and override them.

  Such

  • This state

  must be

  • is represented

  with

  • by a disabled active grey toggle switch and without the "remove" button.
    

Permissions

You can view operations and object permissions while logged into BSN.Cloud. All business operations defined in bsn.Content are organized into a tree structure, where permission granted to the parent operation may be inherited or overridden on the child. To review the complete set of business operations, open BrightAuthor:connected and go to the Admin > Roles page.

...