Read Data & compliance
Data & compliance brings together the organisation-level records available to an administrator. It does not replace consent, eligibility or identity checks on an individual application. Begin by identifying which kind of record your question concerns.
Start interactive tutorial →
Before you start #
Open the Organisation workspace and Settings → Data & compliance. The controls you can use depend on your role and workspace availability. Practice uses synthetic records and never grants extra permissions.
Ask AI about this sectionOrganisation data records #
Data & compliance brings together the organisation-level records available to an administrator. It does not replace consent, eligibility or identity checks on an individual application. Begin by identifying which kind of record your question concerns.
Ask AI about this sectionFind safeguards in the workflow #
The Checks, Users and Audit links identify where different safeguards are managed. Checks holds the application context, Users holds role and access information, and Audit holds recorded activity. Choose the location matching the task rather than treating this page as an approval screen.
Ask AI about this sectionRead retention and deletion status #
Read the Retention and deletion description and its status together. A needs-action indication points to work requiring attention; it is not a command to delete applicant records. Use the authorised retention process and check any applicable holds before a real deletion.
Ask AI about this sectionRead organisation record counts #
Organisation records compares current records with the total available. A current count is an internal record status, not DBS accreditation or proof that every launch requirement has been satisfied. Investigate the underlying records when a review needs more detail.
Ask AI about this sectionUnderstand summary downloads #
Download PDF and Download JSON appear only when the workspace supplies those authorised routes. When unavailable, the panel explains the restriction. This tutorial reads the sample summary and never exports real applicant information.
Ask AI about this sectionRoute a compliance question #
Use the affected check reference for an application question, the member record for an access question, and the event details for an audit question. Do not put raw identity documents into a support message. Internal sample records do not confer live submission approval.
Ask AI about this sectionFollow the interactive walkthrough #
- Open Help & tutorials in the intended Organisation section.
- Select this guide and read the preparation instructions.
- Choose Start practice walkthrough to inspect the synthetic example.
- Follow each highlighted component. Use Back to revisit its explanation and Retry if loading interrupted the step.
- Use Exit tutorial to save your place; choose Resume walkthrough from this guide later.
- If you arrived from a real workspace, use Return to workspace, then verify the actual record and your permissions before making a change.
Guided component walkthrough #
Each component has one short guided step. Read the explanation, then choose Next; Back revisits the previous component. The cursor only demonstrates useful navigation or an explicit action. Replay action repeats that demonstration, and Skip animation keeps the explanation. Use this written guide for feature details.
Organisation data records
- Organisation data records: Data & compliance brings together the organisation-level records available to an administrator. It does not replace consent, eligibility or identity checks on an individual application. Begin by identifying which kind of record your question concerns.
Find safeguards in the workflow
- Find safeguards in the workflow: The Checks, Users and Audit links identify where different safeguards are managed. Checks holds the application context, Users holds role and access information, and Audit holds recorded activity. Choose the location matching the task rather than treating this page as an approval screen.
Read retention and deletion status
- Read retention and deletion status: Read the Retention and deletion description and its status together. A needs-action indication points to work requiring attention; it is not a command to delete applicant records. Use the authorised retention process and check any applicable holds before a real deletion.
- Retention entries: Read each retention entry as a recorded control and its current status. An entry describes the product safeguards; it is not evidence that a particular applicant record has already been deleted.
Read organisation record counts
- Read organisation record counts: Organisation records compares current records with the total available. A current count is an internal record status, not DBS accreditation or proof that every launch requirement has been satisfied. Investigate the underlying records when a review needs more detail.
- Record summary scope: Organisation record counts help you understand the scope of this workspace. Use the relevant record list for individual cases; summary totals do not grant access to private evidence.
- Understand summary downloads: Download PDF and Download JSON appear only when the workspace supplies those authorised routes. When unavailable, the panel explains the restriction. This tutorial reads the sample summary and never exports real applicant information.
Route a compliance question
- Route a compliance question: Use the affected check reference for an application question, the member record for an access question, and the event details for an audit question. Do not put raw identity documents into a support message. Internal sample records do not confer live submission approval.