> Markdown version of https://docs.paynow.gg/guides/store-settings/team-members/. The index of all pages is at https://docs.paynow.gg/llms.txt, and any page can be read as Markdown by appending `.md` to its URL.

# Team Members

Invite staff to your store and control what they can do.

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

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

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

## Inviting someone

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

Build the role on the [Roles](https://docs.paynow.gg/guides/store-settings/roles/) page first, then invite.

![The Team Members page with the invite dialog open, showing the email field and role selector.](https://docs.paynow.gg/guides/store-settings/team-members/team-invite-01.png)

Click any member under **Active members** to see their name, when they were added, and their role. From there you can change their role with **Change Role** or remove them from the store with **Kick Member**.

## Pending invitations

Invites nobody has accepted yet are listed under **Pending invitations**, below **Active members**. Seeing the list needs `invite_read`.

| Column      | Shows                                            |
| ----------- | ------------------------------------------------ |
| **Email**   | The address you invited.                         |
| **Role**    | The role they get when they accept.              |
| **Created** | When the invite was created, and who created it. |

Each row has two icon buttons on the right, labelled when you hover them:

* **Copy invite link** copies the link the person uses to join. Send it to them directly if they can't find the invitation email.
* **Cancel invite** withdraws the invite. Confirm with **Cancel Invite**, or back out with **Keep Invite**. A cancelled invite can't be restored, so invite them again if you change your mind.

When someone accepts, they move from this list to **Active members**. Cancel invites nobody is going to use: until then, each one is still a way into your store.

## Joining a store

This part is for the person you invited.

1. Click **Accept Invite** in the invitation email, or open the invite link you were sent.
2. Sign in to PayNow, or create an account first if you don't have one.
3. The dashboard accepts the invite and opens the store you joined.

If you end up on the **Welcome!** screen instead, which is common if you had to create your account first, choose **Join a Store**. Click **Join an existing Store** (on a phone, select the card and tap **Join Store**), paste the full invite link, and submit it.

## 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](https://docs.paynow.gg/guides/analytics/analytics/).

→ [Account Payouts vs Store Payouts](https://docs.paynow.gg/guides/payments-and-payouts/account-vs-store-payouts/)

## 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](https://docs.paynow.gg/guides/customers/bans/) |
| **Support**       | Ticket handlers               | View orders and customers only                                          |

Support staff resolve most tickets with read access alone. The [order timeline](https://docs.paynow.gg/guides/orders-and-subscriptions/orders/) and a customer's [inventory](https://docs.paynow.gg/guides/customers/managing-customers/) 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](https://docs.paynow.gg/guides/integrations-and-commands/api-keys/) that person had access to. Removing them from the team does **not** invalidate a key they copied.
