Scope, access, and coverage are agreed with your team.
Practical support. Defined responsibilities.
The day-to-day work
A clear queue. A useful handoff.
Define the recurring work and the evidence your team needs to review it. These building blocks become a role-specific operating plan.
Prepare approved invitation requests for account administrators
Guide clients through documented upload instructions
Track missing uploads and inaccessible files
Route account or permissions issues to the authorized administrator
What comes back to your team
Work you can see and review.
Portal onboarding checklist
A working record with source references, current status, and the person responsible for the next step.
Upload request register
A focused view of missing inputs, unanswered questions, and items that need your decision.
Access-support exception queue
A dated handoff that distinguishes completed work from pending review and unresolved exceptions.
Put the role into practice
From the first brief to the final check.
Prepare
Give the role a reliable starting point.
Share the approved portal instructions, invitation process, permission model, and identity-verification procedure. Define which support questions an assistant can answer and which must go to your administrator or engagement team.
An example working day
A practical handoff
A client can sign in but cannot locate the requested upload area. The assistant sends the approved instructions and confirms that the issue is resolved. A request to add another user is routed to the administrator for approval.
Illustrative workflow, not a client case study.Review
Check the work before closing the loop.
Check that requests refer to the correct client and engagement, and verify receipt in the approved workspace. Avoid asking clients to send confidential records through ordinary email as a workaround.
Your systems, your permissions
Fit the role to your environment.
Tool familiarity is considered when defining the role. Your team approves every platform, access level, and source of truth.
Platform names describe possible working environments, not endorsements or a promise of certification.
Before you start
A few useful questions.
What should we prepare for client portal administration?+
Share the approved portal instructions, invitation process, permission model, and identity-verification procedure. Define which support questions an assistant can answer and which must go to your administrator or engagement team.
How will we know what is complete?+
Check that requests refer to the correct client and engagement, and verify receipt in the approved workspace. Avoid asking clients to send confidential records through ordinary email as a workaround.
Which decisions remain with us?+
Authorized administrators grant access, reset credentials, and approve additional users. CPAs decide document sufficiency. The assistant does not share passwords, expand permissions, or interpret uploaded financial records.
Can the role work in our existing tools?+
We scope the role around your approved systems, including environments such as Canopy, TaxDome, SmartVault. Access, training, and the final tool requirements are confirmed before the role begins.