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

# Invite your team and manage access

Open **Closers** as a Project Manager or administrator. This page includes both closers and project managers, plus their call performance.

For the video walkthrough, open [Tutorial 02: Configure Your Project and Invite Your Team](/showreward-docs/getting-started/project-settings.md#tutorial-02) and follow the invitation and HighLevel import chapters.

## Understand the roles

| Role                 | Typical work                                                                    |
| -------------------- | ------------------------------------------------------------------------------- |
| Closer               | Work with assigned leads and validate their calls.                              |
| Project Manager (PM) | Configure campaigns and settings, and manage the project's team and operations. |
| PM Owner             | Manage the project with additional authority over other project managers.       |
| Admin                | Manage projects across the ShowReward platform.                                 |

A PM promoted or invited by another PM cannot invite or promote more PMs. The owner and administrator have additional controls, so available actions can differ between managers.

## Invite a team member

1. Select **Invite closer**.
2. Enter **Full name** and **Email**. Add **Phone** if useful.
3. Choose **Closer** under **Role**, or **Project Manager** if that option is available to you.
4. Select **Invite**.
5. Ask the teammate to register or sign in using that exact email address.

An invitation appears as **Invited** until the account is activated. If the email does not arrive, use **Resend** beside the member. A recorded invitation and successful email delivery are separate steps, so checking the row is useful.

## Import closers from GoHighLevel

Connect the intended HighLevel subaccount under **Settings → Calendar integrations** before starting. Open **Closers** as a Project Manager or administrator with permission to invite members.

1. Select **Import from GoHighLevel**.
2. Review the users returned from the connected HighLevel account.
3. Select the people who handle calls as closers.
4. Select **Invite selected users as closers**.
5. Check the resulting team rows and ask each invited person to register or sign in using the invited email address.

The imported users are linked to their HighLevel identities. **Invited** means the invitation still needs acceptance; it does not confirm active access. Use **Resend** when needed. Importing users does not modify their HighLevel user accounts.

## Approve a request to join

When someone applies using your project ID, their request appears under **Access requests** on **Closers**. Review their name, email and message, then choose **Accept** or **Reject**.

If a decision remains in **Resolution pending**, use the displayed retry action to finish processing it.

## Change access

* Use **Disable** to suspend an active member's access. Use **Activate** to restore an eligible disabled member.
* For an unused invitation, choose **Delete** and confirm **Revoke invitation**. The record is retained to preserve appointments and history.
* Use **Promote to PM** for an active closer when you have permission. Confirm the change in the dialog.
* The PM Owner or administrator can use **Demote to closer** for another PM. The member then returns to managing assigned leads. The owner cannot be demoted through this action.

If ShowReward reports that an email already belongs to another project, ask your administrator to resolve that membership instead of creating duplicate invitations.


---

# 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://showreward.gitbook.io/showreward-docs/getting-started/team.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.