Viewers can review their own AI usage and spend in Keld Atlas. Changing workspace configuration, adding team members, and viewing organization-wide analytics are administrator tasks.
What Viewers can see
- Your personal Briefing: your own AI usage and spend over time.
- The Optimize preview, including Job Categories.
- Connect tools, where you download Keld Signal.
You will not see organization-wide analytics, the Activity feed, or the administrator-only pages grouped at the bottom of the sidebar (Integrations, Classifications, Teams). Connecting provider accounts, managing teams, creating or editing Dimensions, and exporting data are administrator tasks. If you need any of those, ask an administrator in your organization.
Getting access
An administrator invites you to Keld by email and assigns your role. Open the invite link to join the workspace.
Once you have joined, install Keld Signal so your AI usage is attributed to you. Click Connect tools in the sidebar to download the installer for your platform. For the full walkthrough, see Connect your computer in the Getting Started guide.
Reading your Briefing
Your Briefing covers a timeframe you select: a calendar quarter, the last 7 days, or the last 30 days. It shows:
- A summary of your requests, tokens, and spend for the period
- Spend over time or Usage over time, charted daily
- A breakdown of your work by category and subcategory
- The models and tools you use most
Only your own activity appears here. There is no way to reach another person's data from this view.
If your organization puts you on a flat-rate seat plan rather than usage-based billing, Keld charts your usage in tokens instead of dollars. Your individual prompts are not billed per token under those plans, so a per-person dollar figure would be misleading.
How your usage is classified
Attribution is how Keld maps the data collected from Keld Signal to teams, cost centers, and the categories your organization cares about. It works through Dimensions. Administrators define these; this section explains what they mean when you see them.
Built-in dimensions
Every telemetry event is automatically attributed across six built-in dimensions:
- Team: which team generated the spend
- Cost center: the cost center the spend rolls up to
- Repo: the repository the work happened in
- Model: which AI model was used
- Tool / Source: which tool made the call (Claude Code, Codex, and others)
- Person: the individual principal behind the request
Environment (prod, staging, or dev) is available as an attribute for classification rules rather than as a dimension of its own.
System dimensions
Two rule-based dimensions ship by default:
- CapEx / OpEx: capitalizable build work versus operational spend. See Capex / Opex rules below.
- Business function: a 12-value job-category taxonomy (eng, prod, data, mkt, sales, support, delivery, fin, legal, hr, it, gen). Values are derived from your team by rule. When Keld Signal classifies a prompt's function on your computer with high confidence, that classification takes precedence.
Custom dimensions
Your organization can define additional Dimensions that classify usage by its own rules, for example a "Cost ownership" dimension that groups teams into Product & Engineering, Revenue, and Shared. Custom Dimensions are effective-dated, so historical spend keeps the labels it had at the time.
Administrators create and edit these. For the rule builder and the available attributes and operators, see Observability and Dimensions in the Keld Atlas Administrator Guide.
Capex / Opex rules
Keld Atlas classifies spend as either CapEx (capitalizable build work, per ASC 350-40 / IAS 38) or OpEx (operational spend). This matters for finance teams that capitalize AI-assisted development work.
Default classification
CapEx / OpEx is a system dimension with editable, priority-ordered rules. The defaults, first match wins:
- CapEx when the work's job subcategory is any of the eight capitalizable build activities (
eng.dev,eng.debug,eng.test,eng.review,eng.docs,prod.design,prod.spec,data.prep), matching the ASC 350-40 application development stages - OpEx otherwise, including work with no subcategory
Subcategories come from Keld Signal's on-device classification, so CapEx coverage improves as more Keld Signal installations roll out across your organization. Environment is not part of the defaults but remains available as a rule attribute.
Administrators can reorder, add, or remove these rules, and reset them to the defaults at any time. See the Keld Atlas Administrator Guide.
Budgets
Administrators see a Spend vs. Budget figure on the organization Briefing, measured against the prior period's spend as a baseline. User-defined budget ceilings and alerting are coming later in 2026.
Exports
Exporting Keld Atlas data for use in business intelligence or other applications is an administrator task, available from the organization Briefing. If you need an export, ask an administrator.
Your privacy
See Data handling and privacy in the Keld Atlas Overview. In short: Keld sees usage metadata and masked labels, never your prompt text. Your administrator sees attributed usage and spend across the organization, not your content.