Skip to content
Enjoy complimentary data migration when switching from your existing bookkeeper or CPA to Institution.

Security and operating controls

Clear access. Connected records.

See how Institution scopes access, handles documents, and keeps review history connected to your work.

  • Named access

    Only the records each role needs.

  • Connected evidence

    Documents attached to a named request.

  • Review when roles change

    Access follows current responsibilities.

Role-to-record access

Access follows responsibility.

Select a role to see its record scope and the actions available within that scope.

Explore access by role

Business owner

Scope: Every entity record they own

  • Full view of every entity record they own
  • Approve requests and reporting release
  • Grant or remove team access
Outside scope

Modify Institution's internal review records

Control model

How the controls work.

Access, supporting evidence, ownership, and review stay connected to the operating record.

Access starts with responsibility.

Every access decision starts from the record and the role, not the person. When a team member is staffed on an account, access is scoped to that work. When the responsibility ends, access is reviewed and removed.

Documents arrive through a request.

Client documents are tied to a named request, purpose, owner, and completion state. Evidence stays connected to the work it supports instead of disappearing into an email thread.

Role changes trigger review.

A staffing change, client-side role change, or professional handoff triggers an access review before the next recurring cycle. Open requests are reassigned to a named owner.

External access stays bounded.

A tax professional, counsel, or specialist receives only the evidence package required for the engagement. There is no standing access to the live operating record.

Request-driven evidence

Follow a request from start to finish.

Choose a stage to see how documents, ownership, and review stay connected.

Stage 01 / 04

The work begins with a named request.

A request records what is needed, why it is needed, who owns the next action, and its current state. The request becomes the container for the evidence and review that follow.

Named ownerDefined purposeVisible state

Continuity

When responsibilities change.

Access is reviewed and open work is reassigned, while the operating history remains available to authorized people.

Responsibility changes

A person rotates off an account, a client-side role changes, or an external engagement ends.

Access is reviewed

The role-to-record scope is checked before the next recurring cycle and access that is no longer needed is removed.

Open work is reassigned

Requests in flight move to a named owner so the work does not sit without responsibility.

History remains

Request history, review records, and reporting packs persist independently of the people who created them.

Operating practices

How we handle your information.

These practices describe how Institution manages client records and provider access.

Named access only

Access is granted to people staffed on your account. Onboarding and offboarding are documented events, not a change in a shared login.

Delegated over shared

We prefer delegated access and provider-issued invitations over shared passwords. Where shared credentials are unavoidable, they are stored in a business password manager, not in email or shared documents.

Encryption in transit and at rest

Client records and workpapers are held in the accounting software of record, such as QuickBooks Online or Xero, and in Institution's internal systems, which encrypt data in transit and at rest.

Provider-official integrations

Bank, card, and payroll integrations use each provider's official read-only mechanisms whenever available. Write access is limited to the specific tasks it is granted for.

External professionals

Access scoped to the engagement.

A licensed tax professional, counsel, or specialist receives a bounded evidence package and returns work into a defined request.

Evidence package

Only the documents and context required for the engagement.

Approved delivery

Work moves through the client's approved channel.

Defined return path

Completed work returns into a named request.

No standing browse access

External professionals do not receive standing access to browse the client's live operating record.

Client data

Our commitments.

These boundaries apply to client financial information in the operating workflow.

  • We do not sell client data.
  • We do not use client financial data to train third-party AI models.
  • We do not store bank credentials outside sanctioned provider integrations or a business password manager.
  • We do not send financial statements or credentials over unencrypted channels.