What you'll achieve
You will maintain reciprocal client relationships and company-group membership while preserving the boundary and accountability of each organisation.
Who this is for
This guide is for an Organisation Collaborator with the permission or assigned action described below. If the navigation or action is missing, check the selected organisation, effective account level, feature state and role before assuming the product is unavailable.
Before you start
Check that you have:
- The legal organisations and relationship owner.
- Authority to invite or join a company group.
- A decision about what evidence may cross the relationship.
1. Open the right relationship
Use Clients for reciprocal customer assurance and Company Groups for a governed group of separate organisations. Confirm which legal entity and relationship you are working in.
2. Review invitations and memberships
In Company Groups, check My Groups, My Memberships and My Invitations. Accept or issue an invitation only with authority from the relevant organisation.
3. Maintain member context
Record the local owner, participation state and expected contribution for each member. Group membership does not merge tenant data or make every record visible.
4. Share through governed products
Use compliance packs, assurance requests or other explicit sharing routes. Review recipient context and disclosure projection before release.
5. Record group decisions
Keep group-level decisions attributable and distinguish them from actions each member organisation must approve locally.
Check it worked
- The selected legal entity and organisation context are correct.
- Membership status and owner are visible.
- Shared evidence went through an explicit recipient-scoped route.
If something goes wrong
| What you see | What to do |
|---|---|
| An invitation names the wrong organisation | Do not accept it. Ask the inviter to correct the target. |
| A member cannot see shared evidence | Check the release, recipient and local permissions; do not copy the evidence by email as a workaround. |
| A group decision needs local approval | Record the dependency and route it to the member organisation. |
Human judgement, security and privacy
A group creates coordination, not a single data controller or merged authority. Keep legal and tenant boundaries explicit.
What's next
Schedule the next group cycle and confirm local owners for every member organisation.
Need help?
Use your organisation's approved Backstory support route. Include the organisation, page and action that failed, but do not include passwords, invitation links, secret keys or unnecessary personal or confidential content.