Use casePractice management software

A multi-tenant repository by API

Tallybook keeps every accounting firm's files in one bucket. Firms want their own rules, and a security review asks how they are kept apart.

One space per firm, closed by the repository's own rightsA firm adds its own document type with no schema changeEach firm's review workflow changes without a release

The repositoryRights on the space

Only Ashby Carter's groups hold rights here. A user from Northfield CPA is refused on open, on search and on listing.

source · access rules on the space root
The review on a year-end file

Revenue above the threshold · a senior manager reviews

Actions on this firm's space
01

The problem

The whole thing in one move

How does Tallybook prove that one accounting firm can never read another's files? For years, the honest answer was a set of filters in application code. Client documents sat in one storage bucket with a folder per firm, plus a metadata table in Tallybook's main database, and a firm-specific type meant a migration script. The document layer had become the hardest part of the product to change.

The fix is to hand that layer to a repository Tallybook calls by API. Each firm gets its own space, closed by rights the repository enforces on every open and every search. Types and workflows are configured per firm, with no schema migration. Tallybook keeps its product; the repository holds the documents and the rules.

Tallybook · Fellside FarmWorkspace
Accountants never leave Tallybook. The repository sits behind the screen, and its rights close the file to every other firm.
SpacesRepository
Four firms, four closed spaces. Each one carries its own groups, its own types and its own hosting.

Watch the order things happen in: a firm's space is created at signup, its rights close it to everyone else, and the firm shapes its own types and workflow on top of Tallybook's standard. Rafael builds the first part, Nicole shapes the last, and Orchard Tax shows how a contract ends.

02

The space

Rafael Mendes, Tallybook's CTO, starts where the security questionnaire pushed hardest.

Step 1Setup

A firm signs up, and its space is created

When a firm completes signup, Tallybook's back end calls the repository's REST API. It creates the firm's space, its groups and the standard document types Tallybook gives every firm.

Space rootFirm groupsStandard types
Space ashby-carterRepository
The space exists before the firm's first user signs in.
Day one is a working spaceNo ticket, no manual setup. The firm's space is part of Tallybook's own signup.
Step 2Permissions

The repository closes each space to everyone else

Rights are set on the space and go down to each document. Only Ashby Carter's groups hold any. Search runs inside the rights of whoever runs it, so a Northfield user never sees an Ashby result. Rafael adds a check to Tallybook's release pipeline that tries anyway.

Cross-firm check · release 4.18Developer portal
Tallybook's own test, run against the repository's rights at every release.
Suppose a firm's auditor calls tomorrow and asks how its files are kept apart. Do you show a rule in the repository, or a line in your code?
Separation no longer rests on a filterThe repository refuses the call itself. Tallybook's code can have a bug; the rule still holds.
Step 3Hosting

The largest firm gets a dedicated environment

Northfield CPA's questionnaire goes further: it wants its documents in an environment of its own. Tallybook runs Northfield in a dedicated private cloud environment. The content model and the workflows are the same as everywhere else.

Space northfield-cpaAdmin console
Across deployments, the difference is who runs the infrastructure and how far isolation goes.
The answer fits the firm's contractMost firms share an environment, closed by rights. The one that asks for its own gets it, with no fork of the product.
03

The model

Every firm starts with the same types and workflow, then adds what its own practice needs.

Step 4Document types

Tallybook ships the standard model

Yuki Tanaka, product manager, keeps the standard model every firm gets: engagement letters, bank statements, invoices, payroll records, signed tax returns, each with its properties and its retention period. Classification and retention rules are part of the content model.

Standard modelAdmin console
Retention here is the default. Each firm can lengthen it.
Every firm starts completeA new firm files its first bank statement on day one, with the right type and the right retention.
Step 5Document types

A firm adds its own type, with no schema change

At Ashby Carter, Nicole Grant handles many farming clients. In Tallybook's settings she adds a type called Agricultural subsidy claim, with three properties. Tallybook passes it to the repository's API. Access is set by content type, so only Ashby Carter's groups can use it.

ProgramClaim year, requiredAmount
Ashby Carter · Document typesWorkspace
The repository accepts objects that do not look alike. No migration on Tallybook's side.
A customer request is a settingNicole had the type the same afternoon. Tallybook's engineers did not hear about it.
Step 6Workflow

The firm's year-end review gets one more step

Nicole starts from Tallybook's three-step year-end workflow and adds a second review when a client's revenue is above a threshold the firm sets. Processes are designed without code, versioned, and changed without redeploying the application.

Workflow year-end accountsCase management
Each step has an owner, a deadline and the documents it needs.
The workflow belongs to the firmTallybook ships the starting point. Ashby Carter's version 2 runs for Ashby Carter only.
04

The daily work

The space is live. Accountants file, managers review, and one firm ends its contract.

Step 7Intake

The accountant files a client's year-end papers

Omar Haddad, staff accountant at Ashby Carter, drops twelve bank statements, a trial balance, the subsidy claim and the draft accounts for Fellside Farm into Tallybook. Each file goes to the repository with its type and properties, and is indexed on write.

Tallybook · Fellside FarmWorkspace
Content and metadata are searchable as soon as they are filed.
The checklist fills itselfTallybook reads each filed document back from the repository and ticks the client's year-end list.
Step 8Viewer

The manager reviews in the browser, and sends it back once

Laura Brennan opens the draft accounts and the trial balance in the viewer, inside Tallybook. She leaves a note on a depreciation line and sends the file back to Prepare. Omar fixes it; version 2 goes through Review, then Second review, then Sign-off.

Draft accounts v1Viewer
The note stays on the document for whoever opens it next.
The review leaves a traceVersions, notes and decisions sit on the file. Next year's team reads why the rate changed.
Step 9History

A firm leaves: archive first, deletion after

Orchard Tax ends its contract. The operations engine exports its documents, properties and history to an archive, and the report says what left. Once Brian Walsh, Orchard's admin, confirms receipt, a retention workflow runs the secure deletion. Every action is timestamped.

Space orchard-tax · ExitOperations engine
The deletion waits for the firm's confirmation. A person launches it.
The exit is as clean as the startThe firm leaves with its files and their history. What happened to its space is written down.
05

What comes out

The workflow does not decide whether the accounts are right. It puts the reviewer's decision into one of three paths.

Approved

The review passes

The manager signs the review. Below the threshold, nothing else is needed.

Next: the file moves to the partner for sign-off.
Second review

Above the firm's threshold

The rule Nicole wrote adds a senior manager, with five business days.

Next: a task for the senior-managers group, with the documents attached.
Sent back

A point to fix

The reviewer names the line and leaves a note on the page.

Next: the file returns to Prepare, with the note and the version history.
What the repository does not decide

It approves no accounts. It grants no rights on its own. It deletes nothing without a person launching it. Across the nine steps on this page, every decision is made by someone at the firm or at Tallybook, with their own rights and their own trace.

The repository stores, enforces and records. The rules are Tallybook's standard and each firm's additions, written in settings and versioned.

06

What it saves

Tallied on Ashby Carter's space and on a fresh signup. Your own customers will bring their own counts.

0 schema migrationswhen Ashby Carter adds its own document type, with three properties and its retention.
Day 1when a new firm files its first document in its own space, created during signup.
4 stepsin Ashby Carter's year-end workflow, one more than the standard, with no Tallybook release.

Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.

Three principles behind the figures

Rights in the repositorySecurityEach space is closed by rules the repository applies on every open and every search.
A model that bendsFlexibilityTypes and properties change with no schema migration, firm by firm.
Processes as settingsProduct speedWorkflows are designed without code and change without redeploying Tallybook.
07

Who it helps

Moving a product's document layer takes a yes from the architect, the product manager and the firms whose files move. Each gets something different:

CIO and architecture

CTOs and architects

Your document layer is a bucket and a table you keep patching.

  • Documented REST APIs and SDKs.
  • Rights enforced by the repository, down to the document.
  • Built for hundreds of millions of objects.
  • One content model, whether shared, private cloud or on your own servers.
Product leadership

Product managers

Every customer request for a type or a step lands on your roadmap.

  • A standard model you ship to every customer.
  • Customer-specific types with no migration.
  • Workflows customers adjust in your settings page.
  • Retention rules carried by the content model.
Your customers

Firm admins

Your clients' files sit in a product other firms use too, and you are asked to trust it.

  • Your space, closed to every other customer.
  • Your own types and your own review steps.
  • A history on every document.
  • A full export when you leave.

Start small

With one firm and one document type. Move a test firm's client files into its own space through the API, and run your cross-firm check against it.

Then add the type that customer has been asking for, and time how long it takes.

Let's talk

See it under your own product

Share your current storage layout and a sample firm. We will walk your engineers through the first space, its rights and the first firm-specific type.

The screens on this page are drawn to show one step at a time, with example data. Tallybook, the firms and the people named are fictional.

Uxopian Software gives software companies the content building blocks behind their products, through APIs, so their teams can spend their time on what their customers pay for.