RelevanceAI · claude · May 12, 2026
diff --git a/build/knowledge/create-knowledge.mdx b/build/knowledge/create-knowledge.mdx
@@ -186,6 +186,12 @@ To maintain effective knowledge bases over time:
 6. **Quality Control**: Implement validation processes for new knowledge entries
 7. **Scalable Structure**: Design your knowledge organization to accommodate growth
 
+## Access control
+
+Data tables support fine-grained access control for Enterprise teams. Project admins can configure each table as private (invite-only) or open to all project members at a specified role, and can grant access to individual users or groups. The three roles are Admin, Operator (read/write), and Viewer (read-only).
+
+For full details, see [Data table permissions](/enterprise/rbac#data-table-permissions).
+
 ## Related Features
 
 - [Access Knowledge](https://relevanceai.com/docs/build/knowledge/access-knowledge): Learn how to configure how your agents and tools access and use your knowledge bases.

diff --git a/enterprise/rbac-groups.mdx b/enterprise/rbac-groups.mdx
@@ -87,7 +87,7 @@
 ### Adding groups to projects

 <div style={{ width:"100%",position:"relative","padding-top":"56.75%" }}>
 <iframe src="https://app.supademo.com/embed/cmhebwgnb3mp9fatip57eyru5" frameBorder="0" title="Add groups to projects" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />
 </div>

 To add a group to a project:
@@ -105,14 +105,14 @@
 
 ![Adding Groups to Assets](/images/rbac-groups/asset-groups.png)
 
-Groups can also be assigned directly to individual assets (agents, tools, knowledge bases, or workforces). This provides granular control over who can access and use specific resources.
+Groups can also be assigned directly to individual assets (agents, tools, knowledge bases, data tables, or workforces). This provides granular control over who can access and use specific resources.
 
 When adding a group to an asset, you'll assign them an [asset-level role](/enterprise/rbac#asset-level-controls) (Admin, Member, or Viewer) which determines their permissions for that specific asset.
 
 ### Adding groups to assets

 <div style={{ width:"100%",position:"relative","padding-top":"56.75%" }}>
 <iframe src="https://app.supademo.com/embed/cmheca16f3myjfatigr1f7k31" frameBorder="0" title="Add groups to assets" allow="clipboard-write; fullscreen" webkitAllowFullscreen="true" mozAllowFullscreen="true" allowFullscreen style={{ position:"absolute",top:0,left:0,width:"100%",height:"100%",border:"3px solid #5E43CE",borderRadius:"10px" }} />
 </div>

 To add a group to an asset:

diff --git a/enterprise/rbac.mdx b/enterprise/rbac.mdx
@@ -32,7 +32,7 @@

 ### Project Level

 - **Admins** — own the project setup and governance. They control permission and authentication accounts.
 - **Editors** — build, edit, and run all assets in the project. Treat them as your core contributors.
 - **Members** — can build their own assets but don't automatically see or edit others'. Great for independent work within shared projects.
 - **Chat** — access [Relevance Chat](/get-started/chat/introduction) only, cannot access the web app. Perfect for users who only need to interact with agents through chat. Requires asset-level permissions to run specific agents.
@@ -154,7 +154,7 @@
 
 ## Asset level controls
 
-An asset is an Agent, Tool, Knowledge or Workforce.
+An asset is an Agent, Tool, Knowledge, Data Table, or Workforce.
 
 Upon asset creation, the creator becomes the admin. An asset can have multiple admins (project admin is by default).
 
@@ -211,6 +211,51 @@
 
 ----
 
+## Data table permissions
+
+Data tables (also called entity tables) support fine-grained access control using the same three-tier permission system as other assets. Project admins control both the default visibility of each table and which users or groups can access it.
+
+### Table access configuration
+
+Each data table can be set to one of two access modes:
+
+- **Private (invite-only)** — only users explicitly granted a role on the table can view or modify it. This is the default for tables created by project Members.
+- **Open to project members** — all project members are granted access at a specified role (Admin, Operator, or Viewer). Project Admins and Editors have full access by default.
+
+### Roles
+
+| **Role**     | **Capabilities**                                                 |
+| ------------ | ---------------------------------------------------------------- |
+| **Admin**    | Manage table schema, configuration, and assign table-level users |
+| **Operator** | Read and write data in the table                                 |
+| **Viewer**   | View table data only, cannot modify records or configuration     |
+
+### Permissions
+
+| **Permission**              | **Admin** | **Operator** | **Viewer** |
+| :-------------------------- | :-------- | :----------- | :--------- |
+| Edit table schema           | ✅         | ❌            | ❌          |
+| Delete table                | ✅         | ❌            | ❌          |
+| Assign roles on table       | ✅         | ❌            | ❌          |
+| Configure table access mode | ✅         | ❌            | ❌          |
+| Insert, update, or delete rows | ✅      | ✅            | ❌          |
+| View table data             | ✅         | ✅            | ✅          |
+
+### Granting access to a data table
+
+Permissions can be granted to individual users or groups. To configure access:
+
+1. Open the data table you want to share.
+2. Click **Share**.
+3. Set the access mode (private or open to project members).
+4. To grant access to specific users or groups, enter their name or email and select a role.
+
+<Tip>
+Use the Operator role for team members who need to read and write records, and Viewer for stakeholders who only need to review the data.
+</Tip>
+
+----
+
 ## Frequently asked questions (FAQs)
 
 <AccordionGroup>