> ## Documentation Index
> Fetch the complete documentation index at: https://partner-help.letsdothis.com/llms.txt
> Use this file to discover all available pages before exploring further.

# User access

> How to invite team members to your dashboard, and what each role can see and do.

<Info>
  Only **Admin** users can invite new team members and change existing roles.
</Info>

Roles and permissions let you give team members, contractors, or partners access to your dashboard without sharing your own login. Each person gets exactly the access they need — nothing more. You can scope access to your entire organization or to a single event.

## Your first admin account

When Let's Do This sets up your account, the first Admin user is created as part of that process. That person can then invite others from **Settings → Roles and permissions**. If you're not sure who the Admin on your account is, contact Let's Do This support.

## Roles

Each person you invite is assigned one role. The role controls which sections of the dashboard they can see and what actions they can take.

| Role                       | What they can do                                                                     |
| -------------------------- | ------------------------------------------------------------------------------------ |
| **Admin**                  | Full access — can manage events, view all financials, invite users, and change roles |
| **Editor**                 | Can create and edit events and view financial data, but cannot manage users          |
| **Editor (No Financials)** | Same as Editor, but financial data (revenue, payouts) is hidden                      |
| **Viewer**                 | Read-only access to all sections, including financials                               |
| **Viewer (No Financials)** | Read-only access with financial data hidden                                          |

Roles can also be scoped to a single event — for example, **Event Editor** or **Event Viewer (No Financials)**. Event-scoped users can manage or view that event only; org-level sections like Memberships, Settings, and account-wide reports are not available to them.

## Inviting a team member

<Steps>
  <Step title="Go to Roles and permissions">
    In the sidebar, open **Settings** and select **Roles and permissions**.
  </Step>

  <Step title="Open the invite dialog">
    Click the **Invite** button in the top-right corner of the page.
  </Step>

  <Step title="Choose a role">
    Select the role that matches the level of access you want to give. If you want to limit access to one event, choose an event-scoped role and then pick the event on the following screen.

    <Tip>
      Not sure which role to pick? Select **View role descriptions** in the invite dialog for a summary of what each role can access.
    </Tip>
  </Step>

  <Step title="Enter their email address">
    Type the email address of the person you want to invite and click **Invite**.
  </Step>

  <Step title="Share the access link">
    A unique access link is generated. Copy it and send it to the person directly — by email, Slack, or however you prefer. They use the link to claim their access and set up their account.
  </Step>
</Steps>

## Managing existing users

<Warning>
  Only Admin users can change roles or remove access for other users.
</Warning>

The **Roles and permissions** page lists every person who has access to your account, along with their email address, role, and login type. From the table you can:

* Change a person's role
* Remove a person's access entirely

## What event-restricted users see

A user with an event-scoped role (Event Editor or Event Viewer) sees only the event they were given access to. When they log in:

* The event list shows only their assigned event
* **Create new event** is visible but disabled
* Org-level sections — Settings, Memberships, and account-wide reports — are not accessible
* Attempting to reach those sections shows an access-denied message

This makes event-scoped roles a good fit for third-party timing companies, photographers, or contractors who need access to one event's startlist or data exports without seeing the rest of your account.