This article will provide you with an overview of entities permissions.
Entity permissions in Ironclad closely mirror Repository permissions and are tied to a group's access to records. These permissions determine how users interact with entities across workflows and records, and whether or not users can view/edit/create entities on the the Entities tab. Currently, permissions can only be configured by entity type—per-entity permissions for entities are not supported.
Configure Entity Permissions
Admins can manage entity permissions by navigating to Company Settings > Groups > Configure Group. Based on the selected permission level, users can view, select, or manage entities, with granular options available for specific entity types. In the Repository and Entities section, select from the following:
| Permission | Impact |
|---|---|
| No access to Repository or entities | The group will not be able to view the Entities tab. |
| Use in workflows, contracts, and contract relationships | The group access for entities will be set to “no access”. |
| View-only access to all Record types and entity types (current and future) | This group will be able to view Entities in the Entities tab, but cannot edit/create/import entities. Users in this group can also use entities in contracts, workflows, and records. |
| View, edit, and create access to all Record types and entity types (current and future) | This group will be able to view, edit, and create entities in the Entities tab. |
| Choose access rights for specific records, record types, and entity types | When you select this option, you can define what level of access the group will have for each entity type. For each entity relationship type and for “entities without a type,” the user can choose either:
Below the dropdown, there is an Allow users to upload and create new contracts and entities of any type checkbox you can toggle on to allow users to create entities of any type. |