Under Admin → Users you add people and set what they can see.
- Add them with a work email, their name, and a temporary password you choose — at least 12 characters. Then tell them the email address and that password.
- Assign a role: Viewer (read published reports), Care agent (the customer care desk only), Operations (operational reports and reconciliations), Finance (financial reports and statements), or Admin (everything except payroll, plus settings and user management). Payroll is given to people by name; see Give someone payroll access.
- Changing a role ends that person's open sessions. They sign in again with the new role.
The password you type is temporary, and the system enforces that. The first time that person signs in they are asked to set a password of their own, and the one you chose stops working. You never end up knowing a colleague's password, and you don't have to remember to chase them about changing it.
Two things follow from that, both worth knowing before you are surprised by them:
- Send them the temporary password by a route only they can read — in person, or a direct message. It is short-lived, but until they sign in it does open their account.
- If a password is refused when you type it, it is usually because it is too short or because it appears in a public list of leaked passwords. Choose another one; the check is there for a reason and cannot be waived.
Guidelines that keep this clean:
- Give the lowest role that does the job. It's a finance product — least access is the professional default, and you can always raise it later.
- Use Care agent for frontline care staff. A copied Ledger link and a direct Ledger API call are refused for that role; do not give Operations merely to open the desk.
- Individual reports can additionally be limited by role when published, so a sensitive report can be Finance-and-Admin-only even though the person can see the rest.
- When someone leaves, deactivate them here — their sign-in stops immediately, any session they have open is ended, and they come off your company's user list.
- If someone forgets their password, they can reset it themselves from the sign-in screen. You do not need to create them a second account, and you should not.
Deactivating someone is not erasing them
Deactivating ends a person's access. It does not remove them from your history, and that is deliberate: every report they approved, every figure they attested and every sign-off they made still shows their name.
A finance record that suddenly attributes an approval to nobody is worse than one naming somebody who has left — an approval whose author cannot be identified is not much of an approval. So there is no way to delete a person outright from this screen.
Reinstating somebody you deactivated is a support request rather than a button on the page. An action that can be undone in one click eventually gets undone by accident.
Employee numbers: so a salesperson's quotes come back to them
The Employee no. column holds the six-digit number your payroll (PaySpace) gives the person. Type it in and press Save (or Enter). To remove it, clear the box and save.
You only do this once per person. A salesperson's till code starts with that same number — 201234-2049, say, at store 2049 — so once the number is on their sign-in, every quote they make, at any store they work in, comes back to them as a follow-up. You do not need to link each till code separately.
- One number, one person. If the number is already on someone else, you are told so; take it off them first.
- If they leave, nothing needs doing here. When your payroll shows they have left, their new quotes go to someone else in the store at random. Follow-ups they already had stay with them until a manager gives them to someone else.
- If you are warned that no till code starts with the number, check it: the number is saved, but their quotes will not find them until a till code starts with it.
- Till codes that are a name rather than a number still need linking by hand.
Who opened which screen
Every time someone opens a screen, the app records which screen, who opened it, their role and when. This history is kept and is not removed, so it can show which screens are used and by whom. Administrators can see it, and in time so will the head of each department for their own screens. It is not part of any report, and the assistant cannot read it.