> For the complete documentation index, see [llms.txt](https://docs.joingather.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.joingather.org/gather-app-walkthrough/user-management.md).

# User management

### User roles

As an Admin, you can add users to the following access roles.

| Role        | Permissions                                                                                                                                                                                                                        |
| ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Member      | This is the most popular role. Members are your clientele. These users sign up for resources, can reply to group chats, and access resources. They cannot create any new content, and can only edit their own profile information. |
| Coordinator | This role allows for event and resource management, but no user management. This is often other staff in an organization.                                                                                                          |
| Admin       | At the highest level of control, Admins can make new events and resources, invite new users, edit profiles, and create tag-based group chats.                                                                                      |
| Anonymous   | This role has the same access as members, but without the visibility. This ensures their private information is protected and they can't be seen by other users of the app.                                                        |
| View-only   | This role allows viewership without any event sign-ups, messaging, or invite sending. Perfect for stakeholders and observers.                                                                                                      |

### Adding new members

To add a new member, press the Plus icon in the lower right hand corner and select member. From there, add your users name and phone number, select their access role, and send their invite! They will immediately show up in the app, but you'll see an indicator that they have not yet downloaded and logged in.

### Managing members

Once members are active, they'll go through onboarding, where they will fill out answers and (depending on how you've configured your onboarding process with the Gather Team) acquire tags.

If you are an Admin, you can see these answers on an individual's profile and change them as needed. For example, if a member had housing when they completed onboarding, they may have answered "No" to the question "Are you currently in need of housing?". If this changes, you can manually apply the "Needs housing" tag to a member, or change their response to yes. This will let you know the individual's needs at a glance, and ensure they're added to any tag-based communications on the subject.

You can also edit and add information regarding birthday and contact methods.


---

# 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.joingather.org/gather-app-walkthrough/user-management.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.