For admins. A restricted record becomes read-only and drops out of combined reporting.
Steps
- Open Admin, then the page headed Right to restriction.
- Type a reference, given name, family name or preferred name. Use two to 120 characters. Press Search.
- Check the reference and name in the results. The column Restricted? shows Yes or No.
- Type the reason in the box. It must be at least ten characters.
- Press Restrict from processing. The row now shows Yes.
- To end it, write why in the box and press Lift restriction.
If it goes wrong
- If the search cannot load, reload the search before changing anything.
- If nothing matches, check the spelling or try the reference code.
- If the button does nothing, the reason may be too short.
What restriction does
The right to restriction lets a person ask that you stop using their data while a concern is looked into. The record stays, but it is paused.
Every working row for the person becomes read-only. They are left out of combined reports.
Using it carefully
Restriction does not remove a safeguarding duty. If there is a risk to a child, speak to your DSL before and after you restrict.
Write a reason that a stranger could understand later.
Lifting it
Lift a restriction when the reason has gone, and record why. The change is logged like the first.
Who can do it
Only admins. Others are told this page is for administrators.
How it links together
A restricted person shows as read-only on their record, in the planner and in reports. Staff can still read, but they cannot add or change work until it is lifted.
Every change goes in the audit log. See the guides on subject access requests and the audit log.
- SearchSearch by reference or name
- RestrictWith a written reason
- PausedRead-only and out of reports
- LiftedWith a reason
