Organizations & Projects
Understand how organizations and projects structure your Sazabi workspace and isolate data across environments.
Organizations and projects form the foundation of how you structure your Sazabi workspace. Organizations contain your team and billing, while projects isolate data across environments.
Organizations
An organization is the top-level container for your team. It provides:
- Team membership: All team members belong to an organization.
- Unified billing: Billing is managed at the organization level.
- Shared integrations: Integrations like Slack and GitHub are configured once and shared across the organization.
- Project grouping: All projects live within an organization.
Most teams have one organization. You might create multiple organizations for completely separate business units or clients that require isolated billing and team access.
Projects
Projects provide data isolation within an organization. Each project has:
- Separate logs and traces: Data is isolated by project. Logs sent to one project are not visible in another.
- Independent threads: Conversations and investigations are scoped to their project.
- Project-specific alerts: Alerts are triggered and managed per project.
- Dedicated API keys: Public keys for log ingestion are scoped to a single project.
Use projects to separate environments (production, staging, development) or to isolate distinct services that should not share data.
Creating organizations
Open the organization switcher
Click the organization name in the top-left corner of the dashboard.
Create organization
Click Create organization at the bottom of the dropdown.
Enter details
Enter the organization name and click Create.
Create an organization using the CLI:
sazabi orgs create --name "My Company"The CLI returns the organization ID, which you can use for further configuration.
Creating projects
Go to Settings
Navigate to Settings in the left sidebar.
Open Projects
Click Projects in the settings menu.
Create project
Click New project, enter a name, and click Create.
Create a project using the CLI:
sazabi projects create --name "production"The CLI returns the project ID, which you use to configure API keys and send logs.
Switching contexts
Use the organization and project switcher in the dashboard header to change your active context. The switcher shows all organizations you belong to and all projects within the current organization.
Set the active project for CLI commands:
sazabi config set project <project-id>Or use the SAZABI_PROJECT_ID environment variable:
export SAZABI_PROJECT_ID=proj_abc123
sazabi logs query "level:error"The environment variable takes precedence over the configured project.
Best practices
Keep production data separate from development and staging. This ensures alerts are meaningful and investigations are not polluted with test data.
- One project per environment: Create separate projects for production, staging, and development. This keeps data clean and makes it easier to investigate real issues.
- Use descriptive names: Name projects clearly (e.g., "production", "staging-us-east", "local-dev") so team members know which environment they are viewing.
- Keep production separate: Production logs should never mix with test data. Use a dedicated production project for your live environment.