Security & Trust
OhioMade handles real money, real inventory, and real compliance. Security isn’t a slogan here — it’s a set of hard rules that keep businesses isolated, actions accountable, and sensitive data handled in the right place.
Entity-first foundation
Every business in OhioMade is rooted in a real legal entity. That entity is the spine of billing, access control, and reporting — so the platform always knows who the data belongs to and why it exists.
Identity v2 at the center
One login. One access model. Every app — ScanFlow, Payroll, Compliance, Dashboard, and more — uses the same Identity v2 accounts and business mapping. No stray logins, no shadow password databases.
Per-business isolation
Data for one business never mixes with another. Business IDs are enforced across databases, actions, and logs — so each store stays in its own lane even when a user has access to multiple businesses.
Least-privilege roles
Employees only see what they’re allowed to use. Owners can grant access by realm and by role — keeping daily operations fast while limiting sensitive features to the right people.
Data tiering for sensitive info
Not all data belongs in the same place. Day-to-day payroll fields live in Payroll, while highly sensitive compliance items (like tax forms and identity verification documents) belong in a locked compliance layer with tighter access controls.
Audit-friendly by default
Actions are logged so you can answer “who did what and when” without guessing. This supports real-world needs: owners reviewing changes, vendors resolving disputes, and compliance/audit requests.
Layered apps, smaller blast radius
Each realm is separated by design. That reduces the blast radius of mistakes, keeps responsibilities clear, and makes the system easier to maintain as your business grows.
Operator-first design
Security that slows down the store doesn’t survive. The goal is strong controls that still feel practical: fast logins, clean permissions, and workflows that match how real operators actually work.
Built for growth
Start with one realm or a full bundle — the security model stays the same. As you add apps, the platform keeps access consistent, data isolated, and accountability intact across the entire stack.