Permission Set for the Repository Model
The following permissions exist for the Repository Model permission set:
Set permission on Roles. The values for a permission are the following:
- Inherited - default (which means not allowed, unless the end-user is part of another Role, where this grant is set)
Note
Not allowed is NOT the same thing as a Deny(!) as it merely means; Honour the inheritance chain.
- Allow - Access is granted.
- Deny - The feature is blocked from usage. Use this setting only for special cases.
Note
Regardless of other permission sets, a Deny always win. Since the entities are assigned to the Roles, you should rarely have to use the Deny setting. Instead of denying access, consider removing the entity from the Roles instead.
For the Repository Model, the following operations are managed:
Access (read-only)
If the permission is set to Allow; The end-user has visibility and has read-only rights.
Create
If the permission is set to Allow; The end-user can create new items in the Repository Model for the selected entity.
Modify
If the permission is set to Allow; The end-user can modify existing items in the Repository Model for the selected entity.
Access Repository
To access and manage the Nodinite Repository Model; The User must be a member of a Role granted (Allow) access to the Repository.
Note
If the User is a member of any Roles where access to the Repository is denied (Deny); Then, the user is blocked access to the Repository Model.
The Roles is set to Allow access to the Repository.
If the Roles is denied access to the Nodinite Repository Model; The Repository is not even part of the main menu pane:
Integrations
In the Web Client, for end-users in Roles where the Access Integrations permission is allowed; The end-user is granted the right to view information about Integrations. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Integrations permissions for Role.
Systems
In the Web Client, for end-users in Roles where the Access Systems permission is allowed; The end-user is granted the right to view information about Systems. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Systems permissions for Role.
Services
In the Web Client, for end-users in Roles where the Access Services permission is allowed; The end-user is granted the right to view information about Systems. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Services permissions for Role.
Contracts
In the Web Client, for end-users in Roles where the Access Contracts permission is allowed; The end-user is granted the right to view information about Contracts. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Contracts permissions for Role.
Important
The UseContracts System Parameter must be set to
true; Otherwise, the Contracts feature is disabled.
Message Types
In the Web Client, for end-users in Roles where the Access Message Types permission is allowed; The end-user is granted the right to view information about Message Types. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Message Types permissions for Role.
Endpoints
In the Web Client, for end-users in Roles where the Access Endpoints permission is allowed; The end-user is granted the right to view information about Endpoints. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Endpoints permissions for Role.
Articles
In the Web Client, for end-users in Roles where the Access Articles permission is allowed; The end-user is granted the right to view information about knowledge base Articles. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the knowledge base Articles permissions for Role.
Custom Fields
In the Web Client, for end-users in Roles where the Access Custom Fields permission is allowed; The end-user is granted the right to view information about Custom Fields. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Custom Fields permissions for Role.
Custom Metadata
In the Web Client, for end-users in Roles where the Access Endpoints permission is allowed; The end-user is granted the right to view information about Custom Metadata. A Nodinite Administrator can manage the following permissions:
Here's an example of managing the Custom Metadata permissions for Role.
Next Step
Add or manage Role
Add or manage Log View
Add or manage Monitor View
Repository Model