Skip to main content

Development trial ยท sample information only

Set organisation disclosure ceilings and verify sharing

For Organisation Administrators: licensed Collaborators with the relevant organisation-wide permissions.

What you will achieve

Set the maximum disclosure level available for an evidence type and audience, then check the intended recipient's view before sharing.

A ceiling limits what can be shared. Raising it does not itself publish evidence or grant a recipient access.

Before you start

Agree what information may be disclosed, to whom and for what purpose. Identify a representative fictional or approved record for checking the result. Record the current ceiling so you can compare the change.

Do not test with confidential customer material or by publishing a real pack publicly.

Change a ceiling

  1. Open Settings > Organisation > Disclosure.
  2. In Disclosure control plane, find the resource row and the audience/context column. Read the resource description and audience hint; similarly named contexts may disclose to different readers.
  3. Open the cell for the exact combination you intend to change.
  4. Review the current Maximum access level, the available level descriptions and the Backstory baseline.
  5. Select the approved level. Higher unavailable levels cannot be made available by typing a different number elsewhere.
  6. Enter a meaningful Reason for change, even though the interface marks it optional. Explain the business decision without copying sensitive evidence into the reason.
  7. Select Save ceiling. Reopen the cell and inspect its saved level and revision history.

Live versus Snapshot is chosen when evidence is attached, not by the matrix cell. Do not confuse evidence freshness with disclosure depth.

Verify the actual sharing context

Open the intended sharing surface, such as a compliance pack, and review its recipient-scenario preview. Check the visible content, ownership details and source access, not just a level badge.

Verify both the allowed information and something that must remain hidden. If a publication fingerprint or review is stale, complete the current preview/review process before publishing. Saving a ceiling is not permission to skip the sharing surface's own review.

Check it worked

Record the resource, audience, old and new level, reason and revision. Reload the matrix, then repeat the preview for the relevant audience.

A ceiling change cannot retrieve information that someone has already downloaded or copied. If an earlier disclosure was inappropriate, follow your incident and communication process as well as correcting the setting.

If something goes wrong

Problem Next action
A conflict or stale-version warning appears Use Reload current ceiling, review the other change and decide again
The preview still hides content Inspect the evidence attachment and recipient's own disclosure settings; the ceiling is only an upper bound
No controls are available Retry loading and report the error; do not assume the empty view means unrestricted sharing
You want to undo a change Set the reviewed prior level or use the specific baseline control, then save and verify

Human judgement matters

Restore Backstory baselines affects multiple custom controls. It is broader than correcting one cell and may increase some ceilings while reducing others. Review the impact before using it.

What next?

For the wider context, see Configure work planning, reporting and disclosure.

Tell evidence publishers which contexts changed and ask them to recheck affected sharing decisions. Keep internal Platform Admin documentation outside public/customer distribution regardless of disclosure settings.

Get help

Contact your organisation's support route with this guide reference, the affected page and a sanitised error. Do not include passwords, keys or session details.

Was this article helpful?