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

# Join a team from an invitation

> Complete the invited staff signup flow and enter the store with the role assigned by the inviter.

A new invitee joins through the staff signup flow. The invitation identifies the target store and assigned role; the recipient completes identity and account steps rather than choosing broader permissions.

## Who can do this?

Frontmatter roles list everyone affected by the flow. Administration is server-limited to **Owners and Managers**; Staff may perform only the explicitly described joining or access flow.

## Where to do it

Use **Staff** in the Management web app for lists, profiles, and administration. Invitations take new users into the staff signup flow. The Management mobile app has corresponding team, detail, invite, and join screens.

## Steps

1. Open the invitation using the same email address or phone number to which it was sent.
2. Start the staff join flow and confirm the invited team/store context shown by Tapp.
3. Verify the invited contact when prompted. Use the current verification code; requesting a new code can make an earlier one invalid.
4. Enter the required personal information and create a password that meets the displayed rules.
5. Finish signup and sign in. Confirm that the expected store is available and that the displayed role matches the invitation. Contact the inviter instead of selecting another role yourself.

## Platform notes

Roles are store-specific and checked by the API. Web and mobile share the same memberships; a visible control does not replace permission. After a change, refreshing or signing in again may be needed for locally held navigation and store context to catch up.

## Market notes

The same roles and flows apply in GB and Germany. Language and contact formatting are localized, but the Owner → Manager → Staff hierarchy and safeguards do not change by market.

This guide reflects the product on 17 July 2026. When navigation and the server response disagree, the API rule is authoritative; it prevents a visible surface from creating extra permission.

## Troubleshooting

* If Tapp cannot find the invitation, confirm the contact and ask the inviter whether the attempt was successful or expired. Do not create an unrelated account with a different contact.
* If verification or password setup fails, use the message on that step. Reopen the latest link or request a fresh code only when the current one is no longer accepted.

## Related articles

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