Teams & departments
As an enterprise deployment grows beyond a single team, a flat user structure becomes impractical. Teams — or departments — allow administrators to group users so that asset visibility, approval workflows, operational reporting, and cost tracking mirror the real structure of your organization.
Why organizational structure matters
Section titled “Why organizational structure matters”Structuring users into teams provides essential intermediate governance between individual isolation and company-wide exposure:
- Scoped operational visibility — team members and department leads access analytics, activity logs, and shared workspace assets relevant to their specific department rather than the entire enterprise.
- Targeted approvals — high-impact workflow actions and marketplace publishing requests route directly to the designated department lead or line manager.
- Legible cost accounting — system usage, API run costs, and model execution expenses roll up cleanly by department, making AI adoption as accountable and transparent as any standard departmental budget.
Without team structure, workspace access is strictly binary — either private to a single user or visible to the entire company. Teams provide the structured middle layer that enterprise operations require.
Organizing teams to match your chart
Section titled “Organizing teams to match your chart”Administrators can align platform teams directly with existing corporate structures:
- Flexible department grouping — structure teams by functional department (such as Sales, Marketing, or Customer Support), business unit, or project task force.
- Membership-driven scoping — assigning a user to a team shapes their default marketplace views, team dashboard metrics, and shared asset access automatically.
Team membership works alongside a user’s role. For what each role can see and do, see the Capability matrix.
Capabilities unlocked by teams
Section titled “Capabilities unlocked by teams”Grouping users into departments enables three key platform capabilities:
- Scoped analytics dashboards — department leads monitor tool adoption, agent run counts, and activity trends specific to their team.
- Department-specific approval routing — workflow sign-offs, connector access requests, and publishing requests route directly to the appropriate departmental manager. See Approval workflows.
- Departmental cost allocation — financial administrators track, analyze, and set budget limits on AI consumption per department. See the Cost Optimization Center.
A quick example: multi-departmental governance
Section titled “A quick example: multi-departmental governance”Consider an enterprise deployment spanning Sales, Customer Support, and Finance:
- Structure setup — an Enterprise Admin creates three distinct teams: Sales, Support, and Finance.
- Delegated oversight — the Support lead monitors support agent performance and ticket summarization budgets; the Finance lead receives approval requests for financial reporting workflows.
- Executive visibility — the CFO and IT administrators maintain global oversight across all three teams, reviewing company-wide adoption and aggregate expenditure from a single admin console.
Structural governance comparison
Section titled “Structural governance comparison”| Organizational scope | Asset visibility | Approval routing | Cost tracking |
|---|---|---|---|
| Individual user | Private to the creator | — | Tracked per individual account |
| Team / department | Shared across team members | Routed to department lead | Aggregated per department budget |
| Organization-wide | Visible in company marketplace | Routed to Enterprise Admin | Aggregated for global IT spend |
Next steps
Section titled “Next steps”- Set up departmental cost tracking → Cost Optimization Center
- Configure manager sign-offs → Approval workflows
- Review user role matrices → Capability matrix