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 Projects below.
Projects
A project isolates data within your organization: logs, threads, issues, and keys are all scoped to a project. Create one per environment or service you want to keep separate. Creating a project takes about a minute.Create a project
- Dashboard
- CLI
- Open the project switcher and choose to create a project.
- Give it a name and select a region (see Choosing a region). You should see the new project become active once it is created.
- The project provisions its storage; log ingestion and queries become available shortly after.
Choosing a region
A project’s region determines where its data is stored and processed. The region is fixed at creation and cannot be changed — to move data to a different region, create a new project in that region. Choose a region for two reasons:- Data residency — pick a region that satisfies your residency requirements. For EU data, choose a European region.
- Latency — pick a region close to your log sources.
us-west-2. Sazabi supports additional US and European regions; the project creation screen shows the current list, which today includes us-east-1, us-east-2, us-west-1, us-west-2, and several European regions such as eu-central-1 and eu-west-1. If you need a region that is not offered, contact support.
Security model
A project is a shared environment. Everything you connect or expose to it — log sources, sandbox CLI credentials, MCP connectors, linked repositories — is usable by everyone with access to the project: any member can ask the agent questions that read that data and exercise those tools. Grant project access accordingly, prefer least-privilege or read-only credentials when connecting CLIs and connectors, and restrict access to sensitive projects — see Access control.Rename and switch
Rename a project under Settings > Project. Switch between projects with the project switcher; commands and dashboard views apply to the active project. To confirm a new project, check that it appears in the project switcher as the active project, then open Settings > Project and confirm the region shown matches what you selected.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.Further reading
Access control
What each role can do.
Send data
Get logs into your new project.