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

# Create an account

> Self-enroll with your email. Company emails are recognised automatically. One passwordless account works everywhere.

WAT Rooms is self-service. You sign yourself up, no admin invite needed. Accounts are passwordless: you log in with a code sent to your email.

## Sign up

<Steps>
  <Step title="Open the app">
    Go to [app.wat.com](https://app.wat.com) and choose to log in.
  </Step>

  <Step title="Enter your email">
    Type your email address. We send you a 6-digit one-time code.

    <Note>
      Use your **company email address**. WAT keeps a list of resident company domains, and any email on one of those domains can sign up directly. Personal addresses (gmail and the like) work only if a WAT admin has added them individually.
    </Note>
  </Step>

  <Step title="Enter the code">
    Enter the 6-digit code from your email. That's it — if your email is on WAT's resident list, your account is created on the spot.
  </Step>

  <Step title="You're in">
    Your account is created as a member. You can now see the rooms and book them. Returning members just log in with email plus the 6-digit code — even if the list changes later.
  </Step>
</Steps>

## Not on the list?

If your email isn't on WAT's resident list, the refused sign-in automatically files an **access request** with the WAT admins: there is nothing else you need to do. An admin reviews it and either accepts your address (you receive a *"You've been accepted"* email and can log in right away) or accepts your whole **company domain**, which also lets your colleagues sign up on their own. Trying again later doesn't hurt, but it doesn't speed things up either: the request is already pending.

Admins manage requests, residents, and allowed domains in the web app under **Admin → Users & Access** (the *Requests* tab).

## One account, everywhere

The same account drives the web app, the [`wat` CLI](/cli), the [skills plugin](/plugin), and the [MCP server](/mcp-server). There is nothing to re-register: log in once per tool. (The MCP server uses an OAuth sign-in instead of an API key: the same email code, and the same resident-list gate on first enrollment.)

## Mint an API key for the CLI and agents

The CLI and the skills authenticate with an API key tied to your account.

* The easiest way is `wat login`, which mints and stores a key for you automatically (see the [CLI page](/cli)).
* You can also mint and revoke keys yourself in the web app under **Account → API keys**. Use this to issue a dedicated key for an agent or a script, or to revoke a key you no longer trust.

<Note>
  Treat an API key like a password: it carries your member role. Store it only where it's needed and revoke it from **Account → API keys** if it leaks.
</Note>