Skip to main content
Manage and troubleshoot

Regenerate or revoke a Claude configuration

Use Connection details to replace a lost or exposed monitoring key, stop collecting a client's Claude activity, and read the history.

Written By The Lemhi Product Team

Last updated 10 days ago

For the Tenant Admin who needs to replace a client's monitoring key or stop Lemhi collecting a client's Claude activity. When you're done, the old key no longer works and the history shows who changed what.

Before you start

  • The Tenant Admin role in Engage. Other users see the status and last activity in Connection details, but not the buttons or history.

  • For a regenerate, a way to reach the client's Claude admin. Activity stops until they enter the new value.

Connection details

On the client's AI Usage page, Claude tab, select Connection details. The panel shows:

  • Status, with the current badge.

  • "Last activity received [date and time]", or "No activity received yet".

  • "Monitoring configuration created [date] by [name]".

  • Regenerate configuration and Revoke configuration, while a configuration is active.

  • History: every action, newest first, with Action, Person and Date and time. Actions are Generated, Regenerated, Revoked, and Revoked when the client was deleted.

The OTLP headers value never shows here.

Regenerate or revoke

Question

Regenerate

Revoke

Use it when

The key was lost before the client entered it, was pasted wrong, or may have been exposed

The client stops using Lemhi for Claude, or you no longer want its activity

What happens

The old key stops working and a new one is shown once

The key stops working. No new one is made

Activity already collected

Stays. The views hide while the status is Waiting for first activity and show again once Claude sends activity with the new key

Stays. The activity views don't show while the status is Revoked

The client's Claude admin

Pastes the new OTLP headers value, saves, starts a new Cowork session

Nothing required. They can remove Lemhi's values from Claude's Monitoring settings

Status after

Waiting for first activity until the new key is used. Rejected activity if Claude keeps sending the old key

Revoked

Either way, Lemhi locks out the old key within about a minute.

Regenerate the configuration

  1. Select Connection details > Regenerate configuration.

  2. Read the confirmation: "The current monitoring configuration stops working immediately. The client's Claude admin has to enter the new OTLP headers before activity resumes."

  3. Select Regenerate configuration. The Connect Claude panel opens with the new values.

  4. Copy the OTLP headers value and the steps. They're shown once.

  5. Send them to the client's Claude admin. Only the OTLP headers value changed. They follow Set up Claude monitoring for Lemhi, "If your provider sends new values".

You can also regenerate from Regenerate configuration on the Rejected activity note, or from View setup steps while waiting for first activity.

Revoke the configuration

  1. Select Connection details > Revoke configuration.

  2. Read the confirmation: "Lemhi stops accepting this client's Claude activity. Activity already collected stays. You can connect again later."

  3. Select Revoke configuration.

To connect again later, select Connect Claude on the status header. That generates a new configuration, and the client's Claude admin enters all of it again, as in Connect a client's Claude organization.

Revoking in Lemhi doesn't change the client's Claude settings. Until the client's Claude admin removes or replaces Lemhi's endpoint, Claude keeps sending to it and Lemhi turns the activity away.

Was this helpful?

Still need help? Ask the team