Security
Built for separated company workspaces.
Company and location separation, authenticated access, permissions, audit records, and private storage.
- Version
- 2.0
- Effective
- October 24, 2026
- Last updated
- October 24, 2026
- Applies to
- Operiin Training, Scheduling, Workforce, Financials, and Complete; applicable enabled services
Operiin is designed to separate customer information by company, location, assigned role, permission, and authenticated user. If the required access scope cannot be verified, access is denied.
Security controls
Authenticated access
Protected application data requires an authenticated session. Operiin verifies the account and applicable workspace before protected records are returned.
Company and location separation
Customer records are scoped to the applicable company and location. Multi-location access is limited to the locations and regions authorized for the user.
Row-level data controls
Production data tables containing customer information use database-level access policies where applicable, in addition to application permission checks.
Role and permission checks
Operiin separates self-service, store-level, regional, administrative, billing, training, financial, publishing, and other sensitive capabilities.
Server-side authorization
Consequential actions are designed to re-check authority, scope, source state, and applicable permissions at the server or command boundary.
Audit records
Operiin records material account, configuration, permission, scheduling, timekeeping, training, financial, import, export, and administrative events where the applicable workflow supports audit capture.
Private files and media
Imports, profile images, company logos, and training media are stored in access-controlled locations. File access requires the applicable company and permission scope.
Integration secrets
When direct connections are enabled, provider tokens and API credentials are restricted to authorized services and users. Operiin does not display stored secrets back to ordinary workspace users.
Sandbox separation
Personal Sandbox environments are marked as synthetic and separated from ordinary customer operations, reporting, billing, notifications, and production decisions.
Fail-closed behavior
Operiin does not intentionally grant broader access when company, location, membership, role, or permission information is missing or cannot be verified.
Default role model
| Role | Default scope | Default access boundary |
|---|---|---|
| Owner / Admin | Company-wide | Setup, locations, users, operations, reporting, and activation; ownership, contracting, or billing may remain Owner-only |
| Area / District Manager | Assigned region and locations | Regional and assigned-location operations |
| Store Manager / Assistant Manager | Assigned store | Own-location operations according to granted permissions |
| Employee | Self only | Personal schedule, time, availability, requests, profile, and assigned training |
| Dev / Support | Synthetic or expressly authorized scope | No unrestricted cross-company access |
Actual permissions may differ according to customer configuration, assigned scope, feature readiness, and written agreement.
Incident response
Receive and detect
Triage and classify
Contain
Investigate
Remediate and recover
Notify affected customers where required
Document corrective actions
When Operiin determines that a confirmed security incident affects Customer Data, Operiin will notify affected customers without unreasonable delay and according to applicable law and contractual commitments. Customers remain responsible for their own downstream notification obligations.
Independent assurance
Operiin does not claim SOC 2, ISO 27001, or another independent certification unless the applicable current certification is expressly published in this Trust Center.