> 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/workflow-guides/assurance/rights-cases.md).

# Rights Cases

**Open this area:** In the CORTEX menu, select **Assurance & governance → Rights requests**.

Record access, correction, restriction and erasure requests with scoped searches and independent review.

**Who uses this:** Reviewer, Administrator.\
**Open in CORTEX:** `/governance/rights`.\
**In-app guide:** `/help?topic=rights-cases`.

**Expected result:** A controlled case retains the request, search evidence, reviewed decisions, response evidence and closure without automatically disclosing or destroying holdings.

## Before you start

* Select the correct workspace and obtain explicit rights-case read, write or review grants. Workspace roles narrow global grants; they do not supply them.
* Retain the original request at its authorised evidence location. Use a minimised subject reference and select handling that covers the request and intended search evidence.
* An independent reviewer will need the actual legal-owner decision, identity checks, profile, clause/commencement mappings and applicable response deadline.

## What to do

{% stepper %}
{% step %}

## Register the request

Open Rights requests and Register rights request.

The page shows the received-request evidence prerequisite. Three steps cover reference, minimised subject, actual UTC receipt time and requested rights; scope and handling; then review and a 10–2,000 character recording reason.

Required inputs and a missing-input list update as you enter data, red or green step status shows readiness, and Back preserves entries.

Registration does not infer validity, identity, applicability or a deadline. An uncertain response can be retried with the same values on this page.
{% endstep %}

{% step %}

## Record each scoped search

Open the case and Record search evidence.

Record its actual time, evidence reference, method, results and limitations, including no matches.

Optionally inspect and add up to five exact holding references using identifiers from authorised workflow pages. The owning module's access and case handling are checked; payloads are not copied.
{% endstep %}

{% step %}

## Review independently

A reviewer who did not register or search the case chooses Review request.

Record identity checks, search completeness, exemptions or their assessed absence, actual body/jurisdiction/regime applicability, legal-owner decision and clause/commencement evidence.

Adopt a current reviewed profile and record one reasoned outcome for every requested right.
{% endstep %}

{% step %}

## Record the applicable deadline

Enter the explicit owner-reviewed response deadline and explain its basis, extensions or delay.

Late and retrospective evidence can be recorded with actual dates. No universal statutory duration is calculated.
{% endstep %}

{% step %}

## Retain the response evidence

Perform any response or change through the separately authorised owning workflow.

On the case, record its actual response time, evidence reference, actual effects and related workflow references.

Saving the case does not send data, correct a holding, impose restrictions or erase records.
{% endstep %}

{% step %}

## Close or investigate further

An authorised reviewer can close a responded case with a reason.

Further searches before closure reopen review and retain all earlier decisions and response evidence. A subsequent request after closure uses a new linked case.

Select a retained revision to inspect its attributed history.
{% endstep %}
{% endstepper %}

## Check the result

* Does the case handling cover the original request and every linked holding?
* Are search limits explicit rather than assumed exhaustive?
* Does each requested right have a reasoned outcome?
* Are identity, exemptions, deadline and current legal applicability evidenced?
* Are response evidence and actual effects traceable to their authorised workflows?

## If you get stuck

<details>

<summary>Can I register a request while applicability is unknown?</summary>

Yes. Registration records receipt. Independent review later records identity, applicability, exemptions, outcomes and an explicit deadline.

</details>

<details>

<summary>Why can I not review this case?</summary>

Review requires an explicit capability and a separate actor who neither registered the case nor recorded any of its searches.

</details>

<details>

<summary>Why did a holding reference fail?</summary>

Use the correct owning workflow, current exact revision and sufficient case handling. A changed, unavailable or inaccessible holding cannot be added by guessing an identifier.

</details>

<details>

<summary>Does recording erasure or correction change the evidence?</summary>

No. The case retains the request, reviewed outcome and evidence of separately controlled actions. Original material and prior decisions remain retained.

</details>

## Responsibility and limits

* Case read permission grants no additional access to holdings. Read, editing and review are separate capabilities.
* No automatic disclosure or destruction occurs. Record preservation and any correction, restriction or deletion remain subject to their owning controls.
* Conflicts preserve form inputs. Reload and compare current history before retrying. Uncertain registration or search responses can be retried with the same values on the same page; inspect history before repeating later decisions.
* Access failures clear sensitive form content. Never place request or subject details in support logs.
* The bounded case retains up to 20 searches and 64 revisions, with space reserved for decision, response and closure. A capacity refusal requires a linked case; history is not deleted.

**Reference and scope:** F14-R04. Actual organisation legal-owner, applicable regime, jurisdiction, exemptions, current clauses and deadlines must be evidenced for the case.

**Related workflows:** [Record processing purposes and privacy applicability](broken://pages/d290389040afc56efcecf55b7fc2e72ff1dc1dee); [Assess evidence quality and retain defect actions](file:///7397340/analyse/evidence-quality.md); [Review downstream evidence corrections](file:///7397340/analyse/evidence-corrections.md); [Preserve an exact revision and manage holds](broken://pages/0185ca5a2331760fb4c59665b8dde7f4d80e0fc6); [Manage accounts, grants and workspace membership](broken://pages/99c8701bc497eefb32769b668198b1f9f5fc6a93); [Record UK processing paths and approved uses](broken://pages/d1a5ce8a791f7e21103f6f699e97b63ddcffb253).
