Organization units
Organization units let admins mirror how your company is structured: departments, teams, or nested groups, and then assign people into that structure and set shared spend limits on any unit. Spend rolls up the branch; a parent spend limit is a hard stop for everyone underneath.
π Note: Organization units roll out as they are enabled for organizations in production. If you do not see Organization units in organization settings yet, contact your Devs.ai representative. Organizations with no unit budgets configured keep today's personal and organization spending limits unchanged.
What you can doβ
- Create nested departments and teams, then rename or move them as the org changes
- Assign members to a unit (including bulk CSV import)
- Set shared monthly and/or daily spend limits on a unit so the whole branch shares one budget
- See rolled-up spend versus limit next to the unit you manage
- In Analytics, filter by organization unit and see which units drive tokens and dollar cost
Open Organization Unitsβ
- Sign in as an organization administrator (or a role with Organization units permission).
- Open Organization in the sidebar.
- Click Organization Units.
Use the Organization units page to build your org hierarchy and assign members. Shared budgets are managed separately under Usage & Billing (see Shared spend limits).
Build the hierarchyβ
Start with Create your first unit, or use Add unit when the tree already exists.
For each unit, set:
- Name β for example, Engineering
- Unit type β the label shown in the tree, such as Department, Team, or Division
You can:
- Add a child unit under an existing node
- Edit a unit's name or type
- Move a unit to a different parent (or drag to reorder)
- Delete a unit. If the unit has children, deleting removes the whole subtree. Members of deleted units are not removed from the organization. They become unassigned.
Assign membersβ
Select a unit to view and manage its Members.
- A person can belong to only one unit. Assigning them to another unit moves them from their current one.
- People who are not in any unit appear under Unassigned. Unassigned members keep the existing personal and organization billing rules.
- You can search users to add, filter the member list, and unassign someone to move them back to Unassigned.
Import from CSVβ
Use Import to create missing units, align unit types, and assign members by email in bulk.
Required columns (one row per membership):
name,unit_type,parent_name,email
- Leave
parent_nameempty for top-level units. - Leave
emailempty to create or update a unit without assigning a member. - Unknown emails are skipped; users already in another unit are reassigned.
- Duplicate rows for the same unit are merged (first
unit_typewins).
Example:
name,unit_type,parent_name,email
Engineering,Department,,alice@acme.com
Engineering,Department,,bob@acme.com
Platform,Team,Engineering,carol@acme.com
After the import finishes, review the report for created units, type updates, assignments, warnings, and errors.
Shared spend limitsβ
Hierarchy and membership live on Organization Units. Shared budgets live under Usage & Billing:
- Open Usage & Billing (or your organization's billing / cost controls).
- Open the Org Units tab.
- Select a unit in the tree to manage its budget.
If you have no units yet, the tab points you to create them first (Manage hierarchy in Organization units).
For each unit you can set Monthly and/or Daily limits. Spend shown for a unit rolls up from every member assigned to that unit and to units beneath it.
How parent and child limits interactβ
- A parent's limit is a hard cap on its entire branch. When the parent is exhausted, descendants stop spending even if a child still has room under its own limit.
- A child can have its own limit (including unlimited at that layer), but it cannot spend more than its parent allows.
- People who are not assigned to a unit keep the existing personal and organization billing rules.
Unit budgets typically require dollar-based billing and the billing permissions for your role. If the Org Units tab is missing, confirm Organization Units is enabled for your organization and that your role can manage billing limits.
Analytics by organization unitβ
When Organization Units is enabled, the Analytics dashboard in Organization scope can filter by Organization unit and show top units by tokens or cost. That view is for reportingβset budgets on Usage & Billing, not on Analytics.
Permissionsβ
Managing the hierarchy and memberships requires the Organization Units permission (organization level). Setting shared spend limits also requires access to organization usage / billing controls. See User permissions.
Related topicsβ
- Analytics β org-unit filters and cost views.
- User permissions β who can manage Organization Units and billing.
- Organization model settings β which models members can use (separate from unit spend).