> 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/groups/group-members.md).

# Group members

{% 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/group-members.md).
{% endhint %}

The **members** of a group are the people who work in it. Each member has a **role** in the group, Admin or User. A User also has **advanced permissions**, which decide what they may do with the group's tasks and settings, and any member can be made **read-only**, which lets them open tasks but change nothing. Admins, and members with the permission "Add or Remove Users in Group", add people from the site's users, invite people who aren't on Snapfix yet (in the apps), change roles and permissions, resend or cancel invitations, and remove members.

## Rules

### Who manages members

* Admins of the group and members with "Add or Remove Users in Group" (`perBusSettingsEditUser`) see the member menu and the add button ([Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md#users), [Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md)). Android also refuses read-only members when they pick a group to add people to; iOS doesn't check that ([Add users to a group](https://docs.snapfix.com/how-the-apps-work/screens/groups/add-users.md#platform-differences)).
* The server lets these change members: site admins, multi-site users of the site, and the group's admins and holders of "Add or Remove Users in Group" who aren't read-only (api\_php\_live\_v2 @ ef3c4319f6, `app/Policies/BusinessPolicy.php:101-117`). So site and multi-site staff manage any group's members, also when they aren't in it ([Multi-Site Console](https://docs.snapfix.com/product/features/console/multi-site-console.md)).
* A member with "Add or Remove Users in Group" can change their own role and permissions, also to Admin.
* The apps' membership sync writes membership rows with no rights check.

### Roles, read-only and permissions

* A member is an Admin or a User. An admin has every permission; the web hides the permission boxes for admins. The group's admins who aren't read-only are listed on [Group purpose](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-purpose.md).
* "Read-only user" makes the membership inactive: the member opens the group's tasks and changes nothing, and the list shows them as read-only ([Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md#users)). iOS doesn't open the group editor for read-only members.
* A User's advanced permissions are, by their web labels: "Create New Task", "Change task to red", "Change task to yellow", "Change task to green", "View All Tasks", "Hide Task Notes", "Delete or Archive Tasks", "Access Attachments", "Assign Users", "Generate Reports", "Create Planned Tasks", "Group Settings Access" and "Add or Remove Users in Group" ([User role & permissions](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md#dialogs-and-sheets)). Each is a key in the `permissions` of the [member object](https://docs.snapfix.com/engineering-reference/api/groups.md#member-object). The table also holds tag permissions, which the dialog no longer offers, so on the web only admins edit tags \[[ASK-79](https://github.com/snapfix/docs/blob/main/ASK.md#ask-79-who-should-edit-a-groups-tags)].
* On the web, roles and permissions change in "User role & permissions"; its "Save" stays disabled until something changes. iOS and Android have their own permission sheets.
* Without "View All Tasks", a member sees only the tasks they created, follow or are assigned to ([group\_taskcount](https://docs.snapfix.com/engineering-reference/api/groups.md#post-actiongroup_taskcount)).
* "Create New Task" also gates the web's Chat button on the task list \[[ASK-48](https://github.com/snapfix/docs/blob/main/ASK.md#ask-48-should-every-member-be-able-to-open-a-task-groups-chat-from-the-task-list)]. "Create Planned Tasks" is the planner permission, and the apps also want "Create New Task" \[[ASK-51](https://github.com/snapfix/docs/blob/main/ASK.md#ask-51-which-permissions-should-planned-tasks-need)].

### Adding people

* The web's "Add users to this group" lists the site's users who aren't in the group, sorted by name. "+" adds one person, and "Done" adds the selected people ([Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md#dialogs-and-sheets)). The web always adds them as "User" (api\_php\_live\_v2 @ ef3c4319f6, `app/Http/Requests/v1/BusinessUser/CreateUserBusinessRequest.php:27-36`).
* A membership the web adds starts with "Create New Task", the three status changes, "View All Tasks", "Access Attachments" and "Assign Users" on, from the server's model and table defaults (`app/Models/UserBusinessModel.php:39-46`, [`tPri_UserBusiness`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userbusiness.md)). The table's own defaults leave "View All Tasks" and "Access Attachments" off; the model turns them on.
* Adding someone who was removed before restores their old membership as a "User" (`app/Services/UserAssetBusinessService.php:46-60`).
* The server doesn't check that an added person belongs to the group's site.
* The apps add people from [Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md): Snapfix users of the user's network, a new person by phone number or email, or an invitation. A person already in the group can't be picked again ("This user is already added to this group."). iOS also lists the phone's contacts there; Android offers contacts only on the add step after a new group is saved \[[ASK-78](https://github.com/snapfix/docs/blob/main/ASK.md#ask-78-should-androids-users-tab-add-screen-offer-phone-contacts)] ([Add from phone contacts](https://docs.snapfix.com/how-the-apps-work/screens/groups/phone-contacts.md)). The apps also have a pick-a-group-first flow ([Add users to a group](https://docs.snapfix.com/how-the-apps-work/screens/groups/add-users.md)).
* Allowing contacts access also uploads the phone's address book.
* When the plan has no users left, the apps refuse a new user with "No new users left in this account."; its "Learn more" link opens a missing help page.
* When the web adds people, each gets a push saying so (`app/Http/Controllers/v1/Versions/v1_0/App/UserAssetBusinessController.php:53-65`).

### Invitations

* The apps invite people who aren't on Snapfix: Android through its invite sheet (SMS, email or the share sheet) and "Invite via link", iOS through its contacts and new-user flows ([Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md#actions)). The web can't send a new invitation \[[ASK-76](https://github.com/snapfix/docs/blob/main/ASK.md#ask-76-should-the-web-send-invitations-or-should-its-unused-invitation-code-go)].
* Pending invitations are listed under "Invited users" on the web, with "Resend invitation" and "Delete" ([Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md#users)). An invited person sets a password and joins the site and its groups ([Joining a site](https://docs.snapfix.com/product/features/onboarding/join-site.md)).
* A member who has a temporary password and never signed in shows with the warning "This user has already been added to the group but has never used the Snapfix mobile or web app. Please ask this user to login to Snapfix."

### Removing

* The web's member menu calls it "Delete" and asks "Are you sure you want to delete user {name} from the group?"; it removes the person from this group only, not from Snapfix. The name is pasted into the dialog as markup.
* The membership is deleted; the person stays assigned to their tasks \[[ASK-75](https://github.com/snapfix/docs/blob/main/ASK.md#ask-75-should-removing-a-member-take-them-off-their-tasks)].
* The web, iOS and Android refuse to remove or demote the group's only admin. The server doesn't check this ([Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md#actions)).
* Whether ordinary members should see each other's contact details is open: the web shows them when the site shows contact data, and the server sends them to every member either way \[[ASK-72](https://github.com/snapfix/docs/blob/main/ASK.md#ask-72-should-every-member-get-the-other-members-and-invitees-contact-details)].

## Flow

```mermaid
flowchart TD
  users["Group settings: Users"] --> add["Add users"]
  add --> site["Pick the site's users: + or Done (web), Find user to add (apps)"]
  add --> invite["Apps: invite someone not on Snapfix"]
  site --> member["Member as User, with default permissions"]
  invite --> pending["Invited users: resend or delete"]
  pending --> joined["Joins the site and the group"]
  joined --> member
  member --> edit["Edit: role, read-only, permissions"]
  edit --> last{"Only admin?"}
  last -- "yes" --> refuse["Refused by the clients"]
  last -- "no" --> saved["Saved"]
  member --> remove["Delete: confirm, then removed from the group"]
```

## Platforms

| Capability                          | Web                                                                                                                                             | iOS                                                                                        | Android                                                                                                                                                        |
| ----------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Add from the site's users           | "Add users to this group"                                                                                                                       | [Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md) | [Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md)                                                                     |
| Add from phone contacts             | No                                                                                                                                              | On the same screen                                                                         | Only after a new group is saved \[[ASK-78](https://github.com/snapfix/docs/blob/main/ASK.md#ask-78-should-androids-users-tab-add-screen-offer-phone-contacts)] |
| Invite someone not on Snapfix       | No \[[ASK-76](https://github.com/snapfix/docs/blob/main/ASK.md#ask-76-should-the-web-send-invitations-or-should-its-unused-invitation-code-go)] | Contacts and new-user flows                                                                | Invite sheet and "Invite via link"                                                                                                                             |
| Pending invitations                 | Listed, with resend and delete                                                                                                                  | Not traced                                                                                 | Not traced                                                                                                                                                     |
| Role, read-only and permissions     | "User role & permissions"                                                                                                                       | Permission sheet                                                                           | Permission sheet                                                                                                                                               |
| Remove a member                     | "Delete", after a confirmation                                                                                                                  | Yes                                                                                        | Yes                                                                                                                                                            |
| Refuse to remove the only admin     | Yes                                                                                                                                             | Yes                                                                                        | Yes                                                                                                                                                            |
| Pick a group first, then add people | No                                                                                                                                              | Yes                                                                                        | Yes                                                                                                                                                            |

## Screens

* [Group settings](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-settings.md): the Users section, the member menu, "User role & permissions", and invitations on the web.
* [Add users to a group](https://docs.snapfix.com/how-the-apps-work/screens/groups/add-users.md): the apps' group picker before the Users tab.
* [Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md): the apps' picker for members and invitations.
* [Add from phone contacts](https://docs.snapfix.com/how-the-apps-work/screens/groups/phone-contacts.md): the contacts step on Android.
* [Create a new group](https://docs.snapfix.com/how-the-apps-work/screens/groups/create-group.md): the creator becomes the admin.
* [Group purpose](https://docs.snapfix.com/how-the-apps-work/screens/groups/group-purpose.md): the group's admins.

## API and data

* [Groups API](https://docs.snapfix.com/engineering-reference/api/groups.md): the members and pending invitations come with [GET /v1/app/businesses/{uuid}](https://docs.snapfix.com/engineering-reference/api/groups.md#get-v1appbusinessesuuid); [GET /v1/app/businesses/{uuid}/users](https://docs.snapfix.com/engineering-reference/api/groups.md#get-v1appbusinessesuuidusers) lists the members for task and chat screens. Both send every member's contact fields ([member object](https://docs.snapfix.com/engineering-reference/api/groups.md#member-object)).
* [Users API](https://docs.snapfix.com/engineering-reference/api/users.md): the web's calls:
  * `GET /v1/app/parents/{uuid}/users`: the site's users to add from.
  * `POST /v1/app/user/add-relation/{item_uuid}`: add people as "User".
  * `PUT /v1/app/user/{user_uuid}/update-relation/{item_uuid}`: change the role, read-only state and permissions.
  * `DELETE /v1/app/user/{user_uuid}/remove-relation/{item_uuid}`: remove a member.
  * `PUT /v1/app/user/{invite_id}/invite-resend/{item_uuid}` and `DELETE /v1/app/user/{invite_id}/invite-cancel/{item_uuid}`: resend or cancel an invitation.
  * The apps invite with `?action=group_invitation`, and sync memberships through php-apis.
* Tables: [`tPri_UserBusiness`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userbusiness.md) (membership, role, read-only state and permissions), [`group_invite`](https://docs.snapfix.com/engineering-reference/db/tables/group_invite.md) (pending invitations), [`tPri_UserParent`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_userparent.md) (site membership) and [`tPri_User`](https://docs.snapfix.com/engineering-reference/db/tables/tpri_user.md) (people).

## Depends on

* [Groups](https://docs.snapfix.com/product/features/groups/groups.md): the group the members belong to.
* [Site users](https://docs.snapfix.com/product/features/console/site-users.md) and [Multi-Site Console](https://docs.snapfix.com/product/features/console/multi-site-console.md): site-wide management of a person's groups and roles.
* [Joining a site](https://docs.snapfix.com/product/features/onboarding/join-site.md) and [Email and SMS links](https://docs.snapfix.com/product/features/account/email-links.md): what an invited person does to join.
* [Tasks](https://docs.snapfix.com/product/features/tasks/tasks.md) and [Creating tasks](https://docs.snapfix.com/product/features/tasks/task-creation.md): assignments, and the task permissions.
* [Push notifications](https://docs.snapfix.com/product/features/notifications/push-notifications.md): the push to a person who is added.
* [Chat](https://docs.snapfix.com/product/features/chat/chat.md): a task group chat follows the group's members.

## Edge cases

* **Offline (apps):** the members come from the device copy. Adding Snapfix users from the network is saved on the device and synced; looking up a new person and sending invitations need a connection ([Find user to add](https://docs.snapfix.com/how-the-apps-work/screens/groups/find-user.md#states)).
* **Missing permission:** without "Add or Remove Users in Group" there is no member menu and no add button; the apps' group picker says "You don’t have the right permissions to create or edit users in this group. Reach out to the group admin to review your permissions." ([Add users to a group](https://docs.snapfix.com/how-the-apps-work/screens/groups/add-users.md#actions)).
* **Limits reached:** see [Adding people](#adding-people). No member limit per group is documented.
* **Removed members:** adding them again restores their membership; their task assignments stay \[[ASK-75](https://github.com/snapfix/docs/blob/main/ASK.md#ask-75-should-removing-a-member-take-them-off-their-tasks)].
* **Last admin:** refused by the clients, not by the server.
* **Deleted group:** the server leaves its memberships as they are \[[ASK-80](https://github.com/snapfix/docs/blob/main/ASK.md#ask-80-what-should-deleting-a-group-do-to-its-tasks-and-members)].
* **Several sites:** the web offers only the group's site's users; the server doesn't check the site.
* **Time zones and integrations:** none for members.


---

# 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/groups/group-members.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.
