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

# Users

> Invite admin staff, assign one of five fixed roles, and manage invitations from Settings > Users.

**Settings > Users** is where you control who can sign into the admin and what they can do once they're in. Every organization user holds exactly one of five fixed roles. There is no custom-role builder - the role list is the same across every org.

Staff can sign into the admin dashboard with **Google**, **Apple**, **Facebook**, or an email and password. See [Signing in](/reference/sign-in) for all supported methods and how to add a password to an account that was created with a social provider.

## The roles

1Club ships with five canonical roles. Pick the one closest to what the person actually does day-to-day.

| Role           | Typical use                          | What it can do                                                                                                                            |
| -------------- | ------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
| **Admin**      | Owner or main administrator          | Full access to every module (members, marketing, website, operations, billing, analytics, settings).                                      |
| **Manager**    | Club or department manager           | Members and operations full management, marketing manage, analytics manage, inventory manage, billing read and create. No settings.       |
| **Front desk** | Receptionist or front-of-house staff | Members create and read, messaging full, operations create and read, billing read and create. No settings, no analytics beyond their own. |
| **Instructor** | Coach or teacher                     | Manages only their own classes, bookings, and check-ins. Reads their own analytics and messages.                                          |
| **Member**     | End member                           | No admin portal access. Uses the member portal and public apps.                                                                           |

The full permission matrix lives in [Roles and permissions](/reference/roles-permissions).

### Owner flag

Owner is a separate flag on the user, not a sixth role. An Admin can be marked as **owner**, and only owners can delete the organization. Setting **Account owner** in the invite dialog forces the role to Admin.

## The Users page

Open **Settings > Users**. The page is a single table of every organization user with these tabs at the top:

* **All** - everyone in the organization.
* **Admin**, **Manager**, **Front desk**, **Instructor**, **Member** - filtered by role.

Each tab shows a badge with the count. The search box filters by name or email and resets pagination.

Each row shows the user's name, role chip (with an **Owner** chip if applicable), status (Active, Invited, Pending invite, Expired), and join date.

## Inviting a user

Click **Invite user** in the top right. The dialog has two modes:

* **From a contact** - pick someone who already exists in your contact list.
* **New person** - enter first name, last name, and email.

Then choose a role from the five listed above. Tick **Account owner** if this person should be allowed to delete the organization (forces Admin). Submit, and 1Club sends an invitation email. The user appears in the table with status **Invited** until they accept.

If you pick **Instructor** for someone who doesn't yet have an instructor profile, the dialog walks you through creating one before the role is saved. This is so an instructor always has a profile to attach classes, bookings, and schedule slots to.

## Editing, resending, and removing

Click any active user row to open the edit dialog. You can change their role, toggle the owner flag, or (if they have an instructor profile) edit instructor-specific details. You can't edit your own role from this page.

From the row's actions menu:

* **Resend invitation** - available for users still in **Invited** or **Pending invite** state. Sends a fresh email.
* **Set password** - admins can set a password directly for any other user instead of waiting for them to use the reset flow.
* **Delete invitation** - cancels an unaccepted invite.
* **Remove user** - removes an active user from the organization. The contact record (if any) stays; only the organization-user link is deleted.

## Statuses

* **Active** - signed up and using the admin.
* **Invited** - invitation sent, waiting for the user to accept.
* **Pending invite** - the invitation hasn't been sent yet (e.g. created from a contact without an email yet).
* **Expired** - the invitation link expired. Use **Resend invitation** to send a new one.

## What changing a role does

Roles replace each other - there's no permission delta or stacking. When you move someone from Front desk to Manager, their old permissions are dropped and the Manager set is applied wholesale. The owner flag is preserved across role changes (but the system still requires Admin if the owner flag is on).

Existing sessions pick up the new role on their next request. There's no "force sign-out" button - if you need someone out immediately, **Remove user**.

## Related

* [Roles and permissions](/reference/roles-permissions) - The full module-by-module permission matrix.
* [Access control](/settings/access-control) - Door check-in modes, separate from admin roles.
* [API tokens](/settings/api-tokens) - Service tokens for programmatic access; not the same as user invites.