Skip to content

Commit 7fb256f

Browse files
committed
docs: Consolidate pages for access user management
1 parent 4e6c679 commit 7fb256f

19 files changed

+942
-996
lines changed

src/langsmith/administration-overview.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ This overview covers topics related to managing users, organizations, and worksp
99

1010
### Organizations
1111

12-
An organization is a logical grouping of users within LangSmith with its own billing configuration. Typically, there is one organization per company. An organization can have multiple workspaces. For more details, see the [setup guide](/langsmith/set-up-organization).
12+
An organization is a logical grouping of users within LangSmith with its own billing configuration. Typically, there is one organization per company. An organization can have multiple workspaces. For more details, see the [setup guide](/langsmith/set-up-a-workspace#set-up-an-organization).
1313

1414
When you log in for the first time, a personal organization will be created for you automatically. If you'd like to collaborate with others, you can create a separate organization and invite your team members to join. There are a few important differences between your personal organization and shared organizations:
1515

@@ -25,7 +25,7 @@ When you log in for the first time, a personal organization will be created for
2525
Workspaces were formerly called Tenants. Some code and APIs may still reference the old name for a period of time during the transition.
2626
</Info>
2727

28-
A workspace is a logical grouping of users and resources within an organization. A workspace separates trust boundaries for resources and access control. Users may have permissions in a workspace that grant them access to the resources in that workspace, including tracing projects, datasets, annotation queues, and prompts. For more details, see the [setup guide](/langsmith/set-up-workspace).
28+
A workspace is a logical grouping of users and resources within an organization. A workspace separates trust boundaries for resources and access control. Users may have permissions in a workspace that grant them access to the resources in that workspace, including tracing projects, datasets, annotation queues, and prompts. For more details, see the [setup guide](/langsmith/set-up-a-workspace).
2929

3030
It is recommended to create a separate workspace for each team within your organization. To organize resources even further, you can use [Resource Tags](#resource-tags) to group resources within a workspace.
3131

@@ -110,7 +110,7 @@ Service keys are prefixed with `lsv2_sk_`
110110

111111
### Organization roles
112112

113-
Organization roles are distinct from the Enterprise feature (RBAC) below and are used in the context of multiple [workspaces](#workspaces). Your organization role determines your workspace membership characteristics and your organization-level permissions. See the [organization setup guide](/langsmith/set-up-organization#organization-roles) for more information.
113+
Organization roles are distinct from the Enterprise feature (RBAC) below and are used in the context of multiple [workspaces](#workspaces). Your organization role determines your workspace membership characteristics and your organization-level permissions. See the [organization setup guide](/langsmith/set-up-a-workspace#organization-roles) for more information.
114114

115115
The organization role selected also impacts workspace membership as described here:
116116

@@ -158,7 +158,7 @@ Roles can be managed in organization settings under the `Roles` tab:
158158

159159
![Roles](/langsmith/images/roles-tab-rbac.png)
160160

161-
For more details on assigning and creating roles, see the [access control setup guide](/langsmith/set-up-access-control).
161+
For more details on assigning and creating roles, see the [access control setup guide](/langsmith/user-management).
162162

163163
## Best Practices
164164

@@ -175,7 +175,7 @@ In May 2024, LangSmith introduced a maximum data retention period on traces of 4
175175
#### Why retention matters
176176

177177
* **Privacy**: Many data privacy regulations, such as GDPR in Europe or CCPA in California, require organizations to delete personal data once it's no longer necessary for the purposes for which it was collected. Setting retention periods aids in compliance with such regulations.
178-
* **Cost**: LangSmith charges less for traces that have low data retention. See our tutorial on how to [optimize spend](/langsmith/manage-spend) for details.
178+
* **Cost**: LangSmith charges less for traces that have low data retention. See our tutorial on how to [optimize spend](/langsmith/billing#optimize-your-tracing-spend) for details.
179179

180180
#### How it works
181181

@@ -358,4 +358,4 @@ Usage limits can be updated from the `Settings` page under `Usage and Billing`.
358358

359359
### Related content
360360

361-
* Tutorial on how to [optimize spend](/langsmith/manage-spend)
361+
* Tutorial on how to [optimize spend](/langsmith/billing#optimize-your-tracing-spend)

src/langsmith/authentication-methods.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@ Users can alternatively use their credentials from GitHub or Google.
1717

1818
### SAML SSO
1919

20-
Enterprise customers can configure [SAML SSO](/langsmith/set-up-saml-sso) and [SCIM](/langsmith/set-up-scim)
20+
Enterprise customers can configure [SAML SSO](/langsmith/user-management) and [SCIM](/langsmith/user-management)
2121

2222
## Self-Hosted
2323

0 commit comments

Comments
 (0)