Skip to content

Security

Your ledger, sealed and kept separate.

Accounting data deserves the same discipline as the accounting. This is how Leasecount keeps customers apart, decisions accountable and history intact.

ATLASCITYGATEMERIDIAN
Fig. 2 — One drawer per organization
  1. Tenant isolation

    An organization is a hard customer and billing boundary. Every customer record carries its organization through a directly verifiable relation, and database constraints stop journal and calculation provenance from crossing organization, lease or book scope.

  2. Server-side authorization

    Reads, writes, exports, background jobs and downloads are authorized on the server. Client-side route guards are a convenience, never the security boundary.

  3. Memberships and roles

    One human, one identity. People join organizations through memberships with owner, admin and member roles, and removing a membership revokes access without erasing history.

  4. Authentication

    Email and password with a six-digit verification code at sign-up, secure password resets, exact-email invitations, session revocation, rate limits, attempt limits and resend cooldowns.

  5. Segregation of duties

    Designated calculation, journal and close approvers are honoured, organizations can prohibit self-approval, and review actions serialize against control-policy changes.

  6. Immutable accounting history

    Approval snapshots, calculation versions and schedule rows are immutable. Approved journals are corrected by reversal batches. Closed periods are locked against accounting writes.

  7. Audit events

    Membership, permissions, organization and book configuration, policies, approvals, calculations, close and reopen, and exports all write audit events with actor, scope and time.

  8. Hashed, durable exports

    Exports are committed transactionally with their background job. The worker streams the file, hashes it, stores it durably and only then marks it ready.

  9. Retention without erasure

    Historical actor snapshots keep accounting explainable even when live personal data is removed or anonymized under an approved retention policy.

Roadmap

What comes next.

These are planned and not yet available. They are listed so you can plan around what exists today.

  • Multi-factor authenticationPlanned
  • SSO and SCIMPlanned
  • Custom roles and entity assignmentPlanned
  • Customer-authorized, time-limited support accessPlanned

Start with one lease.

Bring in a contract, assign your books and see the schedule your auditor will ask for.