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

# Invite your team

> Add people to the organization, and have each of them sign in on their own machine.

The quickstart set up one person. Everyone else needs two things: a place in the organization, and their own sign-in on their machine.

Everything done through a sign-in is attributed to that person, so the Work page shows who did what. Never share one person's sign-in or key.

<Steps>
  <Step title="Invite them to the organization">
    Open the account menu at the bottom left, then **Organization settings → Members**, and choose **Invite**. Only owners and admins see Organization settings. The invite email lands them in the organization with the role you chose.

    On OuterLayer Cloud the Free plan allows two members per organization. An invite nobody has accepted yet still counts towards that.

    <Frame caption="The invite dialog on Organization settings → Members.">
      <img src="https://mintcdn.com/outer-layer/WamG4UDZsfczxWBI/images/members-invite-dialog.png?fit=max&auto=format&n=WamG4UDZsfczxWBI&q=85&s=ce3d864f7cc11f4cc9028026caffc376" alt="The Manage users invite dialog with name, email address and role fields and an Invite button" width="1200" height="840" data-path="images/members-invite-dialog.png" />
    </Frame>
  </Step>

  <Step title="They set up their machine">
    Each teammate needs Claude Code, Node.js 22 or later, and their own checkout of the repository. In that checkout they run the same commands as the quickstart:

    ```bash theme={"system"}
    npx @outerlayer/cli login
    npx @outerlayer/cli init --factory <org>/<factory>
    ```

    `login` prints a link and a code, and they approve it in the dashboard. `<org>/<factory>` is your organization's and factory's names, as they appear in the dashboard's address. `init` records which factory this checkout uses, installs the hooks, and installs the OuterLayer skills and MCP server for Claude Code.

    They do not install the GitHub App or link the repository again: the first person did that for the factory. They add an issue on the Work page and build it, exactly as the quickstart shows.

    A second factory needs its own repository connection, even in the same organization. On the Free plan, an organization has one factory.
  </Step>
</Steps>

## Machines are not people

CI and shared machines get their own key too, with only the permissions the job needs. See [Use a key in CI](/api-keys#use-a-key-in-ci).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.