Teams & departments

Once you have more than a handful of users, flat is no longer good enough. Teams (or departments) let you group people so that visibility, approvals, and reporting follow the shape of your real organization.

Why structure matters

Teams are what make “team-level visibility” possible. A team member sees activity and analytics for their team, not the whole company; an admin sees everything. Approvals and cost tracking can roll up by team, so each department’s AI usage is legible on its own. Without structure, everything is either private or company-wide, with nothing in between — and enterprises live in the in-between.

Organizing teams

Group people to mirror your org chart — by department, function, or business unit, whatever matches how work and budgets are actually divided. A person belongs to a team, and that membership shapes what they see and how their usage is grouped.

What teams unlock

Scoped visibility — team-level dashboards and activity.
Department approvals — route sign-offs to the right team. See Approval workflows.
Cost tracking by team — see and manage spend per department. See Cost controls.

A quick example

A company sets up Sales, Support, and Finance as teams. Each team lead sees their own team’s adoption and spend; Finance’s approvals route to the Finance lead; and the CFO, as an admin, sees the whole picture. The structure makes AI usage as accountable as any other departmental budget.