Skip to main content
An invitation adds a person to the selected store with a specific role. Existing users may receive access directly; new users receive a signup route. Choose the contact and role carefully because both determine the recipient’s onboarding and 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 Staff for the correct store and select Add staff.
  2. Choose email or phone, enter a valid contact, and select the intended role.
  3. As a Manager, choose only Manager or Staff. The backend rejects Manager attempts to invite an Owner. An Owner may invite any supported role.
  4. Submit the invitation and read the result. The response can contain successful and failed recipients, so do not assume every attempt succeeded.
  5. Tell a new user to follow the received invitation and complete contact verification, personal information, and password setup. Existing users keep their profile and are assigned to the store.

​
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 submission is disabled, check the contact format and role selection. Phone values are normalized before sending.
  • A failed result can mean invalid contact, duplicate handling, insufficient role, inactive store, or rate limiting. Correct the reported cause instead of sending repeated invitations.