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

# Team members

> Run your store with other people: invite owners, admins and members, and group members into teams that open only the parts of the store they need.

Your store can have more than one person behind it. Invite a co-founder as an
**owner**, an assistant as an **admin**, and freelancers as **members** who see
only what their team needs. Team members is part of the **Growth** plan and up.

## Roles

| Role | Can do |
| - | - |
| **Owner** | Everything, including payouts, plan and billing, adding or removing owners, and deleting the store. Payout actions ask owners to confirm it's them (the same check you already use). |
| **Admin** | Everything except money and ownership: no payouts, billing or owner changes. Admins can invite admins and members and edit teams. |
| **Member** | Only the areas of their teams. |

A store always keeps at least one owner. Nobody can change their own role or
access: ask another owner.

## Teams and areas

A team is a named group of members with a list of areas they can open:

| Area | Includes |
| - | - |
| Products and store design | Products, reviews, refund policies, creator page, domains |
| Orders, customers and refunds | Orders, subscriptions, customers, license keys, exports |
| Emails and automations | Emails, templates, subscribers, automations |
| Discounts, upsells and affiliates | Discount codes, order bumps, the affiliate program |
| Analytics | Overview and sales numbers |
| API keys and webhooks | API keys, webhooks, request logs |

Payouts, billing and ownership are never part of a team. A member in several
teams gets every area of those teams.

<Steps>
  <Step title="Create a team">
    In **Settings → Team → Teams**, click **New team**, name it (for example
    *Support*) and tick the areas it can open.
  </Step>

  <Step title="Invite people">
    Click **Invite people**, enter their email, pick a role and, for members,
    their teams. They get an email with a link that works once and expires in
    7 days. You can **Resend** (a new link, 7 more days) or **Cancel** it.
  </Step>

  <Step title="They accept">
    The link opens a page that says who invited them and what they'll be able
    to do. They sign in (or create an account) **with the invited email** and
    confirm that address, then the store opens.
  </Step>
</Steps>

## Seats

Each plan includes a number of seats, you included: **Growth 5, Pro 15,
Scale 50, Volume unlimited**. An open invite holds a seat until it's accepted,
canceled or expires.

If you move to a plan with fewer seats, the newest members beyond your seats
are **paused**, not removed (owners and admins are kept first). They come back
on their own when you upgrade again. You can always remove people, cancel
invites or pause someone, whatever your plan.

## Switching stores

People who work on more than one store get a **store switcher** under the
logo in the sidebar. It lists your own store and the stores you were invited
to, and remembers your choice in this browser. The sidebar shows only the
pages your role and teams open.

## Changes take effect right away

Removing, pausing or re-scoping someone applies on their very next click.

## Activity log

**Settings → Activity log** shows who did what, newest first: invites, role
and team changes, seat pauses, and every change a team member made in the
store. Entries are kept for 400 days.

## Using the API

With an [API key](/api-reference/team) you act as the store owner: list your
team, invite people, change roles and teams, and read the activity log.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.