The Users page (under Settings, admin-only) lists everyone who has ever signed in to your portal. It fills in on its own — a person appears the first time they sign in — so there is nothing to add by hand.
The user roles & what each can do
- Superadmin — the built-in superuser account that can always administer the system, even if company sign-in is down. Full access, including the destructive actions (backup restore) that even ordinary admins can’t do.
- Admin — full access: prices, apartments, settings, sending bags, invoice approvals, user management — everything.
- Power user (your sign-in provider may call this superuser — they mean the same thing here) — read-only: sees every page an admin sees, but can carry out no action at all — no counting, sending, editing, approving or settings changes. The backup download (it holds secrets) and the data API are off-limits too. Ideal for an owner or accountant who needs full visibility without ever changing data. It sits directly under admin and above user in the role list. Set it any of three ways: choose the poweruser role, tick 👁 Power user in the person’s ⚙ Manage panel on this page, or put the person in your sign-in provider’s poweruser (or superuser) group.
- User — a normal staff member. Which of the installable apps they can open is set per person under 📱 App access (see below): with nothing ticked they can open every app, or you tick just the ones they need (e.g. only Housekeeping, or only the Packer app). Never the admin/office pages. Can also be limited to specific property groups.
- Laundry — a user or guest you tick as Is Laundry user and tie to one laundry: confined to the Laundry app — laundry counts and invoice submission — and nothing else (the App-access ticks don’t apply to a laundry account).
- Guest — a light account (for example a driver). A guest has no app access by default: under 📱 App access you tick the apps they may open (e.g. only the Route tool for a driver) — with nothing ticked a guest can open nothing at all. Assign a laundry instead to turn a guest into a Laundry-app account.
Roles come from your sign-in provider (the token it issues), not from this app — so the page shows the role each person held at their most recent sign-in, and updates every time they log in. The built-in superuser is always shown as Superadmin. Power-user read-only status comes either from your provider’s poweruser group or from the read-only tick on this page (below); an administrator is never made read-only, so the tick can’t lock anyone out of administering the system.
App access — which apps each person can open
Each installable app — Packer, Housekeeping, Laundry, Route, Vehicles, Turnovers — can be turned on or off per person. Open ⚙ Manage under someone and tick the apps they may open under 📱 App access. What “nothing ticked” means depends on the account: for an ordinary user, nothing ticked → every app (tick to *limit* them); for a guest, nothing ticked → no app at all (tick to *grant* — a guest is off by default). Either way, once you tick one or more apps the person is limited to exactly those — that is how you give a housekeeper only the Housekeeping app, or a driver only the Route tool. Administrators and read-only power users always have every app regardless of the ticks, and a laundry account stays fixed to the Laundry app by its laundry assignment. Changes apply on the person’s next page load — no re-sign-in needed.
What each column shows
- Name / Email — taken from the sign-in token; the email is shown when the token provides one and is refreshed on every sign-in.
- Last role — the role held at the most recent sign-in.
- Sign-in — how they signed in (company SSO, or the built-in Superuser).
- Logins — how many times they have signed in.
- First seen / Last seen — when they first and most recently signed in.
External laundry users
Next to a user or a guest (not an admin) you can tick Is Laundry user and choose their laundry. That confines them to the Laundry app and the pages linked from it — laundry counts and submitting invoices — and sends them back there if they open anything else. It is also what lets a guest in at all: without a laundry assignment a guest has no access. See the Laundry Invoices guide for details.
When your sign-in provider is connected you can assign a laundry to someone before their first sign-in — the choice is saved right away and applied automatically the moment they first log in, so you no longer have to wait for them to sign in once.
Creating & managing users
When your sign-in provider is connected, this page lists every user. Open the ⚙ Manage panel on any row — it holds every per-user action in one place, so nothing runs off the edge of the table. From there an administrator can change a person’s role and/or reset their password on the 🔑 Password & role step (the role list runs *admin › poweruser › user › guest*), edit a profile (name, email and identity-provider groups), assign a laundry, set property groups, choose which apps they can open (📱 App access), toggle read-only, or enable/disable the account — all through your provider. To change only the role, leave the password box blank — the person keeps their current password; fill the password in only when you also want to reset it. Passwords are hashed on the server (MD5 HA1 + PBKDF2-SHA-256) before they are sent; plaintext is never stored. Give laundry accounts the guest role. You can also tick 👁 Power user (read-only) for anyone (except an admin) to give them full read-only visibility — it applies at their next sign-in. This page is admin-only.
/signal.ashx?credentials=…) only accepts an admin API key or a signed id_token as its credential — a plain access token is refused with *401 bad signature*. For a reliable directory, paste an ak_ key on the Authentication page (mint one at your provider’s api-keys-admin.html). Without a key, the app reuses the signed-in admin’s id_token, which works once they have signed out and back in on this version.