Use casePractice management software
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
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 rootRevenue above the threshold · a senior manager reviews
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.
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.
Rafael Mendes, Tallybook's CTO, starts where the security questionnaire pushed hardest.
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.
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.
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.
Every firm starts with the same types and workflow, then adds what its own practice needs.
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.
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.
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.
The space is live. Accountants file, managers review, and one firm ends its contract.
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.
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.
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.
The workflow does not decide whether the accounts are right. It puts the reviewer's decision into one of three paths.
The manager signs the review. Below the threshold, nothing else is needed.
Next: the file moves to the partner for sign-off.The rule Nicole wrote adds a senior manager, with five business days.
Next: a task for the senior-managers group, with the documents attached.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.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.
Tallied on Ashby Carter's space and on a fresh signup. Your own customers will bring their own counts.
Where these numbers come from. They are counted on the scenario described on this page, with example data. They are not a customer result.
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:
Your document layer is a bucket and a table you keep patching.
Every customer request for a type or a step lands on your roadmap.
Your clients' files sit in a product other firms use too, and you are asked to trust it.
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
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.