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

# Onboard your team

> One organization, one invite link, two commands per teammate.

The admin setup target is **under two minutes**. Nobody on the team learns a tool — they run two commands once and talk to their agent from then on.

<Steps>
  <Step title="Create the organization">
    Sign in at [masterskills.dev](https://masterskills.dev) with GitHub or Google (there are no
    passwords) and create your organization. You become its owner.
  </Step>

  <Step title="Configure the invite link">
    On the members page, copy the invite link and choose how it admits people:

    * **Restrict to your email domain** (`@acme.com`) — teammates with matching emails join
      instantly; anyone else falls into the pending queue for your approval.
    * **Leave it open** (`*`) — anyone with the link joins instantly. For trusted channels only.
    * **No domain** — every join waits for admin approval.

    You can change the domain later without rotating the link; rotating is a separate action
    that kills the old link instantly. Details: [Organizations & roles](/concepts/organizations).
  </Step>

  <Step title="Share the link">
    Post it in your team channel. Joins are rate-limited to 50 per day per organization, and a
    pending request grants no access until approved.
  </Step>

  <Step title="Each teammate sets up their machine">
    ```bash theme={"dark"}
    npm install -g @masterskills/cli
    masterskills install
    masterskills login
    ```

    That's their entire onboarding. Every active member sees every skill and kit in the org and
    can publish — publishing is deliberately a member right, not an admin one.
  </Step>
</Steps>

## After onboarding

* **Approve pending requests** on the [members page](/panel/members-and-access); promote trusted people to admin so member management doesn't bottleneck on you.
* **Seed the catalog** — publish the skills the team already passes around, then [bundle them into kits](/guides/build-a-kit) (`@acme/onboarding`, `@acme/backend`, …) so new machines are one `add` away from the baseline.
* **Mark the non-negotiables as required** from each skill's panel page. Required skills appear in everyone's update check — but are still [installed only with the user's consent](/concepts/trust).
* **Watch the audit log** ([settings → audit](/panel/settings-and-audit)) — publishes, installs, membership changes, and device events all land there.

## Plan note

The Free plan covers 3 users with 1 device each — enough to trial the full flow. Rolling out to the whole team is what [Team plans](https://masterskills.dev/pricing) are for.