> For the complete documentation index, see [llms.txt](https://docs.drizz.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drizz.dev/your-account/organizations-and-access.md).

# Organizations & Access

Every test, module, dataset, app and report belongs to an organization, not to an individual user.

|               |                                                                                      |
| ------------- | ------------------------------------------------------------------------------------ |
| **Created**   | Automatically, when the first person from an email domain signs in                   |
| **Joining**   | Every later sign-in from the same domain joins that organization                     |
| **Sign-in**   | Work email only — personal domains are rejected                                      |
| **Scope**     | Tests, modules, datasets, Memory, registered apps, reports and the wallet are shared |
| **Watch out** | Missing files after sign-in is an organization assignment, not data loss             |

## Prerequisites

* A work email address on your company's domain
* Drizz desktop app installed, or web app access
* Trial or account approved for your organization

## How an organization is created

1. The first person from `yourcompany.com` signs in. Drizz creates the organization.
2. Everyone who signs in from that domain afterward joins the same organization.

There is no self-service organization creation and no invite link.

## What is shared

| Shared org-wide        | Effect                                                                  |
| ---------------------- | ----------------------------------------------------------------------- |
| Tests and modules      | A module written by one member is callable by every member              |
| Datasets               | Includes lockable pools, which lease rows across the whole organization |
| Memory                 | Blocker rules and app context apply to every member's runs              |
| Registered apps        | One upload serves every test plan                                       |
| Reports and recordings | Any member can open any run                                             |
| Wallet                 | One balance, drawn down by every member's runs                          |

A large regression run started by one member reduces the balance available to everyone. See [Billing & tokens](/your-account/billing-and-tokens.md).

## Sign-in domains

| Rule                           | Detail                                                  |
| ------------------------------ | ------------------------------------------------------- |
| Work email required            | Personal domains — Gmail, Outlook, Yahoo — are rejected |
| Domain determines organization | The email domain is the only routing signal             |
| Second company domain          | Creates a second, empty organization                    |
| Contractor on their own domain | Lands in a separate organization from the client team   |

To be moved between organizations, email `support@drizz.dev` with your email address and the target organization name.

## Files missing after sign-in

An empty file list has two causes. Drizz does not delete work on sign-in, and a reinstall does not change organization assignment.

| Cause                                        | Symptom                                  | Fix                                                                     |
| -------------------------------------------- | ---------------------------------------- | ----------------------------------------------------------------------- |
| Account assigned to a different organization | Files from a previous session are absent | Email `support@drizz.dev` with your email address and organization name |
| Trial not yet approved                       | Sign-in succeeds, no content appears     | Email `support@drizz.dev` to confirm approval status                    |

To resolve:

1. Confirm the email address you signed in with, including any alias.
2. Email `support@drizz.dev` with that address and your organization name.
3. Ask which organization the account is assigned to.

## Common mistakes

| What you did                                           | What happens                                                        |
| ------------------------------------------------------ | ------------------------------------------------------------------- |
| Signed up with a personal email                        | Sign-in is rejected. Use your work email                            |
| Reinstalled the desktop app because files were missing | Nothing changes — a reinstall cannot fix an organization assignment |
| Assumed a teammate cannot see your test                | They can. Everything is org-scoped                                  |
| Ran a large plan without checking the wallet           | The run blocks everyone else's runs, not just yours                 |
| Signed in with a second work domain                    | A second, empty organization is created                             |

## Next

* [Billing & tokens](/your-account/billing-and-tokens.md) — metering and the shared wallet
* [Managing apps](/your-account/managing-apps.md) — registering builds for cloud runs
* [Troubleshooting](/reports-and-debugging/troubleshooting.md) — sign-in and network symptoms

***

*Last updated: 6 August 2026*