> 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.md).

# First-time setup

ShowReward helps a team offer rewards to people who attend its calls. Your team works in the ShowReward dashboard. Participants use a separate reward portal to prepare for their call and, when eligible, claim their reward.

A **project** is your team's workspace. A **campaign** contains the reward amount, call rules and portal content for an offer. A **lead** is a participant. A **closer** is the team member responsible for handling and validating calls. A **Project Manager (PM)** configures the project and manages its team.

## Create an account

1. Open ShowReward and choose **Create one** from the login screen.
2. Choose **Continue with Google**, or enter your **Email**, **Password** and **Confirm Password**, then select **Create account**.
3. For email registration, enter the six-digit code sent to your email address and select **Verify**. Use **Resend** if you need a new code.
4. If you already have an account, choose **Log in**. Use **Forgot password?** to request a reset link when needed.

If your team invited you, use the same email address as the invitation.

## Set up your own project

If the welcome screen asks how you will use ShowReward:

1. Choose **I want to reward attendance**.
2. Enter **Project name**. You can also enter a **Business type**.
3. Review the usage billing information shown on the screen.
4. Select **Create project**.

You become the project owner, shown as **PM Owner**. You can configure the project and invite your team.

## Join an existing team

If you are joining as a closer or sales team member:

1. Ask the project manager for the project ID.
2. Choose **I am a closer or sales team member**.
3. Enter the **Project ID** and, optionally, a short **Message** introducing yourself.
4. Select **Send request**.
5. Wait for the manager to approve it. Use **Refresh status** when available, or reload the page after approval.

**Request sent** means the manager still needs to review your access. **We are completing your access** means the approval is being processed; refresh after a few seconds. For **Access suspended**, contact your project manager.

## Your first setup checklist

For a new project using HighLevel bookings, complete these tasks in order. The [Video tutorials](/showreward-docs/getting-started/video-tutorials.md) page follows the same learning path.

1. [Connect GoHighLevel](/showreward-docs/gohighlevel.md#tutorial-01) and confirm the correct subaccount. Tutorial 01 also covers account and project creation.
2. [Configure your project](/showreward-docs/getting-started/project-settings.md#tutorial-02): choose payout methods, currency, time zone and participant portal language before creating rewards.
3. [Invite your team](/showreward-docs/getting-started/team.md). To import HighLevel users as closers, connect the subaccount first and ask invited users to accept their invitations.
4. [Create your first campaign](/showreward-docs/campaigns.md#tutorial-03), save it, then reopen it to link the HighLevel calendars and apply the booking redirects.
5. Make a test booking and check the participant's portal, campaign and appointment before sending traffic.

You can still configure a project and invite team members manually before connecting HighLevel. The connection is needed for importing HighLevel users and synchronizing its bookings.

After setup, continue with [call validation and reward claims](/showreward-docs/daily-operations/validations.md#tutorial-04), then add [HighLevel workflow automations](/showreward-docs/gohighlevel/workflows.md#tutorial-05) if you need them. Use the [Launch checklist](/showreward-docs/troubleshooting/launch-checklist.md) before going live.

The menus you see depend on your role. **Projects** is a platform administrator screen; project managers normally configure their workspace through **Settings**.

## Related guides

[Configure your project](/showreward-docs/getting-started/project-settings.md) · [Invite your team](/showreward-docs/getting-started/team.md) · [Create a campaign](/showreward-docs/campaigns.md)


---

# 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.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.
