> For the complete documentation index, see [llms.txt](https://docs.snapfix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snapfix.com/product/features/console/site-users.md).

# Site users

{% hint style="info" %}
Draft, written by an agent and not yet checked by a person ([how to read these docs](https://docs.snapfix.com/how-to-read.md)). [Source on GitHub](https://github.com/snapfix/docs/blob/main/product/features/site-users.md).
{% endhint %}

**Site admins** bring people into a **site** and manage them. On the web they invite people by email or phone, typed in or from a spreadsheet, choose their **groups** and roles, set five **site permissions**, make people site admins, remove them, and block their devices. In the apps they invite by email, phone or a one-time QR code, change groups and roles, resend or revoke invitations, and block a person or their devices. Group admins on the web can see the active users and add people. In the **Multi-Site Console**, the same work covers every site of a **multi-site**, plus each person's multi-site membership ([Multi-Site Console](https://docs.snapfix.com/product/features/console/multi-site-console.md)).

## Rules

### Who sees what

* On the web, the Users tab opens for role "Admin" and group admins. Group admins see the active list and can add people; for them the groups, permissions and devices are read-only, and they get no "Invited" tab, no site admin box and no "Remove User" ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md)).
* In the apps, every member sees the active list. Only site admins get the add button, the Invited tab and the user sheet \[[ASK-130](https://github.com/snapfix/docs/blob/main/ASK.md#ask-130-should-members-who-are-not-admins-see-the-sites-user-list-in-the-apps)]. iOS shows the side menu item "Users" to site admins only; every member reaches the list from the "Users" tab of [Site details](https://docs.snapfix.com/product/features/console/site-details.md) ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md)).
* The server's site user lists do not check that the caller belongs to the site ([Users API](https://docs.snapfix.com/engineering-reference/api/users.md)).

### Adding people

* On the web, "Add New Users" takes up to 10 people at a time. Each needs a first and a last name (up to 30 characters each), an email (up to 70 characters) or a phone number, and at least one group with a role. "Save Users" adds the entry to "Added users", and "Add Users" sends the invitations. Duplicate checks look only at that list ([Add New Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#add-new-users-web)).
* A contractor is added on the web with an email address only. A contractor cannot be made a site admin and has no site permissions or group roles ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#add-new-users-web)).
* A spreadsheet upload on the web adds people with no groups and never as contractors, and the 10-person limit does not apply to it \[[ASK-128](https://github.com/snapfix/docs/blob/main/ASK.md#ask-128-should-users-added-from-a-spreadsheet-get-no-groups), [ASK-129](https://github.com/snapfix/docs/blob/main/ASK.md#ask-129-should-the-spreadsheet-upload-keep-the-10-user-limit)] ([Upload Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#upload-users-web)).
* In the apps a site admin adds a person by phone, by email, or with a one-time QR code that the new person scans ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#ios-and-android), [Joining a site](https://docs.snapfix.com/product/features/onboarding/join-site.md)).
* An invited person stays on the Invited tab until they join. A resend is offered once the last invitation is 72 hours old. On the web the invite link can be copied; revoking asks first on the web and on Android ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#actions)).

### Roles and permissions

* "Make a Site Admin" (web) saves at once, with no confirmation \[[ASK-136](https://github.com/snapfix/docs/blob/main/ASK.md#ask-136-should-make-a-site-admin-ask-before-saving)]. Making someone a site admin turns on all five permissions. It is not offered for contractors, invited people or the signed-in user ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#web-1)).
* The five site permissions are "Create New Group", "Manage Tags", "Edit Tag Folders", "Create | Edit | Delete Checklists" and "Enable AI Auto-Assign". Each switch saves at once. "Enable AI Auto-Assign" shows only when the site has AI suggestions on. The switches are disabled for site admins, who have them all ([Site permissions](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#site-permissions-web)).
* The checklist permission does not open the Site Console's Checklists tab, which goes by the site role \[[ASK-131](https://github.com/snapfix/docs/blob/main/ASK.md#ask-131-should-the-create--edit--delete-checklists-permission-let-users-manage-checklist-templates)] ([Checklist templates](https://docs.snapfix.com/product/features/checklists/checklist-templates.md)).
* Each task group gives a person the role "Admin" or "User". Asset registers are not listed. The web's groups card lists every live task group of the site, or only the groups a group admin runs ([Groups and roles](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#groups-and-roles-web)).
* A failed group save shows the API's message, but the card then reloads as if it had worked. On Android a failed group change shows nothing.
* Any multi-site user can change the site roles of the multi-site's sites, themselves included, because the server checks only the multi-site membership; whether that is intended is open \[[ASK-123](https://github.com/snapfix/docs/blob/main/ASK.md#ask-123-who-may-manage-a-multi-site-and-change-its-members-site-roles)] ([`PUT /user/{userUUID}/site/{siteUUID}/permission`](https://docs.snapfix.com/engineering-reference/api/console.md#put-useruseruuidsitesiteuuidpermission)).

### Removing and blocking

* "Remove User" (web) asks first, then removes the person from every group of the site and from the site ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#web-1)).
* Neither app offers removal or a password reset: both are in the code but always hidden, and Android's reset sheet would send nothing \[[ASK-138](https://github.com/snapfix/docs/blob/main/ASK.md#ask-138-should-the-apps-let-site-admins-remove-users-and-reset-their-passwords)] ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#ios-and-android)).
* The apps block or unblock a whole person, not offered for the signed-in user. The web blocks only devices ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#ios-and-android)).
* Site admins block and unblock devices on every platform; the web asks first. A blocked device's tokens are blocked, so its next renewal fails ([Sign-in](https://docs.snapfix.com/product/features/account/sign-in.md)).

## Flow

```mermaid
flowchart TD
    open["Open Users"] --> list["Active or Invited list"]
    list --> add["Add people"]
    add --> typed["Web: up to 10 typed, with groups and roles"]
    add --> sheet["Web: from a spreadsheet, no groups"]
    add --> app["Apps: phone, email or QR code"]
    typed --> invite["Invitations sent by email or SMS"]
    sheet --> invite
    app --> invite
    list --> person["Open a person"]
    person --> groups["Groups and roles"]
    person --> perms["Web: site admin and site permissions"]
    person --> devices["Block or unblock devices"]
    person --> remove["Web: remove from the site. Apps: block the person"]
```

## Platforms

| Capability                      | Web                             | iOS           | Android                |
| ------------------------------- | ------------------------------- | ------------- | ---------------------- |
| See the active list             | Role "Admin" and group admins   | Every member  | Every member           |
| Invited tab                     | Role "Admin"                    | Site admins   | Site admins            |
| Add by email or phone           | Up to 10 at a time; contractors | Yes           | Yes                    |
| Add from a spreadsheet          | Yes, with no groups             | No            | No                     |
| Add with a QR code              | No                              | Yes           | Yes                    |
| Groups and roles                | Groups card                     | Sheet         | Sheet                  |
| Site admin and site permissions | Yes                             | No            | No                     |
| Block or unblock devices        | Yes                             | Yes           | Yes                    |
| Block a whole person            | No                              | Yes           | Yes                    |
| Remove from the site            | Yes                             | No (hidden)   | No (hidden)            |
| Reset a password                | No                              | No (hidden)   | No (hidden)            |
| Resend or revoke an invitation  | Yes, plus "Copy invite link"    | Yes           | Yes, revoke asks first |
| Search                          | On the server                   | On the device | On the device          |

## Screens

* [Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md): the Users tab on the web, and the Users page in the apps.
* [Users (multi-site)](https://docs.snapfix.com/how-the-apps-work/screens/console/multi-site-users.md): the Multi-Site Console's Users tab.

## API and data

* [Users API](https://docs.snapfix.com/engineering-reference/api/users.md): the user lists, invitations, group memberships and roles, removal, and user and device blocks.
* [`GET /user/{userUUID}/site/{siteUUID}/permission`](https://docs.snapfix.com/engineering-reference/api/console.md#get-useruseruuidsitesiteuuidpermission) and [`PUT /user/{userUUID}/site/{siteUUID}/permission`](https://docs.snapfix.com/engineering-reference/api/console.md#put-useruseruuidsitesiteuuidpermission): the site admin role and the five permissions.
* [`POST /v1/app/generate-dynamic-link`](https://docs.snapfix.com/engineering-reference/api/account.md#post-v1appgenerate-dynamic-link): the apps' QR invitation link.
* Tables: [`tPri_User`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_user.md) (the person), [`tPri_UserParent`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userparent.md) (their row on the site, with the admin type and the permissions), [`tPri_UserBusiness`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userbusiness.md) (group memberships and roles) and [`group_invite`](https://docs.snapfix.com/engineering-reference/db/tables/group_invite.md) (invitations).

## Depends on

* [Group members](https://docs.snapfix.com/product/features/groups/group-members.md) and [Groups](https://docs.snapfix.com/product/features/groups/groups.md): the groups people join and their roles.
* [Joining a site](https://docs.snapfix.com/product/features/onboarding/join-site.md): what an invited person does with the link or the QR code.
* [Sign-in](https://docs.snapfix.com/product/features/account/sign-in.md): blocked people and devices cannot sign in.
* [Site details](https://docs.snapfix.com/product/features/console/site-details.md): where the apps' Users tab sits, and the "Display contact info" switch.
* [Site tags](https://docs.snapfix.com/product/features/console/site-tags.md), [Checklist templates](https://docs.snapfix.com/product/features/checklists/checklist-templates.md) and [Snapfix Recommends](https://docs.snapfix.com/product/features/ai/snapfix-recommends.md): what the site permissions unlock.
* [Username logins](https://docs.snapfix.com/product/features/console/username-logins.md): staff without an email address or phone number.
* [Multi-Site Console](https://docs.snapfix.com/product/features/console/multi-site-console.md): the multi-site's users and their site roles.

## Edge cases

* **Contractors:** they have no access card and no site admin box; when every person added is a contractor, the dialog closes and the "Active" tab opens ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#web-1)).
* **The signed-in user:** their own row has no site admin box, "Remove User" or invite buttons on the web, and no block in the apps.
* **No devices:** the Devices tab says "No devices listed, or the user has not logged on since Snapfix device management implemented." ([Users](https://docs.snapfix.com/how-the-apps-work/screens/console/users.md#states)).
* **Offline (apps):** the user actions need a connection; Android checks first and shows its connection alert.
* **Leaving a multi-site:** a person removed from the whole multi-site keeps their site admin rows on its sites \[[ASK-127](https://github.com/snapfix/docs/blob/main/ASK.md#ask-127-should-removing-a-user-from-a-multi-site-also-remove-the-site-admin-roles-it-gave)] ([`DELETE /multisite/{multisiteUUID}/user/{userUUID}`](https://docs.snapfix.com/engineering-reference/api/console.md#delete-multisitemultisiteuuiduseruseruuid)).
* **Multi-site invited list:** the Multi-Site Console's "Invited" tab shows the invitations of the site stored as current only.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.snapfix.com/product/features/console/site-users.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
