Skip to content

chore: explicitly state group renaming in SCIM is not supported #1235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 3, 2025
Merged

chore: explicitly state group renaming in SCIM is not supported #1235

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion src/langsmith/user-management.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -414,6 +414,10 @@ The link expires in 24 hours, and can be resent if needed by removing and re-add

#### Group Naming Convention

<Warning>
Renaming groups is **not** supported via SCIM. Group names are persistent because they must match role names and/or workspace names in LangSmith.
</Warning>

Group membership maps to LangSmith workspace membership and workspace roles with a specific naming convention:

**Organization Admin Groups**
Expand Down Expand Up @@ -637,7 +641,7 @@ You must use the [Okta Lifecycle Management](https://www.okta.com/products/lifec
- Create users
- Update user attributes
- Deactivate users
- Group push
- Group push (**without group renaming**)
- Import users
- Import groups

Expand Down