Organizations
The organization is the boundary for your members, billing, integrations, and secret keys.
An organization is the top-level container for your team in Sazabi. It is the boundary for membership, billing, integrations, and secret keys. Projects live inside an organization; data is isolated per project, but members, billing, and integrations are shared across the whole organization.
Manage your organization under Settings > Organization.
What the organization owns
- Members — everyone in your organization, with a role that governs what they can do. See Manage members.
- Billing — one subscription and one credit balance per organization. See Billing.
- Integrations — connections to services such as Slack and GitHub are configured once at Settings > Integrations and shared across the organization.
- Secret keys — organization-scoped credentials for the API and MCP server. See Manage keys.
- Projects — all projects belong to the organization. See Manage projects.
Most teams need one organization. Create a second only when you need fully isolated billing and membership — for example, separate business units or clients.
Profile and settings
Only the owner can change the organization's name, logo, and organization-wide just-in-time member provisioning under Settings > Organization; admins cannot. Organizations cannot be deleted from the dashboard. See Access control for the role rules.
Connected accounts
Connected accounts are personal, not organizational. Each member links their own provider accounts (GitHub, Google, and others) under Settings > Connected accounts; those grants belong to that user and are not shared with the organization. Connecting a coding agent to Sazabi is a personal step too — see Connect your coding agent.
Organization-wide service connections — Slack, GitHub or Bitbucket for code search, and the rest — are integrations, configured at Settings > Integrations, not connected accounts.