← Back to docs

Allocate the AI coding account pool by team, department and member with role-based (RBAC) fine-grained grants — provision and revoke instantly.

Team & organization management — seats, roles and department grants

When AI coding grows from individuals to teams, "who can use it, which account, and how much" needs governance. Dawvia lets you allocate the account pool by team, department and member with role-based, fine-grained grants — provision instantly, revoke instantly.

The org model

  • Org / department: draw resource boundaries by org and department; pools are provisioned on demand.
  • Seats: members get pool access as seats, scaled up or down as needed.
  • Roles: role-based permissions (RBAC) with least-privilege you can tune — see

Security & compliance.

Grant and revoke

Seats and grants provision and revoke instantly, so staff changes no longer mean credential leaks:

# Grant pool access to a department
dawvia org grant --team platform --to bob@example.com --role member

# Revoke immediately when a member leaves
dawvia org revoke --to bob@example.com
  • New members get access on join — no password sharing.
  • Departing members are revoked instantly; the account stays in the

account pool for others to reuse.

  • Every grant change is audited, replayable and exportable.

Observability and usage insights

Governance needs measurement. Usage insights make every credit's output measurable:

  • Multi-dimensional usage analytics from team to department to member surface waste and bottlenecks.
  • Live state and call chains are in the remote console.
  • Export usage data to plug into internal billing and chargeback.

Coverage by plan

Team governance by department/member and usage insights start on Team, with everything on Enterprise (including SSO and data residency). Compare on the features overview and the pricing page.

Next steps