Skip to guides
SkapeHelp Center
All guides

Staff, roles and shift handovers

Give each person their own access, choose the right role and diagnose missing controls.

Grow and manage · 6 min read · Reviewed September 6, 2026

Skape client? We can set this up for you. Send a request, call, or email IOX →

Give each staff member their own access. Shared logins make it harder to know who changed a booking and harder to remove access when someone leaves.

Real product screen · Sep 6, 2026
The demo staff-management summary and invitation entry point. These browser captures end before the staff roster so no names or contact details are published.
  1. 1The invitation action starts a real staff workflow; it was not used here.
  2. 2The summary counts team members without exposing the roster.
The demo staff-management summary, with personal contact details excluded

The demo staff-management summary and invitation entry point. These browser captures end before the staff roster so no names or contact details are published.

  1. 1The invitation action starts a real staff workflow; it was not used here.
  2. 2The summary counts team members without exposing the roster.

Choose a role for the job

Skape’s staff roles include owner, admin, manager and game master. The dashboard filters navigation and actions using role and feature availability. Use the least access that lets the person do their work; game-master responsibilities do not automatically require billing or business configuration access.

Open the staff/team area with an authorized account. Check the intended location, recipient address and role before using an invitation action. Invitations are real communications. The email gallery’s staff invitation examples are only previews, and the legacy team-invite template is retained in the code but is not proof of a working invitation path.

Sign in and confirm access

Staff use the supported Skape / IOX sign-in flow. They should complete their own sign-in and any invitation acceptance. Never ask them to share a password or verification code in a support form.

After access is established, confirm that the person can open the pages needed for their role. A guest/customer account may use the same email but does not by itself create a staff seat. The active staff location determines which venue’s workspace is shown.

Investigate missing controls

  1. Check the signed-in identity and active location.
  2. Confirm that the staff membership is active and has the intended role.
  3. Check whether the associated feature is enabled.
  4. Sign out and back in if the session is stale, then retry the specific page.
  5. Ask an owner or IOX to investigate a remaining mismatch rather than granting broad access as a workaround.

If a person works at several locations, verify each location’s access. Switching active locations is not the same as granting a new membership.

Hand over a shift

Pass on arrivals, outstanding balances, room readiness, active sessions and unresolved technical problems. Use the staff scheduling feature if enabled, but keep responsibilities explicit even when you schedule externally.

Remove or deactivate access through the supported team workflow when it is no longer needed. Check any dedicated devices that remained signed in. Public Help guides remain available without staff access; account-specific shortcuts intentionally disappear when an active membership cannot be verified.

Want us to set this up for you?

If you’re a Skape client, just tell us what you need configured. Call, email, or send a request here, and we’ll set it up for you.

That includes things like hours, prices, booking options, emails, party packages, and feature settings.

We handle system configuration remotely. Your team handles physical onsite work, such as mounting screens, running cables, and installing equipment.

Send a configuration request

We’ll include this guide: Staff, roles and shift handovers.

Describe the result you want and the location it applies to. We don’t need passwords, card details, or verification codes.

We’ll use your contact details to follow up about this request.

Powered by