Control Tower for Claude: observability and operational governance.
It shows leaders what each department uses Claude for, what each one spends, and whether Claude is set up safely. It ranks every fix, routes each one to its owner, and changes nothing in Claude until one of your people confirms it.
Free pilots for 3 companies a quarter · Q4 applications close November 30
0days00hours00min00sec
The email sent when someone leaves but keeps a license
- Financial analyst, FinanceLast used Claude Sep 12
- Account manager, SalesNever used Claude
Example email for a fictional company; roles and dates are illustrations. “Remove both” opens Control Tower for Claude, and nothing changes in Claude until you confirm. The demo uses Halvane Industries, the fictional company on every screen below.
Can you find the risks in your Claude setup before they become incidents?
What a close look would find
- People who have left the company may still have access to Claude. Unless leaving removes it automatically, nothing checks Claude against the list of current employees.
- Tools connected to Claude can change records in other company systems. Often nobody has decided which of them should be allowed to.
- Claude’s settings are rarely checked against a security policy. Without that check, or without a policy for Claude at all, no one can say whether today’s settings are safe.
- There is rarely an up-to-date list of everything each department uses Claude for, with someone accountable for each use. So when a use turns out to be risky, it is unclear who answers for it.
What you couldn’t show when asked
- Managers aren’t asked whether their people still need Claude. Without a review each quarter, nobody can show that everyone with access still needs it.
- No single record shows how Claude is set up and used. Settings, access and use sit on separate screens, so each customer or risk-team request starts from scratch.
- When a risk is found, the fix often has no owner and no priority. So known gaps stay open until a customer or an incident raises them.
Control Tower for Claude checks for these risks every day, gives each fix an owner, and keeps the record.
See it. Check it. Act on it. All in one place.
See how Claude is used
Control Tower for Claude labels every conversation by kind of work, keeping the label, never the conversation. It shows every connected system that read employees’ Claude conversations, and who asked for and approved each request made through it.
Check what quietly changed
Every day, Control Tower for Claude looks for what has quietly changed: people who left still holding a license, a former employee’s key still active, a setting switched off. Incidents stay open until someone addresses them, and stay on record after.
Act on it, with your people deciding
A request for more usage reaches the department’s approver, or an admin, by email, with how the person has used Claude and a recommended limit. A no needs a reason, and the person who asked gets it by email.
Every screen on this page shows Halvane Industries, a fictional 500-person company. Its figures are made up for the demonstration.





Managers see the same pages for their own team only. Leaders can also ask in Claude chat and get the same number the page shows, because both use one definition of every figure.
Give every employee a reason to get better at Claude.
My Claude is each person’s own page: their month in Claude, against the company, with nobody else named.
- Coach. A few specific tips on what to try next, drawn from their own use rather than a generic course.
- Community skills and repos. Picks that fit the work they actually do, refreshed every month.
- Productivity Race. A monthly race that rewards using Claude well, not just using it more. Each person sees their own place and how their team compares. It is built to give people a reason to come back each month, without being told to.
My Claude is built to help people, never to grade them. It does not feed performance reviews.


Your cloud. Your call. No chat text kept.
Where it runs
Control Tower for Claude is already built. We install it in your own cloud account, from a template your IT team can read before it runs.
You confirm every change
Nothing changes in Claude until an admin, or a colleague an admin chose, confirms it. Every fix has an owner. People who left and requests for more usage reach that owner by email; the rest appear on the owner’s list in Actions.
What it can change
It can remove people who left or stopped using Claude, withdraw invitations never accepted, approve or deny requests for more usage, and set spend limits. If your identity provider manages Claude membership, removals happen there instead.
- Usage and cost
- Chats and settings
- Claude, to label
HR file
Department, manager
Daily run
Load, label, check
Database
No chat text
Named metrics
One definition behind every number
Chat text is read only to decide what kind of work it was, then discarded. What is kept is the label and a one-sentence description of the task, with no names, numbers or quotes, checked before it is saved. The database has no column that could hold chat text, and that is tested automatically. Labeling uses an API key from your own Claude Console organization, not ours, billed to you. That organization’s terms may differ from your Claude Enterprise agreement, so your Legal team should confirm they allow labeling chat text.
Answers to your privacy and security teams’ questions
| Your privacy and security team will ask | The answer |
|---|---|
| Where does the data live? | In your Azure subscription. Data leaves only as reads and confirmed changes in Claude, labeling calls to Claude, and emails sent from your own Microsoft 365 mailbox. A monthly public search for skills and repos carries kinds of work, never people. |
| What is never kept? | Chat text, file contents, IP addresses, device details, and any emotion or sentiment judgment about a person. |
| Who sees what? | Admins see every page, with names only on lists that need them. Leaders see totals and each department’s bill, with names only in the access log. Managers see their reporting line, without names. Members see their own My Claude pages. Stewards an admin picks confirm changes for their departments. Outside reviewers you invite see approved evidence packs, read-only, until a date you set. |
| Small groups? | No group under 5 people is shown on its own. Five exceptions: admins’ named lists; the access log, for admins and leaders; each person’s own pages; a department’s own bill, for admins, leaders and its manager; and per-person records an outside reviewer you invite sees in a sample. |
| What can it change? | Only what a person confirms in Control Tower for Claude: removing people who left or haven’t used Claude in 60 days, withdrawing invitations pending 14 days or more, approving or denying requests for more usage, and setting monthly spend limits. Owners and membership admins can’t be removed. If your identity provider manages membership, it can’t remove people. Changes use a separate key that only the web app can read. Without that key, it changes nothing. A key that can delete chats is still flagged as a finding. |
| Is access logged? | Page views once sign-in is on, and every answer given in Claude chat, go to an access log in your own database. You get it in full when you stop. |
| What happens when we stop? | We export the full access log. Revoke your Anthropic keys first, because a deleted Key Vault keeps them recoverable for 30 days. If you give us access, we delete the resource group within 30 days and confirm in writing; if not, your team gets the steps. A locked fingerprint container, if you created one, keeps its storage account and resource group until its policy ends. |
One fixed price, with four reviews a year included
Ready, installed, reviewed
- A readiness checklist, plus a privacy pack and an employee notice for your Legal team to approve
- Control Tower for Claude installed in your Azure subscription, about one week once readiness is done
- Six dashboard pages, My Claude for everyone with a license, and asking from Claude chat
- Every chat and session since your Compliance API was enabled, labeled by kind of work, with accuracy checked on a random sample of 100
- A go-live walkthrough for admins and leaders
- Four quarterly value reviews
Renewal
- Continued use of Control Tower for Claude, refreshed every day
- Four quarterly value reviews: what moved, which actions resolved, and next quarter’s top actions agreed
- Label accuracy re-checked every quarter
- Configuration changes agreed in each review, live by the next daily run
No software license fee. You pay Anthropic for labeling and Azure for hosting directly, on your own bills. Nobody at your company has to run it: your team keeps the HR file current and acts on the ranked list, and we handle the rest.
Available on Microsoft Marketplace. Listed after passing Microsoft’s certification review, so your IT team installs it from the Marketplace like any other Azure application. Data Meaning invoices the fixed price directly.
0days00hours00min00sec
Put Control Tower for Claude to work on your own rollout
Each quarter we choose three companies for a free pilot of Control Tower for Claude. Data Meaning charges no fee; you pay only Azure for hosting and Anthropic for labeling, on your own bills. We set it up, then it goes to work, routing each fix to the person who owns it.
Pick a job. See it done with Control Tower for Claude.
Each short demo shows the result first, then the steps behind it. All use Halvane Industries, a fictional company.
See how Claude is used
How Claude is used, and who approved what
What conversations were for, never their text, which systems read Claude data, and who approved requests made in the product.
An AI use register for Claude, kept current
Every department’s uses of Claude, each with an owner, and a use that may be high-risk flagged for Legal.
Close the risks, keep the proof
Claude’s setup, checked against a built-in security policy
High risks like unreviewed changes by connected tools, or admins doing no admin work, each with its fix and owner.
Catch what quietly changed, and track it until someone fixes it
Found each day: people who left holding licenses, a former employee’s key still active, a setting switched off.
Remove people who left, and keep the record
Each person who left but kept a license is flagged, removed once someone confirms, and the removal date recorded.
The quarterly access review, without the spreadsheets
Each manager marks Keep or Remove for their team. Anyone left undecided goes to the admins. Approval locks the review.
When someone asks for proof, it’s already there
Each day’s Claude activity is sealed so changes would show. Outside reviewers see only what you grant, until a set date.
Know and control what Claude costs
One Claude bill, and where lighter models fit
Licenses, usage and apps built on Claude, one bill split by department, plus work on pricier models than needed.
More Claude usage, with the context to decide
Each request reaches the department’s approver or an admin, with a recommended limit. Any no comes with a reason.
Help people use Claude better
Monthly coaching from each person’s own use
A salesperson’s month in Claude, tips drawn from it, each linked to Anthropic’s guide, plus skills picked for their work.
Coaching that comes to each person’s inbox
A Monday email, sent only when tips change, with a button that opens Claude. Each person can turn theirs off.
A monthly race that rewards good habits
Points for good habits, capped so chatting more doesn’t win. Scores stay private, even from managers, unless people share them.
Turn your best Claude users into champions
People near the top of the race get a shareable image of their own habits, plus a suggested post.
What leaders ask us first
Anthropic already gives us a free dashboard.
We already have a FinOps tool, a security tool and training.
Our BI team can build this from the APIs.
Our IT won’t let an outside firm install something in our cloud.
What do we need, and when is it not for us?
You need
- Claude Enterprise on Anthropic’s own service, with the Compliance API turned on
- An Azure subscription to install into
- Microsoft 365, for the emails it sends from a mailbox of your own
- A US workforce
- Legal approval for Claude to read chats in order to label them
- An HR file of every employee with a department and a manager
It is not for you if
- You run Claude only through Amazon Bedrock or Google Vertex
- Your deployment is in the EU, or a works council must approve
- You want to rank or discipline named individuals
- You want a data loss prevention or chat review tool
- You want custom dashboards, Power BI, or several AI providers in one view
How do we know the “what for” labels are right?
Why quarterly reviews? Just give us the software.
Let us show you how it works.
Bring your license count and last month’s bill. We’ll walk you through what Control Tower for Claude would tell you about both.
Data Meaning is an independent consultancy. Claude is a product of Anthropic, PBC.