Product documentation
Work with an accountant or advisor
How client relationships, consent, entity scope and signed engagements control advisor access in Aiviance.
Open
Aiviance supports collaboration between clients and professional advisors without treating a relationship as unrestricted access. The client relationship, consent and authorised scope are separate controls.
A relationship does not grant access by itself
An advisor must be linked to the client, but that link alone is not enough to read or act on client data. Access checks also require active consent for the relevant period and an authorised entity and capability scope. Missing, revoked or unavailable consent fails closed.
The scope identifies which entities and supported capabilities the client has approved. A request outside that scope is denied rather than inferred from the advisor's role.
Acting for a client has additional controls
Where Aiviance supports acting on behalf of a client, the relationship must be active, consent must remain active, and the linked engagement letter must be signed and unexpired. The acting session is time-limited and can be revoked. Supported actions still pass their own capability checks.
Sharing a document or signing a linked engagement does not create general access to everything in the client's workspace. It applies only to the relationship and scope represented by that workflow.
Access remains reviewable
Advisor reads against client data create access records for review. Clients can revoke consent, and revoked consent no longer satisfies subsequent access checks. The exact collaboration tools visible to either party depend on the relationship, workspace, region and permissions.
Signed-in users should use the Aiviance Guide for the controls available in their workspace. For the wider permission model, read Access controls, and for document sharing and signing, read Documents and financial records.