Tenant isolation
Organization operational databases remain separate from the platform control database and from other organizations.
SECURITY & GOVERNANCE
Control is designed into the architecture.
FIXMAN separates platform administration from organization operations and combines server-side permissions, audit-sensitive workflows, tenant encryption and controlled synchronization.
Role-based authorization
Modules and actions are enforced server-side. Hiding a menu item is not treated as the security boundary.
Controlled audit
Important configuration, workflow and administrative changes are recorded for traceability.
Encrypted tenant payloads
Supported controlled payloads use tenant-specific application key material. Existing keys must be preserved during upgrades.
Biometric privacy boundary
Fingerprint, face or iris templates remain on the external biometric system/device. FIXMAN receives mapped attendance events, not biometric templates.
Device synchronization
The server remains authoritative. Offline capability is limited and replay uses idempotency/version controls rather than creating a separate master database on devices.
Platform supervision without raw employee location disclosure
The Platform Control Plane is designed to receive operational aggregates and supervision data. Detailed employee location evidence belongs in the organization tenant context.
Security deployment responsibilities
- Use HTTPS and valid certificates.
- Keep private configuration outside the public document root.
- Protect cPanel/API credentials and database accounts.
- Preserve tenant encryption keys across upgrades.
- Run staging QA, database regression and backup/restore tests before production.