For licensed Collaborators with permission for this task. Check the selected organisation; feature availability and record access still apply.
What you will achieve
Review a queued disclosure and explicitly release the intended record or revision to the group, without releasing unrelated information.
Before you start
Select the member organisation and confirm authority to share its information. Identify the group owner, the exact record and the business purpose for release.
Review the source content and its sharing configuration first. A queue label alone is not enough to understand all the information a response revision, compliance-pack release or framework sharing level contains.
Inspect the queue
- Open the membership's Disclosure review area.
- Read any Sharing remains restricted message and the eligibility state.
- Identify the record's label, type, revision where shown, preparation date and stated audience.
- Review the exact underlying response, pinned pack release or mandate outcome and its existing disclosure configuration.
- Confirm that the current organisation and adoption/record ceilings permit the intended scope.
- If eligibility is not restored, resolve the restriction with an authorised owner. Do not try to bypass it by copying the content into a comment or email.
Restoring eligibility does not automatically share queued content. Each queued record still needs an explicit release decision.
Release one record
Use the eligible record's release control. In Release disclosure, check the record and recipient again.
Read the explanation of what will be released. The different modes have different effects: a response revision, a pinned compliance-pack release or a mandate headline outcome should not be treated as interchangeable.
Add a useful Release note if needed, then choose Release to group only when authorised. This action releases the selected item, not every queued record.
Check it worked
Refresh the queue and inspect the selected record's new disclosure state. Check remaining items separately. Where appropriate, verify the recipient-visible result using an authorised preview or coordinated recipient check, not the owner's unrestricted view.
For framework sharing, review its live sharing level separately from the release of a queued headline outcome.
If something goes wrong
| Problem | Next action |
|---|---|
| Release is unavailable | Check eligibility, lifecycle and permission |
| The prepared revision is not the intended one | Correct the source/revision decision before releasing |
| A release times out | Inspect the record's current disclosure state before retrying |
| The wrong information may have been released | Escalate promptly and use authorised restriction controls; do not promise recall of copies |
Human judgement matters
Sharing is an external information decision. Membership, acceptance and restored eligibility are not blanket consent to disclose.
What next?
For the wider context, see Manage clients and company groups. Retain the release rationale and monitor changes to the source, recipient relationship and sharing limits.
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.