> For the complete documentation index, see [llms.txt](https://documentation.taskmaverick.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.taskmaverick.com/your-organization/people.md).

# People

People are the employees in your organization. Every person gets a profile, a role, and a 6-digit [Personal Code](#personal-code) for the mobile app.

## Why set up People?

Every action in Taskmaverick — Missions completed, Tickets resolved, reports generated — is tracked to a specific person. Adding people is the foundation of your setup.

## How to add a person

1. Go to **People → New Person**
2. Fill in the required fields: name, email or phone number, role, position, and address.
3. Choose whether to send the invitation now or later
4. Save

The new person receives an email with login credentials and a Personal Code.

{% hint style="info" %}
If the person isn't starting yet, uncheck "Send Invite" — they'll be saved with a "Pending Invite" status. Send the invite later when they're ready.
{% endhint %}

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FLLw6mmkCzf1jpC9LdKjS%2Fuploads%2FCYa1IWiWDkiu1KGryfVj%2FPeople.gif?alt=media&token=da1c9a62-ba8a-4d68-b667-3ef7dee6e77e>" %}

After adding, assign them to the right places:

<table><thead><tr><th>Tab</th><th width="428">What to assign</th></tr></thead><tbody><tr><td><a href="/your-organization/units.md"><strong>Units</strong></a></td><td>Which locations they work at</td></tr><tr><td><a href="/your-organization/teams.md"><strong>Teams</strong></a></td><td>Which teams they belong to (assign Unit first)</td></tr><tr><td><a href="/your-organization/ticket-boards.md"><strong>Ticket Boards</strong></a></td><td>Which Ticket Boards they can see and manage</td></tr></tbody></table>

## Personal Code

Every person gets an auto-generated **6-digit Personal Code**. This code is used on mobile to verify identity when claiming Missions, posting On Demand, or performing admin actions.

* Personal Codes **cannot be changed** by the user
* If forgotten, employees can tap **Retrieve Code** on mobile to receive it via email or SMS
* Admins can reset it via **Actions →** [**Reset Personal Code**](#managing-people) on the web

## Roles

| Role                     | Access                                                           | Typical person              |
| ------------------------ | ---------------------------------------------------------------- | --------------------------- |
| **System Admin**         | Full access — create Missions, manage people, configure settings | Owner, Senior Manager       |
| **Organization Manager** | View people, assign and schedule Missions                        | Supervisor, Department Head |
| **Employee**             | **Mobile app only** — complete Missions                          | Frontline staff, workers    |

### What each role can do

<table><thead><tr><th>Action</th><th width="156.59991455078125">System Admin</th><th>Organization  Manager</th><th>Employee</th></tr></thead><tbody><tr><td>Create and edit Missions</td><td>Yes</td><td>No</td><td>No</td></tr><tr><td>Schedule and deploy Missions</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Create and manage People</td><td>Yes</td><td>No</td><td>No</td></tr><tr><td>Create Units, Teams, Groups</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Access Dashboard, Overview, Reporting</td><td>Yes</td><td>Yes</td><td>No</td></tr><tr><td>Configure Organization Settings</td><td>Yes</td><td>View only</td><td>No</td></tr><tr><td>Complete Missions on mobile</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Access the web interface</td><td>Yes</td><td>Yes</td><td>No</td></tr></tbody></table>

Each person needs at least one role. Roles can be combined. A person can be both a System Admin and an Organization Manager.

## Managing people

| Action              | How                                                                          |
| ------------------- | ---------------------------------------------------------------------------- |
| View or edit        | Select the person → **Open** in sidebar                                      |
| Deactivate          | Select the person → **Actions → Deactivate**                                 |
| Delete              | Deactivate first, then **Actions → Delete Person**                           |
| Reset password      | Select the person → **Actions → Remind Credentials**                         |
| Reset Personal Code | Select the person → **Actions → Reset Personal Code**                        |
| Delay onboarding    | Uncheck "Send Invite" at creation → send later via **Actions → Send Invite** |

{% hint style="warning" %}
Only System Admins can create, edit, or delete people. Organization Managers can only view. People cannot be managed from the mobile app.
{% endhint %}

## Pay types

<table><thead><tr><th width="195.3333740234375">Type</th><th>How it works</th></tr></thead><tbody><tr><td><strong>Salary</strong></td><td>Standard access — no time tracking on the app</td></tr><tr><td><strong>Hourly</strong></td><td>Can be clocked in/out. Supports <a href="/your-organization/people/reserve-time.md">Reserve Time</a> for completing Missions off-shift</td></tr></tbody></table>

## Good to know

* Every person needs at least one **login credential** (email OR  phone) and one [**Position**](/your-organization/people/positions.md)
* A person can belong to **multiple organizations** -  they choose which one to access at login
* People can only be managed from the **web**, not the mobile app
* **Pay type** matters: Hourly users support clock-in/out and [**Reserve Time**](/your-organization/people/reserve-time.md). Salary users have standard access.
* Custom fields (gender, birth date, hourly rate, secondary email) can be enabled in [**Organization Settings**](/your-organization/organization-settings.md) **→ User Fields**


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.taskmaverick.com/your-organization/people.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
