🏔️ Summit 2026 Feature
Admins now have targeted control over who can add or edit each entity.
🏗️ Provisional document
This feature is pending release, and this document may change over time. Check What’s New for the latest releases.
Entities help organize structured data that belongs on a record, such as scholarships, notes, assignments, or other repeatable information. Entity permissions add a dedicated write permission for each entity, so an admin can control who can create or edit that entity without relying only on broad record-update access.
When a user has the required write permission, they can add and edit instances of the entity. When they do not have the permission, Slate hides the option to add a new entity instance and opens existing instances in a read-only view.

With entity permissions, you can:
Store scholarship review data in an entity, with the scholarship committee able to add and update scholarship records. Other admissions staff can view the information, but can’t change it.
Record advising interventions in an entity, allowing advisors with the intervention permission to add new entries, while other staff can review the history in read-only mode.

Track stewardship assignments in an entity, with staff who manage stewardship able to update assignments while fundraisers view the assignments on the record without editing them.
Adding a write permission to an entity
Go to Database → Entities.
Select the entity you want to restrict.
In the permission settings, select the standard or custom permission that should be required to edit the entity.
Save the entity.
Test the entity from a user account with the permission and a user account without the permission.
.png?sv=2026-02-06&spr=https&st=2026-06-24T21%3A49%3A38Z&se=2026-06-24T22%3A00%3A38Z&sr=c&sp=r&sig=klFLjXXPhhnxuVwQwltXSGGIZZ6hIu8hdaJlw3xLJkU%3D)
Make an entity table read-only on a form
Admins can also make an entity table read-only in a specific form context. This is helpful when the form should display entity information but should not be used to update it, even by users who normally have access to edit the entity elsewhere.
Open the form that contains the entity table.
Edit the entity table field or widget.
Under Options, select the Read only.
Save and test the form.
In the below example, we set the Scholarships - Entity - Scholarship widget form to Read only.

Then, we take a look at that widget on a person record as a user who has write permissions to the widget. We see they can no longer add nor edit the rows on the entity table:
