atlasfinance
03 / SECURITY & ACCESS

Access is earned.
Visibility is scoped.

Financial information needs boundaries that apply to real requests, not just hidden buttons.

Private by default

Financial requests require a signed-in identity. Workspace ownership and project permissions are checked on the server and in database policies for Supabase records.

Invitation before access

A shared project is unavailable to its recipient until an invitation is accepted. Removing membership revokes that project access.

Restricted financial views

Project roles can restrict financial sections. A limited viewer need not see client revenue, salaries or project profit.

Financial history

Important financial changes are logged. Historical snapshots and recorded payment events preserve context for later review.

WHAT TO KNOW

Security is a practice, not a badge.

Atlas Finance uses Supabase authentication for new accounts, database row-level policies for Supabase project data, private document storage and server-side access checks. An earlier owner workspace remains on a separate protected legacy store while account migration is still being verified.

We do not claim an external security certification or a completed independent audit. Users should use a unique password, protect invitation links and verify the recipient before sharing a project.

Read the privacy notice