Team and permissions

Concept

QueueJump uses role-based access so each person gets only the permissions needed for their job.

At vendor level, access is grouped into:

• Owner: full access, including billing, business settings, team management, and operations.
• Management: operational access (orders, schedule, menus, locations, outlets, team invites) without billing and business-account control.
• Member: order operations access for service-day execution, with read-only access elsewhere.

Use individual logins for each person. Avoid shared accounts.

Why it matters

Clear permissions reduce operational risk and improve accountability.

• Billing and business settings stay protected.
• Service-day staff can work quickly without excess access.
• Role changes are traceable to specific users.
• Offboarding is cleaner when people have individual accounts.

Most access problems are caused by role drift over time, not one-off errors.

How to configure it

1. Open Dashboard -> Settings -> Team (owner or management access required).
2. Add a team member with first name, last name, email, and role.
3. Choose the role deliberately:
   • Management for day-to-day operational admins.
   • Member for staff focused on order handling.
4. Send the invite and confirm the person appears in the team list.
5. If needed, resend invites from the member actions menu.
6. Use owner access for high-risk changes:
   • Change member role
   • Remove team members
7. Review team access before major events and remove leavers promptly.

If the invited email already has a QueueJump account, they receive a sign-in link. If not, they receive an invite flow to set access up.

How to verify it worked

• Team list shows the expected role for each person.
• Member users can run orders but cannot edit schedule, menus, or billing.
• Management users can run operations and invites, but cannot manage billing/business.
• Owner account remains the only role that can change roles or remove members.

Related guides: Onboarding workflow, Outlets, and Service day runbook.

Common mistakes

• Sharing one owner login across multiple staff.
• Assigning management role when member access is sufficient.
• Expecting member users to edit sessions or menus.
• Leaving old team members active after they stop working with you.
• Forgetting to re-check access ahead of busy seasonal periods.