Skip to main content
Get started

Connect a client's Claude organization

Generate the client's monitoring configuration in Engage, copy it once, and send the setup steps to the client's Claude admin.

Written By The Lemhi Product Team

Last updated 10 days ago

For the Tenant Admin connecting a client to Claude Visibility. When you're done, the client's Claude admin has the values and steps to paste into Claude, and the client's Claude tab shows Waiting for first activity.

Before you start

  • The Tenant Admin role in Engage. Other users see "Ask an MSP admin to connect Claude for this client." in place of the button.

  • The client has Claude Team or Enterprise.

  • You know who the client's Claude admin is, and you've asked whether Claude already sends monitoring somewhere else. Claude sends activity to one destination per organization, and entering Lemhi's endpoint replaces any existing one.

Generate the configuration

  1. Open the client and select AI Usage.

  2. Select the Claude tab. The Claude activity card reads "See who at [client] uses Claude, what it touches, and what it would cost at API prices. Requires Claude Team or Enterprise."

  3. Select Connect Claude. The Connect Claude panel opens.

  4. Copy each value with its Copy button:

Field in the panel

Value

OTLP endpoint

Lemhi's endpoint, ending in /claude

OTLP protocol

http/protobuf

OTLP headers

Authorization=Bearer followed by the client's monitoring key

Resource attributes

Leave blank

  1. Select and copy the steps under Steps for the client's Claude admin. The panel fills the monitoring key into them, so they're ready to send.

  2. Send the steps to the client's Claude admin, or send them the link to Set up Claude monitoring for Lemhi with the values.

  3. Close the panel.

The OTLP headers value is shown once. The panel says "Shown once. Copy it now; Lemhi can't show it again." Lemhi doesn't store the key itself. Once you close the panel, the only way to get a working value is to regenerate the configuration.

If the configuration can't be created, the card shows "The monitoring configuration couldn't be created. Try again, or contact Lemhi support if it keeps failing."

While you wait

The Claude tab now shows Claude activity with the Waiting for first activity badge and "Monitoring configuration created [date] by [name]". The note under it reads:

"Activity usually appears within a few minutes of the client's Claude admin saving the settings. If nothing appears after an hour, the OTLP headers were most likely pasted wrong. Regenerate the configuration and send the new one."

To send the steps again, select View setup steps. The Setup steps panel shows the endpoint, protocol and steps, but not the key: in its place it says "The OTLP headers value was shown once, when the configuration was generated. Lemhi can't show it again. To send it again, regenerate the configuration." Select Regenerate configuration there if the client's admin never received the key. See Regenerate or revoke a Claude configuration for what that changes.

The status moves to Live when Lemhi receives the client's first activity. The client's Claude admin has to start a new Cowork session after saving, because sessions already open keep the old settings.

Next

Read the Claude activity views

Was this helpful?

Still need help? Ask the team