You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/langsmith/administration-overview.mdx
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ This overview covers topics related to managing users, organizations, and worksp
9
9
10
10
### Organizations
11
11
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).
13
13
14
14
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:
15
15
@@ -25,7 +25,7 @@ When you log in for the first time, a personal organization will be created for
25
25
Workspaces were formerly called Tenants. Some code and APIs may still reference the old name for a period of time during the transition.
26
26
</Info>
27
27
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).
29
29
30
30
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.
31
31
@@ -110,7 +110,7 @@ Service keys are prefixed with `lsv2_sk_`
110
110
111
111
### Organization roles
112
112
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.
114
114
115
115
The organization role selected also impacts workspace membership as described here:
116
116
@@ -158,7 +158,7 @@ Roles can be managed in organization settings under the `Roles` tab:
158
158
159
159

160
160
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).
162
162
163
163
## Best Practices
164
164
@@ -175,7 +175,7 @@ In May 2024, LangSmith introduced a maximum data retention period on traces of 4
175
175
#### Why retention matters
176
176
177
177
***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.
179
179
180
180
#### How it works
181
181
@@ -358,4 +358,4 @@ Usage limits can be updated from the `Settings` page under `Usage and Billing`.
358
358
359
359
### Related content
360
360
361
-
* Tutorial on how to [optimize spend](/langsmith/manage-spend)
361
+
* Tutorial on how to [optimize spend](/langsmith/billing#optimize-your-tracing-spend)
0 commit comments