Document Management in LedgerTitan: Staff Library, Client Sharing, and Portal Uploads

Shared drives and email attachments create familiar pain:

• No client context — a PDF in a folder does not know which engagement or request it fulfills
• Awkward sharing — forwarding files or temporary links instead of a controlled client view
• Upload chaos — clients email “here’s my stuff” with no status, version, or request trail
• Staff vs portal split — internal files and client-facing files live in different tools

LedgerTitan treats documents as a first-class practice feature: staff manage a library, share explicitly with teammates or clients, and clients fulfill requests from the portal—all under your subscription’s organizations.

On Documents, your team works from two tabs:

• Library — upload firm files (images and common document types, size-capped), filter by mine / shared with me, download, and share
• Requests — create standalone document requests for a client, track pending / fulfilled / cancelled, and open submitted files when the client responds

Files you upload are private by default. Use Share to pick users and clients from one multi-select (the same pattern as assignees). Client portal uploads stay in the client library; staff review them from Requests or the client’s Files tab—not mixed into the staff Library.

From a Client detail page, staff with Documents access also see that client’s files and requests without leaving the client record.

Portal Documents keeps the client experience simple:

• Requests — signing work from workflows plus file requests from your firm (submit uploads or attach from their own files)
• My files — documents the client uploaded (searchable and paginated)
• Shared with me — files your staff explicitly shared with that client

Clients can fulfill a request by uploading new files and/or choosing from My files. Cancelled requests stay visible so clients understand status. Fulfilled requests no longer show Submit—staff review the files from the staff Requests table instead.

Signing documents from workflow steps also surface on the Requests tab, so clients have one place for both e-sign work and file requests.

The library plugs into delivery—not only a standalone page:

• Request documents steps create library requests when the step is sent, so portal upload lands in the library and links to the step
• From library pickers on signing, email, and analysis steps attach an existing library file without a duplicate upload
• Email compose can attach from the library when your role includes Documents access

That keeps one blob in the library while steps and emails reference it—so renaming or sharing policy stays centralized.

Most accounting practice platforms include some form of client documents. The buying question is whether files live inside the same workspace as engagements, billing, and portal login—or beside it.

• TaxDome and Canopy are strong on tax-firm document and portal workflows; confirm how staff libraries, client shares, and workflow reuse map to your delivery model.
• Karbon emphasizes work management and collaboration; document intake often sits next to engagement ops—validate whether portal uploads and firm files share one client record with billing.
• Financial Cents is checklist- and workflow-oriented for bookkeeping teams; document depth varies—compare request status, client “my files,” and step-level reuse against your volume of client uploads.

LedgerTitan’s angle is narrow but deliberate: staff library, explicit share to users and clients, portal My files / Shared / requests, and attach-from-library on workflow and email—without a second drive product.

Document management in LedgerTitan is not a bolted-on drive. It is the place staff store and share files, the place clients upload and receive them, and the bridge into workflow steps and email—scoped to your organizations.

Pair it with the client portal for invoices and payments so clients have one signed-in home for money and documents. For a broader platform comparison, see our practice management roundup.