> ## Documentation Index > Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt > Use this file to discover all available pages before exploring further. # Organizations and projects > The organization is the boundary for your members, billing, integrations, and secret keys; projects isolate data inside it. Create a project, choose its region, and switch between projects. 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**](https://app.sazabi.com/settings/organization). ## What the organization owns * **Members** — everyone in your organization, with a role that governs what they can do. See [Manage members](https://docs.sazabi.com/manage/members.md). * **Billing** — one subscription and one credit balance per organization. See [Billing](https://docs.sazabi.com/manage/billing.md). * **Integrations** — connections to services such as Slack and GitHub are configured once at [**Settings > Integrations**](https://app.sazabi.com/settings/integrations) and shared across the organization. * **Secret keys** — organization-scoped credentials for the API and MCP server. See [Manage keys](https://docs.sazabi.com/manage/keys.md). * **Projects** — all projects belong to the organization. See [Projects](#projects) below. Most teams need one organization. Create a second only when you need fully isolated billing and membership — for example, separate business units or clients. ## 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 > [tab] Dashboard > > 1. Open the project switcher and choose to create a project. > 2. Give it a name and select a **region** (see [Choosing a region](#choosing-a-region)). You should see the new project become active once it is created. > 3. The project provisions its storage; log ingestion and queries become available shortly after. > [tab] CLI > > Create and switch projects with the CLI (install and authenticate per [`/reference/cli`](https://docs.sazabi.com/reference/cli)). The region is set at creation with `--region` and defaults to `us-west-2`. > > ```bash theme={"system"} > sazabi projects create --name "My Project" # Create in the default region (us-west-2) > sazabi projects create --name "EU App" --region eu-central-1 # Create in a specific region > sazabi projects list # List projects in the active organization > sazabi projects use # Set the active project for future commands > ``` > > The project provisions its storage after `create`; 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. The default region is `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](https://docs.sazabi.com/manage/support.md). ### 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](https://docs.sazabi.com/manage/access-control.md). ### Rename and switch Rename a project under [**Settings > Project**](https://app.sazabi.com/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**](https://app.sazabi.com/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**](https://app.sazabi.com/settings/organization); admins cannot. Organizations cannot be deleted from the dashboard. See [Access control](https://docs.sazabi.com/manage/access-control.md) 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**](https://app.sazabi.com/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](https://docs.sazabi.com/fix/connect-coding-agent.md). Organization-wide service connections — Slack, GitHub or Bitbucket for code search, and the rest — are **integrations**, configured at [**Settings > Integrations**](https://app.sazabi.com/settings/integrations), not connected accounts. ## Further reading > [card] [Access control](https://docs.sazabi.com/manage/access-control.md) > > What each role can do. > [card] [Send data](https://docs.sazabi.com/send-data.md) > > Get logs into your new project. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.