> ## Documentation Index
> Fetch the complete documentation index at: https://help.dsalta.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LangSmith

> LLM observability — members & access

<Tabs>
  <Tab title="Overview">
    Connect LangSmith with a Personal Access Token to sync organization members, workspaces and tracing projects, and run access reviews. Read-only.

    <Info>
      **Read-only access.** DSALTA only reads data from this integration. It never creates, modifies, or deletes anything in your environment, and every remediation step is performed by your team directly in the third-party product.
    </Info>

    <Info>
      **What you'll see.** The Access page lists the **members** of your LangSmith organization with their name, email, organization role and the date they were added; a member LangSmith flags as read-only has **(read-only)** added to the role. LangSmith reports no account status or MFA state, so every member is shown as **Active** with MFA **Unknown**.
    </Info>

    <Note>
      DSALTA collects this integration's data when you connect it — you can refresh it at any time with **Sync from integrations** on the **Integrations** page. The compliance checks below re-run once a day at 02:00 America/New\_York.
    </Note>

    ## What DSALTA reads

    DSALTA reads the LangSmith organization member roster — names, emails, roles and join dates — which appears on your **Access** page; and your LangSmith **workspaces** and **tracing projects**, which appear on your **Inventory** page. Traces, runs and prompts are never read.

    It calls these LangSmith endpoints on `api.smith.langchain.com`:

    * `/api/v1/orgs/current`
    * `/api/v1/orgs/current/members`
    * `/api/v1/workspaces`
    * `/api/v1/sessions`

    Every request is a read. DSALTA has no code path that creates, modifies, or deletes anything in your LangSmith environment.

    ## Troubleshooting

    <AccordionGroup>
      <Accordion title="The connection is rejected">
        The key must be a **Personal Access Token** created under **Settings → API Keys**; a workspace-scoped **Service Key** may not be able to read the organization's members. An expired or deleted token fails the same way — create a new one and connect again.
      </Accordion>

      <Accordion title="The Access page shows fewer members than the console">
        A Personal Access Token inherits the permissions of the user who created it. Create it as an **Organization Admin**, then disconnect and connect again. Note that disconnecting permanently deletes the data already collected from LangSmith.
      </Accordion>
    </AccordionGroup>

    <AccordionGroup>
      <Accordion title="How do I check whether the connection is healthy?">
        Open **Integrations** in the DSALTA sidebar, stay on the **Connected** tab, and click **Manage** on the integration's card. Open the **Status** tab: it shows either **Connected and working properly** or **Connection issues detected**.

        Use the **Status** tab, not **Overview** — Overview always reports **Connected** regardless of the real state.
      </Accordion>

      <Accordion title="A check shows Failed and nothing changed on my side">
        On an integration-powered check, **Failed** normally means DSALTA was blocked rather than that you are non-compliant. Open the test, go to **Source Data**, and read the result code: **403** is a missing permission, **428** is a setting DSALTA still needs, **500** is a failure on DSALTA's side.

        A real compliance gap shows **207** and leaves the test looking **Completed**. See [Understanding Test Results](/guides/compliance/test-results).
      </Accordion>

      <Accordion title="Data looks out of date">
        Compliance checks re-run once a day at 02:00 America/New\_York. To refresh sooner, open **Integrations → Connected** and click **Sync from integrations** at the top right — it refreshes every connected integration at once.
      </Accordion>

      <Accordion title="How do I repair a broken connection?">
        There is no Reconnect, Repair or Refresh Token button. The only repair available is to disconnect and connect again.

        <Warning>
          **Disconnecting is destructive and cannot be undone.** DSALTA removes the access records, inventory, vulnerabilities, code changes, incidents and device records collected from this integration, and deletes the test results tied to the connection. Export anything you still need as audit evidence first — see [Integration errors](/troubleshooting/integration-errors).
        </Warning>
      </Accordion>

      <Accordion title="Configure scope will not let me change anything">
        That is expected. **Configure scope** is read-only — it shows what DSALTA is permitted to read, and has no Save action. To change what DSALTA can see, change the permissions on the credential in the third-party product, then disconnect and connect again.
      </Accordion>
    </AccordionGroup>
  </Tab>

  <Tab title="How to connect">
    A LangSmith Personal Access Token (lsv2\_pt\_…). The organization is detected automatically. Read-only.

    **Before you begin**

    * A LangSmith organization, and a member of it who can see every member — the token inherits that user's permissions, so an **Organization Admin** is the safe choice.

    You will need:

    | Field                     | Where to find it                         | Example                 |
    | ------------------------- | ---------------------------------------- | ----------------------- |
    | **Personal Access Token** | **Settings → API Keys → Create API Key** | `lsv2_pt_…`, shown once |

    <Steps>
      <Step title="Start in DSALTA">
        Open **Integrations** in the DSALTA sidebar, find **LangSmith**, and click **Connect** to open the connect panel.
      </Step>

      <Step title="Create a Personal Access Token">
        In [smith.langchain.com](https://smith.langchain.com), open **Settings → API Keys** and click **Create API Key**. Choose the **Personal Access Token** type, set an expiration (a number of days, or never), and copy the token — it starts with `lsv2_pt_`.

        <Info>
          LangSmith shows the token once. Personal Access Tokens "inherit the permissions of the user who created them"; Service Keys are scoped to a workspace or organization instead and are meant for applications. DSALTA needs the organization's member list, which is why the connection asks for a Personal Access Token created by an admin.
        </Info>
      </Step>

      <Step title="Connect LangSmith">
        Return to the connect panel, paste the token, and click **Connect**. The organization is detected automatically.
      </Step>
    </Steps>

    <Check>
      DSALTA validates the token when you click **Connect**, by reading the token's current organization. On success the integration moves to the **Connected** tab, and **Manage → Status** reads **Connected and working properly**. Checks begin reporting after the first sync.
    </Check>

    <Warning>
      **If the connection is rejected.** An expired or deleted token, or a Service Key instead of a Personal Access Token.

      The on-screen message is generic — see [Connection error messages](/troubleshooting/connection-error-messages).
    </Warning>
  </Tab>

  <Tab title="Automated checks">
    Each check below re-runs once a day, at 02:00 America/New\_York, while this integration is connected. Click any check for step-by-step remediation guidance.

    | Check                                                                                                                    | Severity | What it verifies                                                                     |
    | ------------------------------------------------------------------------------------------------------------------------ | -------- | ------------------------------------------------------------------------------------ |
    | [User access to Critical System should be valid](/integrations/langsmith/user-access-to-critical-system-should-be-valid) | Info     | Checks that everyone with LangSmith access is an active employee on the People page. |
    | [Offboarded users should not have active access](/integrations/langsmith/offboarded-users-should-not-have-active-access) | High     | Checks that offboarded employees no longer have active LangSmith access.             |
  </Tab>

  <Tab title="Useful links">
    | Topic   | Link                                                                             |
    | ------- | -------------------------------------------------------------------------------- |
    | Setup   | [Create an API key](https://docs.langchain.com/langsmith/create-account-api-key) |
    | General | [LangSmith](https://smith.langchain.com)                                         |
    | DSALTA  | [Connection error messages](/troubleshooting/connection-error-messages)          |
  </Tab>
</Tabs>