docs: consolidated RBAC docs (accuracy fixes, transition guide, dynamic-auth OAuth)#658
Draft
jordanc-relevanceai wants to merge 4 commits into
Draft
docs: consolidated RBAC docs (accuracy fixes, transition guide, dynamic-auth OAuth)#658jordanc-relevanceai wants to merge 4 commits into
jordanc-relevanceai wants to merge 4 commits into
Conversation
Non-admin team members can now add their own OAuth accounts when dynamic authentication is enabled on a shared agent. Update user-level-authentication.mdx to clarify this capability in the setup section, first-time auth flow, privacy section, and a new FAQ entry. Update rbac.mdx permissions table and add a note distinguishing project-level OAuth management (admin-only) from personal OAuth for dynamic auth (all members). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
This was referenced Jun 3, 2026
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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 the open RBAC documentation work. Opened as draft for review before the source PRs are closed.
Source PRs (being closed in favor of this one)
Why consolidated
All three edit
enterprise/rbac.mdx. Shipping them separately would mean each merge conflicts with the next and the permissions tables / role descriptions drift. #606 already reconciled the two RBAC-accuracy PRs; folding #593 in here keeps the permissions table and role notes coherent in a single pass.Changes by source PR
#606 — TSP-1150 + TSP-1152
admin/project-management/add-members.mdx— adds the Chat role accordion, simplifies the Viewer description (removes the incorrect "can run agents" claim), reframes the Info banner to link both the RBAC docs and the transition guide.enterprise/rbac.mdx— Editor/Viewer/asset-visibility clarifying callouts, plus three new sections: Transitioning to RBAC, Permission inheritance and cascading, and Technical implementation notes.#593 — TSP-1169
enterprise/rbac.mdx— adds an "Add personal OAuth accounts (dynamic auth)" row to the project-level permissions table (all roles ✅) and a note distinguishing project-level OAuth management (admin-only) from personal OAuth for dynamic auth (all members).enterprise/user-level-authentication.mdx— Info callout, updated first-time auth steps, privacy paragraph, and a new FAQ entry documenting that non-admin members can add their own OAuth accounts when dynamic auth is enabled.Reconciliation note
No conflicts between the two — #593's permissions-table row and note land inside the existing Project-level section, while #606's additions are separate sections. Verified no duplicate headings or table rows in the merged
rbac.mdx.