> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/settings/workspace/users.md).

# Users

### Active Users

The **Users** tab lists everyone with access to your workspace. Each user shows:

* **Name and email**, their identity in the system
* **Role**, their permission level

The search bar at the top finds users by name or email.

#### Removing a User

Click **Delete** next to a user to revoke their access. They lose the ability to sign in to your workspace.

***

### Inviting a New User

Click **Invite user** in the top-right corner to add a team member, then fill in:

* **Role**, the permission level for this user
* **Email**, the address the invitation goes to

Click **Invite user** to send it. The recipient gets an email with instructions to join your workspace.

#### Accepting an Invitation

The invitation email carries a link with a one-time ticket. Your invitee clicks it and two things happen:

* They land on the hosted login screen to sign in, or to create their password, with the invited email address.
* The ticket travels along with that sign-in. It assigns the role you picked and adds them to your workspace.

{% hint style="info" %}
**Note:** the role arrives only through the emailed link. A normal sign-in without the ticket assigns nothing. Ask invitees to use the link in the email rather than going straight to the app.
{% endhint %}

***

### Pending Invitations

The **Invitees** tab lists every outstanding invitation. Each entry shows:

* **Email**, the invited person's address
* **Invited at**, the time you sent it
* **Expires at**, the time the link stops working

An expired invitation carries an **Expired** tag. Delete an expired or unwanted invitation and send a new one.

{% hint style="info" %}
**Tip:** an invitation that never arrived shows in the Invitees tab. Confirm it went out, then delete and resend.
{% endhint %}

***

### A Note on Roles and Manual Sends

Sending an email or SMS straight from a person's page passes two different checks, and the two do not line up.

* The **button** appears for anyone whose role can manage people.
* The **server** that sends the message expects the caller to hold settings-modify access.

A user with people-management access and no settings-modify access sees the button anyway, and the server can still refuse their send. That mismatch is the likely cause of a rejected manual send. Grant the settings-modify level, or send as an admin.