langchain-ai/docs
1
0
Fork 0
mirror of https://github.com/langchain-ai/docs.git synced 2026-07-22 04:15:25 -04:00
Code Issues 490 Packages Projects Releases Wiki Activity

[PR #3307] [MERGED] fix: clarify organization roles availability by plan type [closes DOC-643] #3364

New Issue
Closed
opened 2026-06-05 18:22:52 -04:00 by yindo · 0 comments
yindo commented 2026-06-05 18:22:52 -04:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langchain-ai/docs/pull/3307
Author: @katmayb
Created: 3/25/2026
Status: ✅ Merged
Merged: 3/25/2026
Merged by: @katmayb

Base: main ← Head: open-swe/0b01a598-78a2-1692-5fb5-714fd7e27379

📝 Commits (2)

  • 7f94bd7 Clarify that Organization User/Viewer roles require Plus or Enterprise plans, and Developer organizations default to Organization Admin
  • aab612f Edits

📊 Changes

3 files changed (+3 additions, -7 deletions)

View changed files

📝 src/langsmith/rbac.mdx (+1 -5)
📝 src/langsmith/set-up-hierarchy.mdx (+1 -1)
📝 src/snippets/langsmith/multi-workspace-org-roles.mdx (+1 -1)

📄 Description

Description

Clarifies organization roles documentation to explicitly state that Organization User and Organization Viewer roles are only available on Plus and Enterprise plans. Replaces vague "plans with multiple workspaces" phrasing with specific plan names and uses "Developer organizations" terminology to explain that single-workspace orgs default to Organization Admin. This addresses user confusion about role availability across plan types.

Resolves DOC-643

Test Plan

  • Verify updated snippet renders correctly on administration-overview page
  • Verify rbac.mdx Note box reads clearly
  • Verify set-up-hierarchy.mdx Info box includes Organization Viewer role mention

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langchain-ai/docs/pull/3307 **Author:** [@katmayb](https://github.com/katmayb) **Created:** 3/25/2026 **Status:** ✅ Merged **Merged:** 3/25/2026 **Merged by:** [@katmayb](https://github.com/katmayb) **Base:** `main` ← **Head:** `open-swe/0b01a598-78a2-1692-5fb5-714fd7e27379` --- ### 📝 Commits (2) - [`7f94bd7`](https://github.com/langchain-ai/docs/commit/7f94bd760b043fda4ded78fe615a7da4cee27ed0) Clarify that Organization User/Viewer roles require Plus or Enterprise plans, and Developer organizations default to Organization Admin - [`aab612f`](https://github.com/langchain-ai/docs/commit/aab612f0a72ed9b1204a202ceb2a627b7e90e4b0) Edits ### 📊 Changes **3 files changed** (+3 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `src/langsmith/rbac.mdx` (+1 -5) 📝 `src/langsmith/set-up-hierarchy.mdx` (+1 -1) 📝 `src/snippets/langsmith/multi-workspace-org-roles.mdx` (+1 -1) </details> ### 📄 Description ## Description Clarifies organization roles documentation to explicitly state that Organization User and Organization Viewer roles are only available on Plus and Enterprise plans. Replaces vague "plans with multiple workspaces" phrasing with specific plan names and uses "Developer organizations" terminology to explain that single-workspace orgs default to Organization Admin. This addresses user confusion about role availability across plan types. Resolves DOC-643 ## Test Plan - [ ] Verify updated snippet renders correctly on administration-overview page - [ ] Verify rbac.mdx Note box reads clearly - [ ] Verify set-up-hierarchy.mdx Info box includes Organization Viewer role mention --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-06-05 18:22:52 -04:00
yindo closed this issue 2026-06-05 18:22:52 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
deepagents
docs-infra
external
external
help wanted
integration
internal
internal
javascript
js/ts
langchain
langgraph
langsmith
needs-title
pull-request
Mirrored from GitHub Pull Request
 python
reference
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langchain-ai/docs#3364
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?