> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/menu-areas/release-and-sharing/uk-sharing.md).
# UK Sharing
**Open this area:** In the CORTEX menu, select **Release & sharing → UK sharing agreements**.
Record verified UK parties, one exact purpose, release handling and conditions with independent accountable-authority approval.
**Who uses this:** Author, Reviewer, Administrator.\
**Open in CORTEX:** `/releases/agreements`.\
**In-app guide:** `/help?topic=uk-sharing`.
**Expected result:** A versioned, time-bound agreement retains the actual party and legal decisions needed for an exact domestic sharing scope.
## Before you start
* Select the correct workspace and obtain explicit UK sharing read, proposal or approval permission plus current corpus access where needed.
* Obtain the actual agreement, both UK parties' authority references, UK location evidence, onward-use and recipient retention conditions, legal basis and incident arrangements.
* Identify the accountable sharing authority and applicable approved UK profile. No overseas or automated email transfer is provided.
## What to do
{% stepper %}
{% step %}
## Propose the agreement
Open Product, UK sharing agreements, then Propose sharing agreement.
The page shows workspace proposal authority, actual UK parties and legal evidence, accountable authority and reviewed-profile prerequisites. Four validated steps cover parties, purpose and terms, validity and handling with authority, then final review. Each step lists missing inputs and turns green when complete.
Record both parties with different authority references and verified UK locations, the exact purpose and agreement reference. Complete onward use, retention, legal basis, special restrictions and incident arrangements, with a 10–2,000 character reason.
Current eligibility, profile and handling are checked again on save; the final action retains one draft awaiting independent approval.
{% endstep %}
{% step %}
## Bound the scope
Enter explicit UTC start and end times; the end is exclusive and no duration is preselected.
Select the accountable authority using the shared person lookup. Private agreement handling must cover the proposed release marking. Review the approved UK profile and record the proposal reason.
{% endstep %}
{% step %}
## Approve independently
The named authority needs approval permission and must have authored no proposal revision.
Inspect the retained agreement and record actual UK party/authority approval and legal-review references. Approval before the start date is retained but cannot yet authorise use.
{% endstep %}
{% step %}
## Handle changes
Amendment creates a new draft and clears approval. Withdrawal stops future use and retains history.
Scope matching requires the exact current revision, parties, purpose and handling, a current approved profile and an effective agreement. Changed scope requires fresh review.
{% endstep %}
{% step %}
## Continue the separate release review
The agreement alone does not release a package, remove protected lineage, change a source marking or approve originator conditions.
The derivative, originator, special-policy and exact-package decisions remain separately required. Existing internal release and same-handling Shield workflows retain their existing rules.
{% endstep %}
{% endstepper %}
## Check the result
* Are both actual parties and destinations verified as UK?
* Does the exact purpose match the proposed use?
* Are validity, handling, onward use, retention and incident arrangements explicit?
* Is the authority independent, and are actual party and legal decisions retained?
## If you get stuck
Why is the agreement unavailable for use?
Refresh and inspect the exact parties, purpose, handling, revision, UTC validity and current profile. Amendments, expiry, withdrawal or changed access stop use. Approval status alone does not mean the agreement is effective now.
What happens after a save conflict?
Your entered decision notes remain available while you refresh and compare the current revision. Reconsider the changed agreement before retrying. Access loss clears the protected record and notes.
Does withdrawal recall downloaded material?
No. Withdrawal stops future agreement use. It cannot erase downloaded bytes or prove a recipient has acted; correction, withdrawal notices and receipt evidence require their separately recorded workflow.
## Responsibility and limits
* New capabilities require explicit grants; upgrading does not grant sharing authority or recipient access.
* A P handling code is not public-release permission and A1-A3 codes are not legal powers. S2 originator consultation and detainee or other special restrictions require their own actual decisions.
* A lower proposed release marking never changes an original or existing package. Recipient projections and transfer are separate workflows.
* Agreements retain up to 32 revisions and one MiB. No earlier record is discarded at a bound. Unchanged registration retries recover the same record on the same page.
**Reference and scope:** F16 domestic UK sharing. Agreement approval records actual evidence; it does not confer powers, originator consent or permission to change a marking.
## Related workflows
* [Review a derivative for UK sharing](broken://pages/0f2353fa172e1221893de98a680eecbabeae16c1)
* [Review, approve and publish an exact internal release](broken://pages/470978e3be0758fbc43448d1d7b8fc918bd9675f)
* [Create an immutable literal-sanitised Product](broken://pages/cdb9c7b59bf661ff4d337957385a22c20e4bc07a)
* [Protect source identity and review each use](file:///7397340/collection/source-protection.md)
* [Record processing purposes and privacy applicability](file:///7397340/assurance/processing-activities.md)
* [Review retention and appraise records](file:///7397340/assurance/retention.md)
* [Manage accounts, grants and workspace membership](file:///7397340/assurance/access.md)