Individual accounts
Employees and system identities do not share one universal login.
SECURITY & PRIVACY
Useful visibility, without unnecessary access.
Opia River uses individual identities and backend-enforced role, authority, department and qualification checks so access does not depend only on what the interface happens to show.
Your routinesYour teamOne connected flow
SECURITY & PRIVACYOpia River
Revocable access
Server-backed sessions allow logout and deactivation to revoke access.
Server-enforced boundaries
Sensitive APIs verify the user’s authority on the backend.
Private storage
Cleaning photos are retrieved through authorized application routes.
Employee separation
Crew cannot access Manager/Admin APIs simply by requesting the URL.
Display isolated
The restaurant display uses a dedicated read-only identity.
Developer isolated
Technical diagnostics are separated from normal restaurant authority.
Auditability
Important administrative and operational changes remain traceable.
EXPLORE OPIA RIVER
Security controls
Designed as part of the same connected restaurant operation.
- Individual authenticated accounts
- Employee / Manager / Admin role separation
- Supervisor operational authority
- Department restrictions
- Station and workflow qualifications
- Backend authorization checks
- Secure HttpOnly production sessions
- Session revocation
- Forced password-change enforcement
- Last-active-Admin protection
- Private cleaning-photo storage
- Login throttling and trusted-origin controls
- Production security headers
- Parameterized database queries
- Audit and activity history
Security is layered
A hidden button is not treated as a security control. Sensitive permissions are enforced by the server because users can make requests outside the visible interface.