Application Roles

Access to the Blueprint application and all features are controlled by Application Roles. These are positive based permissions in the sense that an explicit permission has to be given in order to provide access. As a key example there is a ‘System Access’ permission and if a user has not been granted this permission they will be unable to access Blueprint.

Roles sit at a lower level than Feature Enablement. For example if you have the permission for ‘Archive Documents’ but the ‘Archive’ feature is disabled then you be unable to Archive Documents.

Any features within the application that you do not have the permission to access will be hidden from view.

Creating a Role

From the Application Roles page you will have the ability to ‘Add’ new roles to the application. These roles require a role ‘Name’ and for individuals or groups (populated directly from your Azure Entra ID) to be assigned.

Once the Role name and individuals/groups have been selected you will have a selection of permissions to assign. These are split across four categories:

• Documents

• Knowledge Bundles

• System

• User

Individuals and Groups can be assigned to multiple Roles and will receive all permissions assigned to them over all Roles that they are party to.