Skip to main content

​
Overview

The Claude Code integration connects your organization’s Claude Code (Teams plan) subscription to G360, so you can see Claude Code usage, cost, adoption and productivity on the Claude Code dashboard and use it in your engineering and AI coding metrics. G360 does not poll Anthropic with an API key. Instead, Claude Code on each developer’s machine sends its built-in OpenTelemetry (OTel) metrics and logs to G360. You turn this on once, org-wide, by pasting a settings block that G360 generates into Claude Code’s managed settings. With this integration, you can:
  • Track Claude Code usage, tokens, cost and adoption across the organization
  • See who holds a seat and which seats are inactive
  • View cost savings and an ROI estimate
Setup has four parts:
  1. Create the connection in G360 and copy the settings block it generates.
  2. Paste the settings block into Claude Code managed settings.
  3. Upload your seat roster (the usage export from Claude).
  4. Review the ROI and cost settings used by the Cost Savings and ROI tabs.
Only the Teams plan can be connected today. The Enterprise option is shown in the form but is marked Enterprise — Coming Soon and cannot be saved.

​
Prerequisites

Before you start, make sure you have:
  • A Claude Code Teams plan
  • A G360 admin account (only admins can open the Claude Code connection page and the Claude Code settings pages)
  • A Claude admin who can edit managed settings at claude.ai/admin-settings/claude-code
  • Developer machines that can reach the G360 OTel endpoint shown in the settings block (see Network requirements)

​
Connect Claude Code

1

Open the Claude Code connection page

  1. In the left navigation menu, click Integrations.
  2. Select the AI Coding tab.
  3. Click the Claude Code card.
You see the Claude Code Connections page: a search box, an Add Connection button and a table of existing connections with the columns Connection Name, Provider, Plan Type, Status, Created At, Last Received and Actions.
2

Add the connection

  1. Click Add Connection. The Add Claude Code Connection window opens.
  2. In Connection Name (required), enter a name that is easy to identify, for example Acme Corp Claude Code or Engineering Team Claude Code. Names must be unique among your Claude Code connections.
  3. Leave Account Type set to Teams.
  4. Click Save Connection.
After you save, you see:
  • The page title changes to Teams Connection, with a Teams Plan Connected card showing the Plan Type and Connection Name.
  • A settings.json block with a Copy JSON button.
  • A Next Steps panel.
  • A Project Created message: G360 automatically creates a project for this connection, links the connection to it and starts its first sync. (If you started from Project Setup instead, that flow links the connection to the project you are setting up.)
If the name is already used, the form shows A connection name already exists.
3

Copy the settings block

Click Copy JSON. The button briefly changes to Copied!.The block looks like this. The endpoint and token are filled in for your connection; always copy them from G360 instead of retyping them.
Copy the block now. The G360 UI shows it only on this screen, right after you create the connection; it is not shown again from the connections list. The ingest.token identifies your connection, so treat it like a password.
4

Apply the settings in Claude Code managed settings

Follow the Next Steps panel:
  1. Go to Managed Settings: claude.ai/admin-settings/claude-code.
  2. Paste the copied settings.json content.
  3. Follow the on-screen instructions in Claude to save your changes.
Do not change OTEL_EXPORTER_OTLP_PROTOCOL to grpc, and do not edit the endpoint or token. Leave OTEL_LOG_USER_PROMPTS unset (it is off by default), so prompt text is never exported.
G360 collects Claude Code metrics and event logs only. It does not collect prompts or code.
5

Confirm telemetry is arriving

  1. Click Back to return to Claude Code Connections.
  2. Once developers use Claude Code with the new settings, the connection’s Last Received column changes from Never to the date telemetry last arrived.
The Claude Code dashboard fills in after G360’s next processing run.
6

Upload the seat roster

The roster tells G360 who holds a Claude Code seat. It powers the Inactive Users, Cost Savings and ROI tabs, and it decides whose telemetry is loaded.First export the file from Claude (G360 shows these same steps when you hover Upload instructions):
  1. Go to claude.ai/analytics/usage.
  2. Scroll to top members by artifacts created.
  3. Click see all to view the full member list.
  4. Confirm all members is now displayed.
  5. Set the date range to last 30 days and export as CSV.
Then upload it in G360:
  1. In the left navigation menu, open Users and Teams and select the Claude Code Users tab. The Claude User Management page opens.
  2. In Connection, select your Claude Code connection.
  3. Click Upload Usage Data and choose the exported file (.csv or .xlsx).
After the upload you see a Users Uploaded message such as “5 added, 2 updated, 40 in the roster. 3 removed (not in this file).” The Seat Roster table lists each person with Name, Email, Chats, Code Sessions, Cowork Sessions and Last Active.
The file you upload is the source of truth. Anyone who is not in the latest file is removed from the roster, and their telemetry is no longer loaded. People who appear in a later file again are restored. Always upload the complete member list.
  • Until the first roster upload, G360 loads all telemetry it receives for the connection.
  • The roster is also how G360 learns which Anthropic organization is yours, so telemetry from a developer signed into a personal account can be rejected. This only switches on once at least three rostered people have sent telemetry and at least 80% of them agree on one organization; until then G360 keeps storing everything it receives.
  • Without a roster, the Cost Savings and ROI tabs show an error saying the seat roster is empty.
7

Review ROI and cost settings

The ROI tab uses three values. Until you change them, G360 uses the defaults below.
  1. Go to Settings → ROI Settings → AI Coding Tool Settings and open Claude Code Settings.
  2. Click the edit action. The Claude Code ROI Settings form opens.
  3. Enter the values (all required, each must be greater than 0) and save.
The Cost Savings tab uses a different value: the Claude Code Cost / Seat under Settings → Tool Cost Settings. The number of days without activity before a seat counts as inactive comes from Settings → Inactive User Settings (30 days if not set).
Settings → AI Coding Tool Settings → Claude Settings holds optional analytics tuning (model downgrade, savings rates, high-waste thresholds and productivity score weights). You don’t need to change it to get started.

​
Edit or delete a connection

On Claude Code Connections, use the icons under Actions:
  • Pencil: opens Edit Claude Code Connection. Only the Connection Name can be changed; click Save Connection. The plan type cannot be changed. To switch plans, delete the connection and create a new one.
  • Trash: asks Delete connection — Are you sure you want to delete this connection? Click Yes to delete.
A connection that is linked to a project cannot be deleted. G360 shows Cannot Delete Connection: This connection is linked to a project. Unlink it first. Because G360 links a new connection to a project automatically, remove it from its project before deleting it.
Deleting a connection removes it from G360 together with its ingest token, seat roster, sync schedule and the Claude Code data loaded through it, so its data no longer appears on the dashboard. Developer machines that still send telemetry with the old token are no longer accepted. Remove the settings block from Claude Code managed settings as well.

​
Network requirements

Developer machines must be able to reach the endpoint in OTEL_EXPORTER_OTLP_ENDPOINT from the settings block. The exporter sends to <endpoint>/v1/metrics and <endpoint>/v1/logs using HTTP. On a standard G360 deployment this is the G360 host’s /otel route on port 443, the same TLS endpoint that serves the G360 UI, so no extra port is needed. If your G360 is hosted differently, the block shows the endpoint to allow.

​
Troubleshooting

  • Confirm the settings block was saved in Claude Code managed settings, exactly as copied.
  • Confirm developers have used Claude Code since the settings were applied.
  • Confirm developer machines can reach the endpoint in the settings block.
  • Check that they are in the latest roster file. People missing from the latest upload are removed and their telemetry is not loaded.
  • Upload the seat roster for the connection on Claude User Management.
  • The connection is linked to a project. Unlink it first, then delete.

​
Summary

Create a Teams connection, paste the generated settings block into Claude Code managed settings, and upload your seat roster. Once telemetry arrives (Last Received shows a date), Claude Code usage, cost, adoption, productivity, inactive seats and ROI become available on the Claude Code dashboard.