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

# Teams & Permissions

> Give other people access to your stores without sharing your login

Teams let you bring in staff, a VA, a developer or a business partner without handing over your account. You create a team, attach your stores to it, and invite members by email with their own granular permissions. Teams are included on **every plan, including Free**, at no extra cost.

Teams are managed under **Account Settings → Teams**.

## How teams work

<Steps>
  <Step title="Create the team">
    A team is created and owned by one merchant account - yours. The owner
    attaches their **own stores** to it, and members then work on those shared
    stores.
  </Step>

  <Step title="Invite by email">
    The invitee **must already have a Komerza account** with that exact email
    address. If not, the invite fails with: "No user with that email address is
    registered on Komerza. Please ensure an account is created with that email
    before sending an invitation." Ask them to register first - a Free account
    is enough - then send the invite again.
  </Step>

  <Step title="They accept">
    The invitation email contains an accept link valid for **72 hours**. Members
    show as inactive until they accept. If the link expired, just send a new
    invite.
  </Step>
</Steps>

## Permissions

Each member gets their own permission set, chosen by the owner. Permissions are granular - view, create, update and delete - across the areas of the attached stores. You will see friendly names such as "Update Products", "View Orders", "Deliver Orders" and "Refund Orders".

Permissions cover products, orders, coupons, customers, categories, tickets, blacklist, discount dialogs, email marketing, blog, tax, subscriptions, buyer protection, webhooks, analytics and the audit log. "View Stores" is always included for members.

<Warning>
  Be deliberate with the money-adjacent and destructive ones. **Refund Orders**
  moves real money, **Deliver Orders** consumes stock and issues license keys
  without verifying payment, and delete permissions are irreversible. Grant the
  minimum each person actually needs.
</Warning>

The same permission model backs API access, so the [scopes reference](/api-reference/scopes) is a useful companion when you are deciding what a member or an integration should be able to do.

## Who can do what

| Action                   | Owner | Member |
| ------------------------ | ----- | ------ |
| Invite or remove members | Yes   | No     |
| Edit member permissions  | Yes   | No     |
| Add or remove stores     | Yes   | No     |
| Rename the team          | Yes   | No     |
| Leave the team           | n/a   | Yes    |

<Note>
  There is **no ownership transfer**. A team, or its stores, cannot be handed to
  another account through the dashboard. If a business changes hands, contact
  support before making any other changes.
</Note>

## The audit log

The owner, and any member granted "View Audit Log", can review what members have done on shared stores. The log filters by member email, store, method, date range, and a destructive-action flag, and lives in the dashboard's Audit Log tab.

If a member changed something they shouldn't have: check the audit log to confirm who did what, tighten that member's permissions or remove them from the team, then undo the change in the store.

## Common questions

<AccordionGroup>
  <Accordion title="The invite says the user was not found">
    The invitee must register a Komerza account with that exact email address
    first, then you resend the invite.
  </Accordion>

  <Accordion title="The invite link expired">
    Links last 72 hours. Send a fresh invite.
  </Accordion>

  <Accordion title="Can a member invite other people?">
    No. Inviting, removing and permission changes are owner-only.
  </Accordion>

  <Accordion title="Do teams cost extra?">
    No. Teams are included on every plan, Free included.
  </Accordion>

  <Accordion title="A member says a button is greyed out">
    They are missing the permission for that action. Some features also require
    a related permission to be visible at all - for example the Buyer Protection
    page requires the store analytics view permission.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="API Scopes" icon="key" href="/api-reference/scopes">
    The same permission model, applied to API access.
  </Card>

  <Card title="Notifications" icon="bell" href="/guides/notifications">
    Store alerts reach members holding the relevant permission.
  </Card>
</CardGroup>