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

# Invite team members during setup

> Invite your first team by email or phone and check who has joined your shop.

Invite the people who will work in your shop while you finish its setup. You can send invitations by email or phone, or skip this step and invite your team later.

## Who can do this?

The setup checklist is for the **Owner**. Owners and Managers can also manage invitations from **Staff**. This guide describes the Owner's setup flow.

## Where to do it

Open **Set up your shop** in the web app. After entering your shop description, continue to **Invite your team**.

## Send invitations in the web app

1. Choose email or phone for the first person.
2. Enter their email address or phone number. For a phone invitation, check the country code.
3. Select the person's role. Check this carefully: the form initially selects Owner and keeps your chosen role for the next person.
4. Add the person to the invitation list.
5. Repeat for the rest of your team and review each contact and role.
6. Remove any incorrect entry and add the corrected details.
7. Select **Send invites**.
8. After setup, open **Staff** to check the invitations and team members for this shop.

Adding someone to the list does not send the invitation. Use the send button after reviewing the list. A new user follows the invitation to finish signup. If the contact matches an existing account that is not yet in this shop, that account is added directly; do not wait for a new signup invitation.

## Check the result

Some invitations can succeed while others fail. The setup screen may advance when at least one invitation succeeds, so reaching the completion screen does not confirm that everyone was invited. Check the team list and any pending invitations before sending again.

In the web app, if every invitation fails, the form stays open and shows an error. A failed email or text-message delivery can still leave a pending invitation saved. Check **Staff** before retrying, even when every row failed. Sending another invitation to a pending person replaces their code; it does not change their existing role.

## Platform notes

In mobile setup, choose **Email** or **Phone number**, enter the contact and role, then **Add team member**. Review the cards and remove mistakes with their close icon. The role resets to **Owner** after adding each person or switching contact type; check it every time. The phone country code also resets after adding a person.

Select **Send invites** after reviewing everyone. The mobile screen can advance even if every invitation failed individually. Check the team and pending invitations afterward. If sending reports an error, keep the same check-before-retry approach. **Skip** continues without sending the list, but it does not cancel a request already sent.

On **You're all set!**, select **Go to dashboard** and wait to return to the app. This saves setup completion. **Copy shop link** and **View shop page** do not finish that save; check the link opens the intended shop before sharing. If the final button leaves you on the same screen, check your connection and retry, or contact support. A failure may show no message.

Invitations grant access to the selected shop, not every location.

## Market notes

The same setup invitation flow is available for Great Britain and Germany. Choose the role for the person's responsibilities in this shop.

## Troubleshooting

Check contact details and existing invitations if someone cannot find their invitation. Avoid repeatedly inviting a person who is already listed. You can skip this step and finish invitations from **Staff** later. Entries added to the setup list are not sent when you skip.

## Related guides

* [Invite a team member](/en/staff/invite-team-member)
* [Understand roles and permissions](/en/staff/understand-roles-and-permissions)


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