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

# Create an account and organization

> Sign up, verify your email, and set up your first organization.

## Signup

Visit [app.stoutdata.ai](https://app.stoutdata.ai) and click **Sign up**. You'll need a name, a work email, and a password.

After submitting the form, Stout sends a verification link to your email. Click it within a few minutes — unverified accounts can log in but cannot invite others or register boxes.

## Your first organization

Stout automatically creates a personal org on first login, named after you. For most teams, this is where you'll do your work — rename it to match your company from **Settings → General**.

Additional organizations are provisioned by a Stout admin on request. If you need a second org (for a subsidiary, an isolated customer environment, or a staging tenant), reach out and we'll set it up for you. Org slugs are visible in URLs and can't be changed once set, so let us know a stable slug when you ask.

## Joining an existing org by invitation

If a teammate has already set up an org, they can send you an invite from their **Settings → Team** tab. You'll receive a link that brings you to a dedicated acceptance page. Invites:

* Expire after **7 days**.
* Are single-use — once accepted, the link no longer works.
* Carry a role (Owner, Admin, or Member) set by the inviter.

If you already have an account, accepting an invite adds the org to your existing account. If you don't, the acceptance flow doubles as signup.

## Account security

Once you're signed in, open **Settings → Security** to:

* Change your password.
* Enable time-based one-time-password (TOTP) multi-factor authentication with any standard authenticator app. You'll be shown a QR code and a set of backup codes — save the backup codes somewhere safe.
* Upload SSH public keys under **Settings → SSH Keys**. These keys get synced onto every box you have access to, enabling passwordless SSH.

## Roles at a glance

| Role       | Can do                                                                                                   |
| ---------- | -------------------------------------------------------------------------------------------------------- |
| **Owner**  | Everything, including billing, org deletion, and role changes. There must be at least one owner per org. |
| **Admin**  | Manage members, boxes, SSO, integrations, webhooks. Cannot delete the org or change owner assignments.   |
| **Member** | Use assigned boxes — Workbench and Factory — and view their results. Cannot change org settings.         |

Per-box access is layered on top: even an admin can be restricted to a subset of boxes, and members must be explicitly granted access to each box or box group.

See [Organizations](/source/organizations/overview) for the full model.