> ## Documentation Index
> Fetch the complete documentation index at: https://docs.snapsec.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Organizations & Workspaces

> Understand the multi-tenant hierarchy and boundary isolation between Organizations, Workspaces, and Business Units.

Snapsec structures access and governance using a three-tier hierarchy: **Organization**, **Workspaces**, and **Business Units**.

***

## Hierarchy Model

```mermaid theme={null}
flowchart TD
    Org["Enterprise Organization (e.g., Acme Global)"]
    WS1["Workspace: North America Production"]
    WS2["Workspace: EMEA Operations"]
    WS3["Workspace: R&D / Sandbox"]

    BU1["Business Unit: Retail Banking"]
    BU2["Business Unit: Mobile App"]
    BU3["Business Unit: Core Cloud Infra"]

    Org --> WS1
    Org --> WS2
    Org --> WS3

    WS1 --> BU1
    WS1 --> BU2
    WS1 --> BU3
```

### 1. Enterprise Organization

The top-level entity representing your company subscription.

* Holds global policies (SSO, global SLA rules, billing, global audit logs).
* Managed by **Super Administrators**.

### 2. Workspaces

Logically isolated environments within an organization.

* Ideal for separating distinct operating regions, subsidiary brands, or production vs non-production scopes.
* Users can belong to multiple workspaces with distinct roles.
* Integrations and API keys can be scoped to specific workspaces.

### 3. Business Units (BUs)

Logical groupings within a workspace representing product squads, departments, or cost centers.

* Assets, scans, and vulnerabilities belong to business units.
* Facilitates executive reporting (e.g., "Which BU has the highest SLA breach rate?").


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