Skip to main content
Removing a team member revokes their role and store access. The action is immediate and is not the same as reassigning them to another location. Review identity and store carefully before confirmation.

​
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, select the person, and verify their name, contact, role, and current store.
  2. Choose Delete profile or the removal control and read the irreversible confirmation. The Management UI does not offer this action on your own profile.
  3. As a Manager, remove only Manager or Staff records; Managers cannot remove an Owner. An Owner can remove other roles but not the store’s last Owner.
  4. Confirm once and wait for completion. Return to the Staff list to verify the membership is gone.
  5. If the person should work in another store, use reassignment instead so the destination role is created as part of the transfer.

​
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

  • The backend rejects removing yourself, removing an Owner as a Manager, and removing the only Owner.
  • Historical operational records are not a reason to share the old account. Create or retain the correct new membership and let the system preserve its own audit/history references.