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

# Inviting People

> Invite teammates, app users, and collaborators, give each an existing role, and manage their access.

## Overview

This page covers the day-to-day work of giving people access: inviting a teammate, adding a user to your live app, and managing who has what. You pick from roles that already exist, so there's nothing to build.

If you instead need to **create roles or decide what each one can do**, that's a separate job covered in [Members & Roles](/members-and-roles).

There are three kinds of people you'll add, and each lives in a different place:

| Who they are                 | Where they sign in                                      | Add them under                            |
| ---------------------------- | ------------------------------------------------------- | ----------------------------------------- |
| **Teammate / staff**         | The Stardeck dashboard, plus the apps their role allows | Organization **Settings → Members**       |
| **App user**                 | Only your deployed app, never Stardeck                  | The app's **Settings → Deployment Users** |
| **Collaborator / developer** | Builds and manages one app inside Stardeck              | The app's **Settings → Project Members**  |

<Note>
  The public pages of a deployed app are open to anyone by default, so no invitation is needed. You
  only invite people when they need to sign in to do something authenticated.
</Note>

***

## Inviting a teammate to your organization

Teammates are the people who work inside Stardeck with you. They sign in to the dashboard and use the apps their role allows.

<Steps>
  <Step title="Open Members">
    Go to [**Settings → Members**](https://www.stardeck.ai/dashboard/settings?tab=members) in your
    organization dashboard.
  </Step>

  <Step title="Invite a member">
    Click **Invite member**, enter their email address, and choose the **role** they should get. If
    you're not sure, leave it on the default. Every organization has a "role for new members" that's
    applied automatically.
  </Step>

  <Step title="Send">
    They receive an email invitation. It shows up as **pending** until they accept; you can **revoke**
    it from the same tab if you need to.
  </Step>
</Steps>

<Tip>
  Adding a lot of people at once? Use **Bulk invite** to paste in several email addresses in one go.
</Tip>

### Which role should I pick?

Pick the closest fit from the roles your organization already has. You don't need to understand every permission. The built-in ones:

| Role       | Good for                                           |
| ---------- | -------------------------------------------------- |
| **Admin**  | Full access, including settings and billing.       |
| **Member** | Standard team access, the usual choice.            |
| **Viewer** | People who mostly need to look, not change things. |

Your organization may have more roles than these. Each person has exactly **one** organization role, and you can change it later. For the full list, or to create a role, see [Members & Roles](/members-and-roles).

<Note>
  Inviting teammates may require a plan that supports more than one user. If your plan is single-user,
  you'll see an upgrade prompt on the Members tab.
</Note>

### Giving a teammate access to a specific app

Some roles are **App-only**: the person can't open the Stardeck dashboard and only uses the apps you assign them. It's the setup for frontline staff like cashiers or drivers. (See [App-only access](/members-and-roles#access-level-team-vs-app-only) for how it works.)

<Steps>
  <Step title="Invite or find the member">
    Invite them with an App-only role (or pick an existing member on the Members tab).
  </Step>

  <Step title="Expand their row">
    Click to expand the member to reveal **App access**.
  </Step>

  <Step title="Assign the app and a role">
    Add the specific app(s) they need and choose which role they hold inside each one.
  </Step>
</Steps>

They'll be able to sign in to exactly those apps, and nothing else.

### Changing a role or removing someone

All from the same [**Members**](https://www.stardeck.ai/dashboard/settings?tab=members) tab:

* **Change someone's role** — pick a different role from the dropdown next to them.
* **Make someone an admin** (or remove admin) — use the shield action on their row.
* **Remove a teammate** — revoke their access from their row. They lose dashboard and app access.

***

## Inviting users to your deployed app

App users (also called **Deployment Users**) are the people who use your live app. They sign in to the app only, and never see Stardeck, your code, or your settings.

<Steps>
  <Step title="Open the app's users">
    In the app, go to
    [**Settings → Deployment Users**](https://www.stardeck.ai/projects/~/dashboard/config/users).
  </Step>

  <Step title="Invite a user">
    Add their email and choose a **deployment role** for them (for example, **Admin** or **User**).
  </Step>

  <Step title="Manage them later">
    From this tab you can change a user's role, resend or revoke invitations, and remove access.
  </Step>
</Steps>

<Tip>
  Don't want to invite users one by one? Turn on **self sign-up** so people can register themselves.
  Anyone who signs up gets the app's **Default Sign-Up Role**. See
  [User Authentication](/user-authentication) to enable it.
</Tip>

***

## Inviting a collaborator to help build an app

Collaborators (or **Project Members**) are people who help you build and manage one app inside Stardeck. They can touch its code, settings, and deploys. This is the right choice for an external developer, freelancer, or partner agency working on a single app.

Invite them from the app's
[**Settings → Project Members**](https://www.stardeck.ai/projects/~/dashboard/project/members).

<Note>
  A Project Member works on **one app**. If you want someone to build across all your apps, invite
  them as an organization teammate with a Team role instead (see above).
</Note>

***

## Next steps

<CardGroup cols={2}>
  <Card title="Members & Roles" icon="shield-halved" href="/members-and-roles" horizontal>
    Create roles and decide exactly what each one can do
  </Card>

  <Card title="User Authentication" icon="key" href="/user-authentication" horizontal>
    Turn on self sign-up and choose sign-in methods for your app
  </Card>

  <Card title="Identities" icon="address-book" href="/identities" horizontal>
    Manage the customers and contacts your agents and apps work with
  </Card>

  <Card title="Publishing & Deployment" icon="rocket" href="/publishing-deployment" horizontal>
    Deploy your app so people can sign in to it
  </Card>
</CardGroup>