> ## 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.

# Access

> How Sazabi controls who can see and change your data — roles, project access, sign-in, two-factor, single sign-on, sessions, and the isolation between organizations.

Access to your data is scoped to your organization and enforced on every request. Who can see and change what is governed by roles, project membership, and the credential a request carries.

## Roles

Every member holds one organization role, from most to least access:

| Role | Can do |
| - | - |
| **Owner** | Everything an admin can do, plus changing the organization's name, logo, and organization-wide just-in-time member provisioning. |
| **Admin** | Manage members, teams, billing, integrations, secret keys, webhooks, and project settings. Cannot change the organization's name, logo, or organization-wide just-in-time member provisioning. |
| **Member** | Day-to-day work: connect sources, run investigations, configure tools. Cannot manage organization settings. |
| **Viewer** | Read-only access. |

Permissions are enforced on the server, not only in the interface. See [Access control](https://docs.sazabi.com/manage/access-control.md) for the full permission model.

## Project access

By default, every organization member can reach every project. A project can be restricted so ordinary members can open it only when they are named on it — the restriction is enforced on reads and writes alike, so a member who is not on a restricted project cannot query its data. Organization owners and admins retain organization-level access to every project, including restricted ones.

## Sign-in and two-factor

Members sign in with email or a connected identity provider — Google, GitHub, Microsoft, Slack, or Linear. Sazabi links a social sign-in to an existing account only when the provider has verified the email or domain, which prevents an attacker from claiming an account by asserting someone else's address. Each member can add two-factor authentication under [**Settings > Security**](https://app.sazabi.com/settings/security).

## Single sign-on and SCIM

An organization can have its members sign in through its own identity provider (IdP) over SAML 2.0 or OpenID Connect, so the IdP decides who gets in. Sazabi starts every SSO sign-in itself and refuses responses it didn't ask for. Single sign-on needs a plan that includes it; [contact Sazabi](https://docs.sazabi.com/manage/support.md) to enable it.

* **Enforcement.** An owner can require SSO for a verified email domain. Its addresses can then sign in only through your IdP: email codes, passwords, magic links and social sign-in are refused for them. Turning enforcement on signs out every account on the domain, so everyone signs in again through SSO.
* **Break-glass owners.** Up to two owners, each with an authenticator app, can still sign in with an email code and a second factor while SSO is required, so an IdP outage can't lock your organization out.
* **SCIM deprovisioning.** With SCIM, deactivating someone in your IdP removes them from your organization and ends their dashboard and CLI sessions. SCIM can't remove owners, break-glass owners or the last admin, so removing one of these [protected members](https://docs.sazabi.com/manage/sso/scim.md#protected-members) takes a separate step in Sazabi.

See [Single sign-on](https://docs.sazabi.com/manage/sso.md) to set it up, [SSO enforcement](https://docs.sazabi.com/manage/sso/enforcement.md) for requiring SSO and break-glass owners, and [SCIM provisioning](https://docs.sazabi.com/manage/sso/scim.md) for deprovisioning.

## Sessions

Permissions are evaluated live, on every request, against the member's current role and membership — not against what was true when they signed in. Changing a member's role takes effect on their next request. Removing a member from the organization ends their access to it, and secret keys they created stop working within 30 seconds.

## Tenant isolation

Your organization's data is isolated from every other organization. Sazabi resolves the organization and project for a request from the credential it carries, never from a value the caller supplies, and re-checks membership on every authenticated request. A request for a resource you cannot reach is denied with the same uniform response whether or not the resource exists, so access boundaries do not leak information about other tenants.

## Keys

Two credential types reach your data: **public keys**, which are project-scoped and used only to send telemetry in, and **secret keys**, which grant full read and write — organization-scoped by default, or restricted to a single project at creation so the narrowest credential can be issued. Treat secret keys like production credentials. See [Manage keys](https://docs.sazabi.com/manage/keys.md) for scoping, rotation, and revocation.

## Further reading

> [card] [Access control](https://docs.sazabi.com/manage/access-control.md)
>
> Roles, project access, permissions, and two-factor.

> [card] [Manage keys](https://docs.sazabi.com/manage/keys.md)
>
> Public keys for ingestion and secret keys for API and MCP access.

> [card] [Manage members](https://docs.sazabi.com/manage/members.md)
>
> Invite people, assign roles, and remove access.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.