Organizations, Departments & Hubs
Model your enterprise as organizations and departments, filter every analytics view by them, and see the two-organization worked example with isolated rosters.
On this page
TL;DR: The platform models your company as organizations containing departments containing users, managed at /admin/enterprises and /admin/access/departments. Every analytics tab filters on all three dimensions, and organizations carry their own plans, seat limits, and budget caps — so two projects can run on one instance without seeing each other.
Organizations
/admin/enterprises is where organizations are created and managed. An organization is the top-level boundary: it owns a plan (seat limit, soft budget threshold, hard monthly cap), a user roster, and its own slice of every analytics view. Access-control rules and gateway entitlements can be scoped to an organization, so what one org's users can reach says nothing about another's.
Departments
/admin/access/departments manages departments inside an organization. Departments are the chargeback and reporting unit: cost attribution, usage dashboards, and access rules all understand them. A user belongs to a department, and the department rolls up to its organization.
Filtering everywhere
The organization / department / user filters are applied identically across every analytics tab — Overview, Usage, Spend, Seats, and Code. Pick an organization and every chart, leaderboard, and export on the page re-scopes to it; narrow further to a department or a single user without leaving the view. See Usage, Adoption & Productivity Analytics for what each tab shows.
Worked example: two isolated projects
A real deployment runs two organizations on one instance:
ai-kit— one delivery group, with its own plan, seat limit, and budget cap.ai-sdlc-delivery— a second group, likewise self-contained.
Each organization has its own roster (populated by admin invites per group), its own analytics scope, and its own ACLs. Nothing overlaps: a user in ai-kit cannot appear in ai-sdlc-delivery reports, spend in one never counts against the other's cap, and entitlements are granted per organization. This is the recommended pattern whenever two initiatives need clean cost and access separation.
Hubs
A Hub is a geographical grouping — a region or location dimension that sits alongside organizations and departments rather than inside them. This is the agreed definition.
The Hub analytics dimension itself — filtering dashboards and reports by Hub — is not yet available. Until it ships, geographic reporting is approximated by mapping locations onto organizations or departments — see the Enterprise Roadmap.
Verified evidence
Every capability on this page is proven by tagged end-to-end tests run against a seeded instance. To replicate: just start, then just e2e-seed --reset, then the command in the table. Screenshots regenerate with just e2e-screens.
| Ref | Verified behaviour | Replicate with |
|---|---|---|
| REQ-006 | Analytics drill down by organization, department, and individual user, with the two seeded organizations fully isolated from each other | just e2e-req REQ-006 |
The same dashboard re-scoped by the organization and department filters.
Narrowing further to one individual user without leaving the view.