Security

Your whole company in one system. Locked down by design.

One database means one place to get access right. Here’s how Apro OS decides who sees what, protects sensitive data and keeps AI on a short leash.

Security & access

Everyone sees exactly what they need. Nothing more.

Access is set per designation, module by module. Pick a person to see what Apro OS shows them and what the server refuses.

Settings · Module access

Changes audited

Server · live requests

Enforced on the server
Every API route checks module access, so a blocked module returns 403, not just a hidden menu item.
Encrypted messages
Chat is encrypted at rest with AES-256-GCM, and so are Vault files.
Every change audited
Who changed module access, and who started or stopped each timer, when and why.
AI with blinders
Anton runs read-only and never sees salaries, the vault or chat.

Dashboard, My Tasks, Chat, Calendar and Vault are available to everyone.
Every other module is granted per designation, and admins can apply ready-made templates.
Each API route checks module access on the server and returns 403 when access is missing.
Records inside a module have their own rules too. For example, sales roles see only the leads they created or were assigned.

Chat messages are encrypted at rest with AES-256-GCM.
Vault credentials and files are encrypted, and shared only with the people or teams you choose.
Project budgets and financial figures are admin-only.
Team copies of proposals are generated with every money detail removed.

Every change to module access is recorded with who made it.
Every timer start, pause and stop is logged with its cause: a person, a timer switch, a biometric punch-out, the night auto-pause or a QC hand-off.
Lead timelines show when each lead was created, modified and moved between stages.

AI safety

Anton answers open questions by writing its own database queries, and those queries run with hard limits.

Thirty minutes with the team that builds Apro OS and runs its own company on it every day.