Workspace admin

Workspace types

Every workspace is one of two types. The type shows as a badge next to the workspace name in the header.

• New workspaces start as individual workspaces where both types are offered. Onboarding asks how many people will use Token Meter; any answer other than “Just me” turns the workspace into a team workspace.
• Turning an individual workspace into a team workspace: the owner chooses Turn this into a team workspace in the workspace menu in the header. Paying for a team plan in Settings › Billing does the same.
• The change is one way. A team workspace never goes back to an individual one. No data moves; the workspace moves onto the team Free plan.

Plans and billing

Settings › Billing shows the current plan, this month's spend and events against the plan's caps, and the plans you can move to. Only the owner, CTO and CFO can open it. Payments are handled by Dodo Payments as merchant of record; Token Meter never stores card details.

What the plans unlock

• Single sign-on is included with Scale and Enterprise, for team workspaces. See Single sign-on.
• Seats (how many people can be members) come with the plan. The number is shown as Included under Settings › Team.
• Individual workspaces have their own plans: Freelancer (free: 5 projects, 10 client contacts, 5 provider connections) and Freelancer Pro (unlimited projects, contacts and connections, full portal branding). A team plan bought from an individual workspace turns it into a team workspace.

Changing plan

• Upgrade to … opens a Dodo checkout the first time you pay. When a subscription already exists the change is immediate and prorated. The plan on the page updates once Dodo confirms the payment.
• Downgrade to … and Cancel subscription take effect at the end of the current billing period. There is no refund for the rest of the period.

Roles

Every member has one workspace role. Three of the roles also carry the billing role, which is what opens billing, the plan and workspace-wide settings.

Team lead is not set on the person directly: a member becomes a team lead when they are made lead of at least one team. An admin who also leads a team stays an admin.

What each role can do

Anything an admin can do, the owner, CTO and CFO can do too.

Invite people and manage seats

Team workspaces only. There are two places to invite from:

• Settings › Team › People (/settings/organization/people), for admins. Invite a Member or a Team Lead; a team lead needs a team, a member can be left with No team and added to one later.
• Settings › Team › Teams, for the owner, CTO and CFO. The same form, plus CTO and CFO for the owner.

Teams and team leads

A team groups people and their usage. Each team has a name, a slug, an optional description, a monthly budget, members and a team lead. The owner, CTO and CFO manage teams in Settings › Team › Teams.

1. Choose Add team. Enter the Team name, the Monthly budget (USD) and, optionally, a Team lead email to invite the lead at the same time.
2. Open the team to see its usage for the last 30 days (metered spend, month to date against the budget, requests, tokens, top models and spend by member).
3. Under Members, add existing workspace members as Member or Team lead, change their team role or remove them from the team. Removing someone from a team keeps their workspace seat. To add someone new, invite them to the workspace and choose the team.
4. Under Attribution & targets, add Tag aliases and set an Adoption target (Target % from 1 to 100 and Window (days) from 7 to 365), tracked on the Adoption page.

How usage reaches a team: events are matched on the team tag. A value equal to the team's slug belongs to that team; any other value needs an alias (below). See Attribution for how to set the tag.

To delete a team, remove all its members and revoke its ingest keys first, then use Delete team and type the team's slug. Usage already recorded stays under its tag.

Access aliases

Settings › Team › Access aliases (/settings/teams) decides which usage a team's lead and members can see. Admins make changes here; team leads can view the page.

• Team Tag Aliases map a raw team tag value (for example growth-eng) onto a team. Without one, usage tagged with a value that isn't a team's slug is not shown to that team's lead or members; it is never attributed to a different team.
• Service Ownership maps an OpenTelemetry service name to the team that owns it. Calls from that service that arrive without a team are attributed to that team. A team value on the event always wins.
• Directory attribute mapping chooses which Google Workspace fields fill people's department and job role. Values an admin types on the People page override directory sync.

Business units

Business units roll metered AI spend up into your cost centres. They live in Analytics › Business units, for admins and above.

1. Choose Add a business unit. Give it a Name, an optional Cost-centre code, and choose what it Sits under (one level of nesting).
2. Choose Add a rule: Match on Team, Project, Product, Feature, Customer, Plan, Environment or Action, enter the Value exactly as it appears on Analytics › Spend, choose the unit and, optionally, a Priority. When a request matches several rules, the lowest priority number wins.
3. Largest unallocated spend lists the biggest values no rule matches, each with an Assign button.
4. Under Unallocated spend, choose whether spend no rule matches stays as its own line or is spread across units by their share (shown in its own column, never mixed into measured spend).
5. Optionally set a Monthly budget (USD) on a unit (alerts at 80% and 100%, and when the month is projected to go over) and turn on the Monthly chargeback email, sent on the 1st to admins and to the owner, CTO and CFO.

Rules apply to every month, past and present. Export CSV downloads the month shown. Every change is recorded in the audit log.

General settings

Settings › General is for the owner, CTO and CFO. It has three tabs.

• Details: Workspace name and Billing email, changed with Edit. The Workspace slug is fixed at creation.
• Defaults: the Default environment stamped on events that arrive without one. It also holds the router's two spend limits, Per request, at most and Per run, at most, with the presets Open (no limits), Balanced ($5 request, $25 run) and Strict ($0.50 request, $5 run). Changes apply to new traffic within a minute.
• Audit log: the 100 most recent workspace-level changes (settings, members, invites, teams and denied access) and receipts for completed permanent purges. The full audit trail of AI requests and provider activity is in Governance › Audit log.

Other settings tabs

• Data sources: provider credentials, accounts, negotiated rates and billing imports. Individual workspaces on the free Freelancer plan can have up to 5 provider connections.
• Notifications: where alert rules and budgets deliver: email addresses and Slack or Discord webhooks.
• System: a link to Metric definitions (what each dashboard number means and how it is calculated) and, for admins, Background jobs: syncs and imports for your workspace with their status, failures in the last 24 hours and last success.

Switch workspaces

You can belong to several workspaces. If you belong to more than one, sign-in asks you to Choose a workspace. To switch later, open the workspace menu in the header and choose another workspace. Switching only ever lists workspaces you are a live member of.

Where it is offered, the same menu has Create workspace: a name and a type. You can own up to 5 workspaces.

Delete a workspace

Only the owner can delete a workspace, from Settings › General › Details › Danger zone.

1. Choose Delete workspace and type the workspace slug to confirm.
2. The workspace disappears for everyone straight away. Within a day its keys are revoked and its members are signed out of Token Meter, including any other workspaces they belong to.
3. The workspace and its data are permanently deleted after 30 days.

What a new admin sees

• Overview (/dashboard): this month's spend, requests and tokens, daily spend, spend by provider, tracked spend compared with the provider bill, and the most recent traces.
• Analytics: tabs for Spend, Usage, Activity, Bill, Use cases and Business units. Spend, Bill, Use cases and Business units are for admins; members open on Usage.
• Traces: every individual call, or the same traffic rolled up by action, with the full trace behind each request.
• Improvements: cost and routing opportunities measured from your own usage and billing data.
• Data health: every gap in your data named in dollars: readiness, coverage, unattributed and unpriced usage, data quality, the ingest pipeline, the model catalog, requests and (for admins) provider usage.

Members and team leads see the same pages scoped to their own usage or the teams they lead.