Permission Set for the Repository Model
Unlock secure, role-based access and advanced management for your entire integration landscape with the Repository Model permission set in Nodinite. This guide empowers integration experts and administrators to control who can view, create, or modify key repository entities—ensuring compliance, security, and operational efficiency.
✅ Granular, role-based access control for all repository entities
✅ Empower users with self-service options while maintaining security
✅ Advanced features: view, create, and modify integrations, systems, services, and more
✅ Flexible permission inheritance and global settings
The following permissions exist for the Repository Model permission set:
Visual overview: Permission relationships for the Repository Model in Nodinite
Set permissions on Roles. The values for a permission are as follows:
- Inherited – Default (not allowed unless the end-user is part of another Role where this grant is set).
Note
Not allowed is NOT the same as Deny! It means the inheritance chain is honored.
- 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 wins. Since entities are assigned to Roles, you should rarely need to use Deny. Instead, consider removing the entity from the Roles.
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 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.
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, end-users in Roles with the Access Integrations permission can view information about Integrations. A Nodinite Administrator can manage the following permissions:
Example: Managing the Integrations permissions for Role.
Systems
In the Web Client, end-users in Roles with the Access Systems permission can view information about Systems. A Nodinite Administrator can manage the following permissions:
Example: Managing the Systems permissions for Role.
Services
In the Web Client, end-users in Roles with the Access Services permission can view information about Services. A Nodinite Administrator can manage the following permissions:
Example: Managing the Services permissions for Role.
Contracts
In the Web Client, end-users in Roles with the Access Contracts permission can view information about Contracts. A Nodinite Administrator can manage the following permissions:
Example: 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, end-users in Roles with the Access Message Types permission can view information about Message Types. A Nodinite Administrator can manage the following permissions:
Example: Managing the Message Types permissions for Role.
Endpoints
In the Web Client, end-users in Roles with the Access Endpoints permission can view information about Endpoints. A Nodinite Administrator can manage the following permissions:
Example: Managing the Endpoints permissions for Role.
Articles
In the Web Client, end-users in Roles with the Access Articles permission can view information about Articles. A Nodinite Administrator can manage the following permissions:
Example: Managing the Articles permissions for Role.
Custom Fields
In the Web Client, end-users in Roles with the Access Custom Fields permission can view information about Custom Fields. A Nodinite Administrator can manage the following permissions:
Example: Managing the Custom Fields permissions for Role.
Custom Metadata
In the Web Client, end-users in Roles with the Access Custom Metadata permission can view information about Custom Metadata. A Nodinite Administrator can manage the following permissions:
Example: 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