For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Understand the state of a client connection, record relationship obligations and coordinate work without confusing private relationship records with information the client can see.
Before you start
Select your organisation and open the correct client relationship. Clients are a beta surface in the recorded feature baseline. Confirm the client's identity, your responsibility for the relationship and the permissions needed for the task.
A client relationship is not the same as company-group membership. Nor does creating a private record establish a reciprocal connection.
Inspect the relationship
- Open the client overview.
- Read Reciprocal connection. Distinguish not established, invitation awaiting acceptance, active, rejected and terminated.
- Check the Visibility information and relationship context, including the client organisation and primary contact.
- Review Priority actions and open the relevant obligation or communication.
- Verify the underlying record rather than interpreting a count as proof that an action has been completed.
An invited connection still needs the client's acceptance before reciprocal assurance access is established. A terminated connection retains private history but should not be treated as continuing authority for new access.
Record and maintain an obligation
Open Obligations and inspect existing commitments. Use Add client obligation when a new formal commitment is needed.
Complete the offered obligation fields from the actual agreement: its purpose, trigger or deadline, accountable parties and relevant relationship context. Do not turn an informal discussion into a contractual assertion without evidence.
Save and open the obligation using its view/edit control. Record progress and fulfilment evidence through the supported fields and associated work. Keep a task's completion separate from evidence that the underlying obligation was satisfied.
Coordinate supporting work
Use the relationship's contacts, tasks, documents, assurance and compliance-pack areas as appropriate. Before sharing, inspect the recipient-visible projection and permitted disclosure route for that item.
Do not assume a document uploaded to the relationship is visible to the client, or that everything in the client's own organisation is visible to you.
Check it worked
The connection state is understood, the obligation belongs to the correct client and the actual owner and timing are clear. Supporting records are linked without exceeding the intended disclosure scope.
If something goes wrong
| Problem | Next action |
|---|---|
| Reciprocal access is absent | Check invitation and acceptance state |
| Connection was rejected or terminated | Resolve the relationship with its owner before attempting more sharing |
| Obligation appears duplicated | Compare its source and scope before deleting anything |
| The client cannot see an item | Review connection and disclosure controls separately from your own access |
Human judgement matters
The platform records commitments and evidence. It does not create commercial authority or determine contractual fulfilment merely because a field is complete.
What next?
For the wider context, see Manage clients and company groups. Review outstanding obligations and use the dedicated assurance or compliance-pack guide for any external evidence exchange.
Get help
Ask your Organisation Administrator about access or the task owner about the content. For a platform error, include this guide reference, the affected page and a sanitised message. Never share passwords, session details or confidential evidence in an open support request.