# Organizations and multi-org

{% hint style="info" %}
**Available in Stratix Premium.** This surface is part of the logged-in workspace at [stratix.layerlens.ai](https://stratix.layerlens.ai). Stratix Public users can browse the catalog but cannot use this feature.
{% endhint %}

Stratix supports users belonging to **multiple organizations**. Each organization is a tenant — separate data, separate ECU balance, separate roles. A user can be a member of many.

## Org switcher

When you belong to ≥2 orgs, the top bar shows an **org switcher**. Click to flip between active orgs. The dashboard, catalog, and Settings refresh for the active org.

## Belonging to multiple orgs

You join an org via:

* **Creating** it (you're auto-added as Admin)
* **Accepting an invitation** (Admin invites you by email)

Email-domain auto-join is supported per-org if the org admin enabled it.

## Active org

At any time, exactly one org is active. The active org determines:

* What's shown in catalog views (the public catalog plus that org's private items)
* Who you appear as in audit logs
* Which ECU balance bills your runs

## Switching consequences

When you switch orgs:

* The dashboard refreshes
* In-flight queries are cancelled and re-issued against the new org
* API keys are scoped per-org; if you have an SDK terminal open, it uses the key for the org it was issued under (not the active dashboard org)

## Multi-org best practices

* **Personal account + work account** are common — Stratix supports both
* For consultants who serve many customers, a separate org per customer keeps audit clean
* Don't share a single org account across people; invite teammates instead

## Where to next

* [Team management](/11.-admin/team-management.md)
* [Settings](/11.-admin/settings.md)
* [Concept: Multi-tenancy](/7.-observe-see-whats-happening/multi-tenancy.md)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.layerlens.ai/11.-admin/organizations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.