Who sees what, and why

A directory that decides what people can do.

Roles, per-location scoping and capability limits, so a store manager sees their store and an area manager sees all of them, without anybody hand-managing access.

Who sees what, and why

Four roles that stack

Admin, manager, scheduler and employee, each a superset of the one below. Simple enough to explain to a new manager in a sentence.

  • A manager can be restricted to the locations they run, so a multi-site directory does not hand everybody everybody else's team.

Limits inside a role

Narrow what a role reaches without inventing a new one, for the manager who schedules but should not see pay.

Bring a team in at once

Import from CSV with a downloadable sample that matches the parser, so the first day is not ninety rows of typing.
FAQ

People and permissions, answered.

Can a manager see other locations?+
Only if you let them. Restricting somebody to their assigned locations is a switch on the person, and it holds on the server rather than merely hiding menus.
Who can grant Admin?+
Only an admin. Handing out the role that can hand out roles is the one permission worth being strict about, so managers cannot promote anybody.
What happens when somebody leaves?+
Deactivate them and their history stays intact for timesheets and audit, while they stop appearing in scheduling. Deleting a person would take the record of what they worked with them.
Vocabulary

The terms behind this feature.

Plain definitions for the words that show up when you run shifts, each one written to answer the question on its own.

Field notes

Written up, from the floor.

How operators actually handle this, what it costs when it goes wrong, and where the trade-offs really sit.

See it with your own schedule

Set up a workspace, add your team, and build a week. It takes about ten minutes and costs nothing.

Start free