docs(rbac): consolidated RBAC fixes and transition guide#606
Draft
jordanc-relevanceai wants to merge 1 commit into
Draft
docs(rbac): consolidated RBAC fixes and transition guide#606jordanc-relevanceai wants to merge 1 commit into
jordanc-relevanceai wants to merge 1 commit into
Conversation
Combines two drafter PRs that both modify add-members.mdx and enterprise/rbac.mdx: - TSP-1150 (#583): correct inaccuracies — adds Chat role to add-members, simplifies Viewer accordion, adds clarifying callouts about Editor scoping, Viewer access scope, and asset-level visibility, and adds "Permission inheritance and cascading" + "Technical implementation notes" sections - TSP-1152 (#586): adds the "Transitioning to RBAC" section covering what changes during migration, role mapping, and admin action items Reconciled the Info banner at the top of add-members.mdx so both PRs' framing co-exists: the page now describes itself as the standard permission system for orgs not yet migrated to RBAC, with links to both the RBAC docs and the transition guide.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
jordanc-relevanceai
changed the title
This was referenced May 5, 2026
|
|
||
| <Info> | ||
| This page covers adding members to projects and organizations. If you're on an Enterprise subscription and want to learn about Role-Based Access Controls (RBAC) with more granular permissions, see our [RBAC documentation](https://relevanceai.com/docs/enterprise/rbac). | ||
| This page describes the standard permission system used by organizations that have not yet migrated to RBAC. If your organization has RBAC enabled, see [Role-based access controls (RBAC)](/enterprise/rbac) for the current permission model and the [transition guide](/enterprise/rbac#transitioning-to-rbac) for what changes during migration. |
Collaborator
Author
There was a problem hiding this comment.
don't change this line - leave it as is.
| ### User roles | ||
|
|
||
| Members in your organization can be assigned the following roles: Admin, Editor and Viewer. These roles determine what they can do inside of the platform, and what they can do when using the API. | ||
| Members in your organization can be assigned the following roles: Admin, Editor, Chat, and Viewer. These roles determine what they can do inside of the platform, and what they can do when using the API. |
Collaborator
Author
There was a problem hiding this comment.
leave this as it was - Chat is not a general role type
| </Accordion> | ||
| <Accordion title="Chat" icon="message" iconType="duotone"> | ||
| Access [Relevance Chat](/get-started/chat/introduction) only — cannot access the web app. Requires asset-level permissions to run specific agents. | ||
| </Accordion> |
Collaborator
Author
There was a problem hiding this comment.
REMOVE
| **Other permissions:** | ||
|
|
||
| - Can run agents. | ||
| View agents, tools, and knowledge outputs only. Cannot run agents, create assets, or edit anything. |
Collaborator
Author
There was a problem hiding this comment.
Fact check this against the codebase - is this a real change?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR consolidates 2 drafter PRs that all modify the RBAC docs. Each section below is the original description from a source PR. Opening as draft for review before closing the source PRs.
Source PRs (kept open until confirmed)
Files touched
admin/project-management/add-members.mdx— adds Chat role accordion, simplifies the Viewer description, and reframes the existing Info banner so it links to both the RBAC docs and the transition guideenterprise/rbac.mdx— adds clarifying callouts (Editor scoping, Viewer access, asset visibility), plus three new H2 sections: "Transitioning to RBAC", "Permission inheritance and cascading", and "Technical implementation notes"Reconciliation note
Both PRs edit the same two files. #586 frames the legacy page as describing only Admin/Editor/Viewer; #583 adds Chat to that same page. Reconciled the framing in one pass so the docs don't ship two contradicting messages.
#583 — docs(TSP-1150): fix critical RBAC permission inaccuracies
Summary
add-members.mdx: removes the false "Can run agents" claim from the Viewer roleadd-members.mdx(was entirely absent from the page)enterprise/rbac.mdx: view-only, cannot run or editadd-members.mdxto the full RBAC reference pageIn
enterprise/rbac.mdx:Context
Customer confusion traced to two root causes:
add-members.mdxViewer role incorrectly stated Viewers can run agents (they cannot —can_triggerrequires operator/Member minimum)Fixes: https://linear.app/relevance/issue/TSP-1150/
Test plan
add-members.mdxViewer accordion no longer mentions running agentsadd-members.mdx/enterprise/rbac#586 — docs(TSP-1152): add RBAC transition guide and legacy permissions note
Summary
enterprise/rbac.mdxcovering:admin/project-management/add-members.mdxdirecting RBAC-enabled orgs to the RBAC docsTest plan
/enterprise/rbacresolves/get-started/chat/introduction,/enterprise/rbac) are validLinear: https://linear.app/relevance/issue/TSP-1152/
Linear