> For the complete documentation index, see [llms.txt](https://guides.paynow.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.paynow.gg/store-settings/team-members.md).

# Team Members

Bringing people in to help is necessary as a store grows. Doing it carelessly is how stores get drained.

*Dashboard → Access → Team Members. Needs `invite_manage`.*

{% hint style="danger" %}
**Give the narrowest role that lets someone do their job.** Only owners should have full access. A moderator answering tickets needs to view orders and customers, not to issue refunds, edit products or create API keys. Every extra permission is a way for a mistake or a compromised account to cost you money.
{% endhint %}

## Inviting someone

1. Go to **Access → Team Members**.
2. Click **Invite New Member** in the top right.
3. Enter their **email address**.
4. Select the **role** to apply.
5. Send.

Build the role on the [Roles](/store-settings/roles.md) page first, then invite.

<figure><img src="/files/PMMjoBQizWlTQuhyAlny" alt="The Team Members page with the invite dialog open, showing the email field and role selector."><figcaption></figcaption></figure>

Click any member to see their name, when they were added, and their role. From there you can change their role or remove them from the store.

## Payouts is not grantable

No role grants access to Payouts. It is owner-only rather than permission-gated, so even a fully-privileged Administrator cannot open it. If someone needs revenue visibility without payout access, give them `stats_revenue_read` for [Analytics](/analytics/analytics.md).

→ [Account Payouts vs Store Payouts](/payments-and-payouts/account-vs-store-payouts.md)

## A sensible starting structure

| Role              | Who                           | Roughly what they need                                                  |
| ----------------- | ----------------------------- | ----------------------------------------------------------------------- |
| **Administrator** | Co-owner you trust with money | Products, refunds, marketing, team                                      |
| **Moderator**     | Trusted staff                 | View orders, customers, subscriptions; issue [bans](/customers/bans.md) |
| **Support**       | Ticket handlers               | View orders and customers only                                          |

Support staff resolve most tickets with read access alone. The [order timeline](/orders-and-subscriptions/orders.md) and a customer's [inventory](/customers/managing-customers.md) answer most questions without any write permission.

## Reviewing access

Do this quarterly, and immediately when someone leaves.

1. Remove members who are no longer involved, on the day they leave.
2. Check nobody has accumulated permissions from a temporary task.
3. Reset any [API keys](/integrations-and-commands/api-keys.md) that person had access to. Removing them from the team does **not** invalidate a key they copied.