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

# Organization setup

> Create organizations, switch workspace context, and manage organization details using the current app flows.

An organization is the workspace boundary for connections, pipelines, members, and activity. If you work in multiple organizations, the currently selected one determines what data and settings you see in the app.

## What lives inside an organization

* source and destination connections
* data pipelines
* team members and roles
* activity scoped to that workspace

## Create a new organization

1. Open **Organizations**.
2. Click **Create Organization**.
3. Enter the organization name.
4. Let MantrixFlow generate the slug.
5. Add an optional description.
6. Submit the form.
7. The new organization becomes the current workspace context.

## Important current behavior

Invited users may not be allowed to create organizations. The creation flow checks that permission explicitly, so a team member who joined by invitation should expect to work inside an existing organization unless granted broader access.

## Switch between organizations

1. Open **Organizations**.
2. Review the list of organizations you belong to.
3. Click **Switch** on the organization you want to work in.
4. Return to **Workspace** and confirm you are looking at the correct connections and pipelines.

## Update organization details in workspace settings

1. Click **Settings** in the left sidebar.
2. Click the **Organization** tab.
3. If you are the **Owner**, edit the name, slug, or description.
4. Click **Save changes**.

Non-owners can view organization details but the form is read-only for them.

## Real-world example

A services company keeps one organization for customer-facing production pipelines and a separate one for internal sandbox testing. That separation prevents accidental edits and keeps activity history easier to interpret.

## Practical governance advice

* Use a clear organization name that reflects environment or business unit.
* Avoid mixing unrelated customers or environments in one org.
* Switch context deliberately before creating connections or pipelines.