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

# Claude Cowork

> Send Claude Cowork activity to Velatir by pointing Cowork's OpenTelemetry export at your organisation's Velatir endpoint

Claude Cowork can export its activity over OpenTelemetry. Point that export at Velatir and Cowork sessions
appear alongside everything else in your organisation.

This is configured once, for the whole organisation, in Anthropic's admin settings — there is nothing to
install on anyone's machine.

<Note>
  Cowork monitoring requires a Claude Team or Enterprise plan.
</Note>

<Info>
  **Cowork is set up in the opposite direction to most connectors.** Elsewhere you give Velatir a credential and
  Velatir fetches your activity. Here you give *Claude* a Velatir endpoint and Cowork sends its activity to us.
  So there is nothing to add on the Velatir side — you will not find Cowork in the connector list, and all the
  configuration below happens in Claude.
</Info>

## What you need

* Administrator access to your Claude organisation's admin settings.
* Your Velatir ingest key. Create one under **Settings → API keys**, or see the [quickstart](/quickstart).

## Connect Cowork

<Steps>
  <Step title="Open Cowork's monitoring settings">
    In Claude, go to **Organization Settings → Cowork** and find the **Monitoring** section.
  </Step>

  <Step title="Enter the endpoint">
    Set **OTLP endpoint** to:

    ```
    https://otlp.velatir.com
    ```

    Enter it exactly as shown, with no path after the domain — Cowork adds the rest itself.
  </Step>

  <Step title="Choose a protocol">
    Set **OTLP protocol** to either `http/protobuf` or `http/json`. Velatir accepts both, so pick either one.
  </Step>

  <Step title="Add your ingest key">
    Set **OTLP headers** to your ingest key:

    ```
    X-API-Key=vltr_your_key_here
    ```

    `Authorization=Bearer vltr_your_key_here` also works if you prefer it.
  </Step>

  <Step title="Leave Resource attributes empty">
    Velatir needs nothing here. Cowork already identifies itself in every message it sends, so there is no
    label to add.

    If your organisation uses resource attributes for its own purposes, anything you put here is passed
    through and ignored — with one exception:

    <Warning>
      Do not set `service.name`. That is how Velatir recognises the activity as coming from Cowork. Overriding
      it means your activity arrives unrecognised and is discarded.
    </Warning>
  </Step>

  <Step title="Save, then start a new session">
    Save your settings and start a **new** Cowork session. Cowork reads these settings when a session begins,
    so sessions already running keep using the old configuration.
  </Step>
</Steps>

Activity from that new session appears in Velatir within a minute or two.

## What Velatir receives

Cowork sends prompts, model responses, tool use, and errors. Whether the **text** of prompts and responses is
included is controlled on the Claude side, not by Velatir. When Claude sends activity without that text,
Velatir records nothing for those turns rather than storing empty entries.

Cowork also sends usage measurements. Velatir accepts them and does not store them.

## Notes

* **No firewall changes are needed for Cowork itself.** Cowork adds your collector's hostname to its own
  session network allowlist automatically. If your corporate network restricts outbound traffic from
  employees' machines, allow `otlp.velatir.com` on port 443 there.
* **Your ingest key identifies your organisation.** Anyone holding it can send activity as your organisation,
  so treat it like any other credential. Rotate it under **Settings → API keys** if it is exposed.
* **Cowork sessions carry the acting user's email**, so activity is attributed per person without any extra
  configuration.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Nothing appears in Velatir">
    Start a brand-new Cowork session — settings only take effect for sessions started after you saved them.
    Then check the endpoint is `https://otlp.velatir.com` with nothing after the domain, and that the header
    is spelled `X-API-Key=` followed by your key with no spaces around the `=`.
  </Accordion>

  <Accordion title="Sessions appear, but with no prompt or response text">
    That text is only included when content capture is enabled on the Claude side. Velatir stores whatever
    Cowork sends and never invents the rest.
  </Accordion>

  <Accordion title="The key was rejected">
    Confirm the key is active under **Settings → API keys**. A revoked or expired key stops working
    immediately, and Cowork has no way to show you the rejection — you will simply see no new activity.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Get your ingest key" icon="key" href="/quickstart">
    Set up your account and create a key
  </Card>

  <Card title="Sessions and traces" icon="list" href="/traces/understanding-sessions">
    How activity is grouped once it reaches Velatir
  </Card>
</CardGroup>