---
title: "Entity Permissions"
slug: "entity-permissions"
updated: 2026-07-01T16:40:38Z
published: 2026-07-01T16:40:38Z
canonical: "knowledge.technolutions.net/entity-permissions"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Entity Permissions

> [!TIP]
> 🏔️ Summit 2026 Feature
> 
> Admins now have targeted control over who can add or edit each entity.

[Entities](/v1/docs/merged-lifecycle-article-procedure) 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.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Set an entity's write permissions.png?sv=2026-02-06&spr=https&st=2026-11-11T15%3A59%3A48Z&se=2026-11-11T16%3A59%3A48Z&sr=c&sp=r&sig=GiOGdfrvt9d6B%2FtkWoFq4JoBC2Q8%2F4FURqWglvjYdHQ%3D)

With entity permissions, you can:

**Admissions 🪪**

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.

**Student Success 🎓**

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.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Advising notes entity with permission set.png?sv=2026-02-06&spr=https&st=2026-11-11T15%3A59%3A48Z&se=2026-11-11T16%3A59%3A48Z&sr=c&sp=r&sig=GiOGdfrvt9d6B%2FtkWoFq4JoBC2Q8%2F4FURqWglvjYdHQ%3D)

**Advancement 🤝**

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

1. Go to **Database** → **Entities**.
2. Select the entity you want to restrict.
3. In the permission settings, select the standard or custom permission that should be required to edit the entity.
4. Save the entity.
5. Test the entity from a user account with the permission and a user account without the permission.

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Example of users with and without entity write permission(1).png?sv=2026-02-06&spr=https&st=2026-11-11T15%3A59%3A48Z&se=2026-11-11T16%3A59%3A48Z&sr=c&sp=r&sig=GiOGdfrvt9d6B%2FtkWoFq4JoBC2Q8%2F4FURqWglvjYdHQ%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.

1. Open the form that contains the entity table.
2. Edit the entity table field or widget.
3. Under **Options**, select the **Read only**.
4. Save and test the form.

In the below example, we set the **Scholarships - Entity - Scholarship** widget form to *Read only.*

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Setting widget form field to Read Only.png?sv=2026-02-06&spr=https&st=2026-11-11T15%3A59%3A48Z&se=2026-11-11T16%3A59%3A48Z&sr=c&sp=r&sig=GiOGdfrvt9d6B%2FtkWoFq4JoBC2Q8%2F4FURqWglvjYdHQ%3D)

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:

![](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/Effect of read-only setting on user who otherwise has write permissions to entity.png?sv=2026-02-06&spr=https&st=2026-11-11T15%3A59%3A48Z&se=2026-11-11T16%3A59%3A48Z&sr=c&sp=r&sig=GiOGdfrvt9d6B%2FtkWoFq4JoBC2Q8%2F4FURqWglvjYdHQ%3D)