Two-step verification for owners
Workspace owners must enroll an authenticator app before their workspace opens. The requirement is enforced in the database, not just in the interface.
Security
AP7 Office is built so that the safe path is the only path. These are the controls running in the product today—not aspirations.
Workspace owners must enroll an authenticator app before their workspace opens. The requirement is enforced in the database, not just in the interface.
Every company record is protected by PostgreSQL row-level security. A query without the right membership returns nothing—there is no shared pool of data.
Employees join only through single-use invitation links bound to their email and role. Tokens are stored only as cryptographic hashes and expire after seven days.
Browsers hold only publishable configuration. Sensitive transitions—onboarding, roles, invitations—run through guarded database functions that verify identity on every call.
Authentication messages are sent from a verified domain with click tracking disabled, so security links are never rewritten by third parties.
Membership, invitation, and project lifecycle changes create audit events that owners and admins can review inside the workspace.
If you believe you have found a vulnerability, report it privately through GitHub Security Advisories. Please do not test against other companies' data.
Report a vulnerability privatelyAP7 Office is in active beta. We do not claim certifications we have not earned; compliance documentation will be published as it is independently evidenced.