Invitations — how a person arrives
Invite Staff on the People screen is the front door: a first name, a last name and an email address, plus their first assignment — position, location, employment type and start date. So an invitation is more than an account.
Once it is sent, the invitee gets an invitation email. Someone new to the product opens the link in it, fills in Set Your Password and Confirm Password, and presses Accept & Get Started, which accepts the invitation; they then sign in with their email and the new password, and land at the location the invitation chose, holding the position’s permissions.
- Someone who hasn’t accepted yet is “Invited”: not in the list below, but listed in Pending invitations above it. Whoever holds the invite permission can Resend or Revoke from each row; revoking takes two clicks — the first turns the button into “Revoke” plus the invitee’s email and a question mark — and revoking withdraws the invitation.
- The link in an invitation email works for 7 days, and opens nothing after that. Once it has lapsed, Resend sends the invitee a new link that opens.
Users
One row per person, active people first, inactive ones after. Export CSV saves the list as a file, people who haven’t accepted yet included — first name, last name, email, membership status, and the date the account was created (the Joined column). Clicking a row opens the person’s page: their name, status and email at the top, their Assignments and attachments below (and, where the organization has payroll, for payroll admins, the Compensation profile; for holders of the company-wide notes permission, Notes — see Staff notes).
- Deactivate / Reactivate — on the person’s row in the list, or in the header of their page. Deactivating takes two clicks: the first turns the button into “Deactivate” plus their name and a question mark, and the second deactivates. A deactivated person is signed out, shows as “Inactive” in the list, and can no longer get into this organization; nothing of theirs is deleted, and Reactivate brings them back. You can’t deactivate yourself.
- Assignments — every assignment the person holds; clicking a row opens the assignment panel, and Add assignment adds another.
At a branch — the branch’s people
A branch manager sees who works at the branch under People in the branch’s part of the sidebar: everyone based here — you too, marked “You” — and everyone granted to cover the branch, with their home branch. Each person shows their position, phone and email.
Clicking a row opens their profile at this branch: position, contact details and the date they started, with their Notes below (for holders of a notes permission — see Staff notes). Nothing here can be changed — assignments, deactivation and pay live in the Company’s People. Switch to a branch the person doesn’t work at, and the page says so, with Back to People.
Assignments — the system’s hinge
An assignment is “who, at which location, as which position, since when”, plus an employment type. Permissions follow the position and scope follows the location, so nearly every screen’s behavior is decided by the assignment. Which is also why every change to an assignment — adding one, changing its location or position, its end date, setting it primary, its coverage, its permissions — signs the person out once saved, and they must sign in again.
- Primary — with several assignments, one is marked “Primary”; Set primary on another assignment’s row, on the person’s page, moves it there.
- End date — to end an assignment, fill in the assignment panel’s End date, then save.
- Also covers — tick which branches this assignment covers besides its own location (support days, a travelling manager), then save. Absent on a single-location org.
- Permissions — the last layer: starting from the position’s grants, one toggle per capability is this person’s add or takeaway — with an “Overridden” badge on every row that differs from the position. Each toggle saves immediately, and from the person’s next sign-in this assignment carries the change.