Connect a Claude Enterprise organization

Turn on usage reporting for Claude Code, Cowork, and the Office agents across your whole Claude Enterprise organization from Anthropic's admin console, with nothing installed on any device.

If your company is on a Claude Enterprise plan, an admin can turn on usage reporting for everyone at once from Anthropic's own admin console. Claude Code, Cowork, and the Office agents (Claude in Word, Excel, PowerPoint, and Outlook) then send their model usage and cost to Proxon, credited to the person who used them. Nothing installs on anyone's device, and no developer changes anything. This page is for the Claude Enterprise admin doing that setup.

You mint one shared Proxon credential, then paste it into three places in the Anthropic admin console. Anthropic keeps a separate configuration for each product, and none of the three reads the others, so you set all three. You need to be an organization owner or admin in Proxon to mint the credential, and a Claude Enterprise admin to reach the console. The Claude Code page needs the Owner or Primary Owner role.

Step 1: Mint a shared service credential

In Proxon, open Org Settings, then Credentials, and choose Generate. Give it a label such as "Claude Enterprise" and turn on the option that lets Proxon trust the identity Anthropic stamps on each record. Proxon issues a bearer token that starts with prx_svc_, scoped to your organization.

The token is shown once. Copy it and store it as a secret. Proxon keeps only a hash, so it cannot show the token to you again. If you lose it, rotate it or generate a new one from the same screen.

A credential minted here has no owner, which is what this setup needs. Every person in your Claude Enterprise organization sends through this one token, and Anthropic stamps each record with the email of the person who used the product. The attribution option tells Proxon to read that email and credit the right person. A personal credential cannot carry this option, and the option changes nothing for other tools that send OpenTelemetry with the same token.

Only organization owners and admins see Credentials.

Step 2: Configure Claude Code

In the Anthropic admin console, open Admin settings, then Claude Code, then Managed settings. You need the Owner or Primary Owner role for this page. Add the keys below to the env object of your existing managed settings, replacing prx_svc_<prefix>_<secret> with the token from Step 1. If your organization has no managed settings yet, paste the block as it is. Do not replace an existing document with it, because that removes every other managed setting for the whole organization.

json

{
  "env": {
    "CLAUDE_CODE_ENABLE_TELEMETRY": "1",
    "OTEL_LOGS_EXPORTER": "otlp",
    "OTEL_METRICS_EXPORTER": "otlp",
    "OTEL_EXPORTER_OTLP_PROTOCOL": "http/protobuf",
    "OTEL_EXPORTER_OTLP_ENDPOINT": "https://ingest.proxon.ai",
    "OTEL_EXPORTER_OTLP_HEADERS": "Authorization=Bearer prx_svc_<prefix>_<secret>",
    "OTEL_LOG_USER_PROMPTS": "0",
    "OTEL_LOG_ASSISTANT_RESPONSES": "0"
  }
}

This one block covers Claude Code in the terminal, VS Code, JetBrains, the desktop app's Code tab, the Agent SDK, and cloud sessions. It applies to the whole organization and replaces any endpoint a developer set on their own machine. The last two keys keep prompt and response text out of the export even when a developer turned it on in their own settings, since managed settings only override the keys they define.

The first time each person starts Claude Code after this, they see a one-time prompt naming https://ingest.proxon.ai and asking them to approve it. Tell people to expect it. Declining exits Claude Code.

Cloud sessions, meaning claude.ai/code and routines, also need ingest.proxon.ai added to the cloud environment's Custom allowed domains list. Managed settings deliver the environment block but can never add a domain, and the cloud environment blocks every other destination.

Step 3: Configure Cowork

In the Anthropic admin console, open Admin settings, then Cowork, then Monitoring. Enter these values.

Endpoint: https://ingest.proxon.ai
Protocol: http/protobuf (http/json also works, and gRPC is not supported)
Headers: Authorization=Bearer prx_svc_<prefix>_<secret>
Resource attributes: optional, for example deployment.environment=prod

Anything you put in resource attributes lands on every record Cowork sends, so it is a convenient way to mark a channel.

Cowork does not read the Claude Code managed settings block. It has its own configuration on this page, and until you fill it in, Cowork sends nothing, even with Claude Code fully set up. This is the single easiest thing to get wrong.

Step 4: Configure the Office agents

In the Anthropic admin console, open Admin settings, then Office agents, then Monitoring. Enter the same endpoint, protocol, and header line as for Cowork. This covers Claude in Word, Excel, PowerPoint, and Outlook.

The Office add-in reads this configuration when its panel loads. After you save, people need to reload the Office tab in their browser, or restart desktop Office, before their usage is sent.

Step 5: Confirm it landed

Start a fresh Claude Code session, a new Cowork conversation, or a new Office agent task, and run one prompt. Then open Cost Intelligence in Proxon. The usage appears there, credited to the person who ran it, usually within a minute. Claude Code sends its logs every 5 seconds and its cost and token metrics every 60 seconds.

Configuration is read when a session starts. A Claude Code process that was already running, or a Cowork conversation that is continued rather than started fresh, sends nothing until it is restarted. If you see no data, quit and start again before you look anywhere else.

While testing, you can add "OTEL_METRIC_EXPORT_INTERVAL": "10000" to the Claude Code env block so the metrics arrive every 10 seconds. Remove it afterwards.

What is sent

Every record carries the model and the token counts of each call, along with the email of the person who used the product. Claude Code and Cowork also report the cost of each call. The Office agents do not, so Proxon computes it from its price list. Proxon uses the email to credit the usage to the matching person in your roster, so the roster must carry the same email Anthropic reports. A directory import keeps it in sync. Usage sent before a person is on the roster stays Unattributed. Usage sent after they are added is credited to them.

Cowork and the Office agents send prompt and response text by default, and Anthropic offers no setting to turn that off. The Office agents also send the address of the document being edited and the full input and output of every tool call. Proxon discards all of that text on arrival unless an admin has turned on the Content aware level for your organization. Claude Code sends no prompt or response text with the block above. See What Proxon captures for what each level includes.

What this does not cover

Nothing on this page reaches chat on claude.ai, chat in Claude Desktop, Claude in Chrome, or Claude in Slack. Their daily usage and cost come through the Claude Enterprise integration instead, which reads Anthropic's Analytics API. You connect it from the Integrations page in Proxon.