Organizations
Organizations are the top-level unit of access and billing in dbdeux. Every workspace, project, member, and AI budget belongs to an organization.
Organization Switcher
A global organization switcher sits in the left navigation panel. If you belong to multiple organizations, click the switcher to change your active context instantly without a full page reload. Each organization shows its display name and a distinct avatar.
The switcher includes a search field that filters the org list as you type, making it fast to find the right org even if you belong to many.
Organization Settings
Organization settings are divided into tabs:
Overview
General information about the organization: display name, creation date, and plan details.
Members
Manage who has access to the organization:
- Invite members by email
- Assign roles: Admin or Member
- Remove members who no longer need access
- View each member's last active date
Admins can manage settings, budgets, and members. Members can access projects and use platform features within the org's budget.
AI Budget
Control how much your organization spends on AI features (Atlas chat, AI code review, test generation):
- Monthly limit: Set a spending cap per month. Usage is tracked in real time
- Usage breakdown: See spend by user and by feature
- Spending alerts: When the limit is reached, AI features pause until the next cycle or until an admin adjusts the limit
- Adjust anytime: Admins can increase or modify the budget at any point
- Export usage: Download a CSV of all AI usage for the current billing period
Notifications
Configure organization-level notification defaults:
- Channels: Slack, email, and webhooks
- Inheritance: Project-level notification settings inherit from the org defaults unless overridden
- Events: Choose which events trigger notifications (build failures, scheduled job completions, CI results)
Service Accounts
Create machine identities and scoped API tokens so external systems can call dbdeux programmatically:
- Create service accounts for CI pipelines, orchestrators, or scripts
- Mint scoped tokens with per-token expiry, rate limits, and optional IP allowlists
- Rotate or revoke tokens at any time
See Service Accounts & API for the full workflow and API reference.
Organization Isolation
All resources are scoped to the active organization:
- Projects: Each project belongs to a single org. Switching orgs shows only that org's projects
- Connections: Warehouse credentials are org-scoped, so different teams can use different warehouses without overlap
- Databases: The Database Explorer shows only connections belonging to the active org
- AI Budgets: Usage and spend limits are tracked independently per org
When you switch organizations, all resources (projects, connections, databases) reload automatically to reflect the new context.
Multi-Organization Support
Users who belong to multiple organizations can:
- Switch between orgs instantly via the nav switcher
- See which org is currently active at all times
- Have separate projects, connections, and budgets per org