Staff Permissions: Employees, Roles, and Per-Location Access

The Users module in admin.eatsyorders.com is where you control who on your team can do what. Three tabs: Employees, Roles, Permissions. All self-serve.

The Users module

Open admin.eatsyorders.com → Users. Three tabs across the top:

• Employees — the actual people on your team.
• Roles — the role definitions (Owner, Manager, Kitchen, Cashier, etc.) you create.
• Permissions — the granular toggles per role for each module of the platform.

Adding an employee

Users → Employees → + New Employees. Fields:

• Name + email — the employee's login.
• Phone (optional).
• Location assignment — pick the locations this employee can see.
• Role — pick from your defined roles.

The employee gets an invite email and sets their own password.

Defining roles

Users → Roles → + New role. Eatsy ships no default roles — you define the ones your team needs. Most operators end up with something like:

• Owner — full access everywhere.
• Manager — most things except payment/billing.
• Kitchen — Order Management tablet only.
• Cashier — process orders, run reports.

Spanish-team operators often label these Dueño / Gerente / Cocina / Caja. Whatever naming makes sense to your team.

Your onboarding manager seeds the initial roles for you during kickoff so you don't start from a blank page.

Permissions

Users → Permissions. For each role, granular toggles per module:

• Menu management — read / write
• Orders — view / refund
• Marketing — view / edit
• Catering — view / edit
• Account — view / billing access
• Users — view / edit (the meta-permission)

A common rule: only Owners get Account → Billing access. Managers can run the restaurant but not change the credit card.

Per-location restrictions

When you assign an employee to specific locations (rather than "all"), they only see those locations in the location switcher and only see their assigned locations' data everywhere. A Manager at location A can't see location B's orders, customers, or revenue.

Activity logs

The platform records who did what and when. Viewable per employee in their profile. Useful when you need to figure out who voided a $84 order at 9 PM on Tuesday.

Disabling vs. deleting

Always deactivate an employee instead of deleting. Deactivating preserves the audit trail (their old orders still show their name) but blocks the login. Deletion strips the audit trail.