Running the business
Access and sessions
Fixmo checks a user's role, branch and active state against the database on every request rather than trusting what their session was issued with. Removing access takes effect immediately, and the person is told their access changed.
What it does
Most systems put a role into a session token at login. Change someone's access and nothing happens until they sign out, which can be days.
That is the wrong behaviour for the case it matters most: removing access from someone who should not have it any more.
Fixmo reads the role, branch and active state on each request. A change applies to the next thing they do.
When the change is detected, the session is reissued to match and an alert tells the person their access has changed, so nothing fails silently.
Separation between shops is not a permission and cannot be reached by one. It is applied to every query unconditionally.
Some sensitive actions need a second person rather than only a permission. A cashier's refund, an exchange and a document edit each wait for an admin or manager, who can approve from their own account or by entering a PIN on the cashier's screen.
Every capability
| Checked per request | Role, branch and whether the account is active |
|---|---|
| Effect | Immediate. Not deferred to the next sign in |
| Session | Reissued when a change is detected |
| Notification | The person is told their access changed |
| Shop isolation | Unconditional, and not a permission |
| Second approval | Refunds, exchanges and document edits |
| Approval routes | The approver's own account, or their PIN on the other screen |
| PIN authority | The PIN holder is the approver, not the signed-in user |
| Deactivation | Blocks access while keeping the person's history |
Questions
If I deactivate someone, when does it take effect?
On their next request. There is no window where an old session keeps working.
Does Fixmo support two-factor authentication for my staff?
Not today. Access is controlled by roles, permissions and immediate deactivation, and sensitive actions need a second person to approve them.
Can one shop ever see another's data?
No. Separation between shops is applied to every query and is not something a permission or a role can affect.