Security and access
One sign-in.
Not one master key.
Signing in confirms who you are. It does not automatically open every company, location, module, or administrative tool. Odarius evaluates each access boundary separately.
Four boundaries
Access narrows at every step.
A person only reaches work allowed by all four checks. If one check fails, access stops there.
- 01
Identity
The sign-in confirms the individual account. Shared team logins are not the intended model.
- 02
Company membership
The account must belong to the specific company workspace. Membership in one company does not imply access to another.
- 03
Enabled capabilities
The company sees only the capabilities included in its subscription or written beta invitation. Internal-only tools remain unavailable to subscribers.
- 04
Assigned role
Within those capabilities, the person sees only the actions their job requires—such as owner, manager, cashier, kitchen, or reporting access.
What this means
Your workspace should feel focused—not exposed.
Menus, pages, and actions should reflect the company and role selected for that session. Administrative changes should be explicit, sensitive actions should be attributable, and switching companies should never become silent cross-company browsing.
Company separationEach business remains inside its own workspace boundary.
Least necessary accessPeople receive the capabilities needed for their work, rather than every available module.
Deliberate administrationOwners and authorized administrators control invitations and role changes.
Traceable activityAccount-level activity can be associated with the person who performed it where auditing is supported.
Invitation-only beta
A request is not an account.
Submitting a beta request does not provision access. Odarius reviews the business, agrees on the test scope, and issues a written invitation before any workspace is created.
Security is an operating practice.
This page explains the intended access model; it is not a certification or a guarantee that risk can be eliminated. Detailed security, privacy, retention, and incident terms will be documented for invited customers as the beta matures.
Read the privacy notice