Keep the systems that work
Choose the workflow by its actual connection method.
Coordinate approved tax software, cloud files, email, practice systems, and front-desk connections without representing every directory entry as a full or bidirectional integration.
Supported scope
What this workflow is designed to do.
Visible capabilities are separated from configuration requirements, preview surfaces, and roadmap work.
Cloud-file providers
Email connection
Practice-system connectors
Per-firm activation state
Provider-specific boundaries
The workflow
Four clear handoffs. Human control where it matters.
The exact action changes by product status and firm configuration, but the ownership boundary stays explicit.
Choose
Identify the workflow and system of record.
Confirm
Verify current connection method, direction, and scope.
Authorize
Grant only the approved provider access.
Monitor
Track activation and keep exceptions visible.
Straight answers
Know what you are buying—and what remains outside the claim.
Does a listed provider mean a full integration is live?
No. The provider page and firm configuration define the actual lane and current availability.
Can firms keep existing systems?
Yes, where the required workflow is supported by a current connector or an explicit manual handoff.
Connected lifecycle
Continue through the practice workflow.
Map this workflow to the systems your firm actually uses.
We will separate current capability, connector requirements, preview work, and roadmap needs before recommending a rollout.
Request a workflow review →Status reflects the verified repository scope for this release. Provider configuration and firm permissions can further limit availability.