Testing settings and reviewing access

1. Regulatory Concept & Core Standards

In this video we will consolidate a skill: review functions and access after platform changes. Use the case to test what you would do in a similar situation. We will explain the proposed response step by step so that you can understand each choice and recognise when more information would be needed. The demonstrations in this course use a generic platform and fictional data. Field names depend on the chosen product. The aim is to understand which settings to look for and how to verify the result, keeping technical administration rights separate from access to case content.

Settings may become unsuitable after staffing changes, new integrations or product updates. Reviews must cover who has access, which actions they can perform and how actions are logged. Plan recovery and continuity tests with the technical team. Real cases need not be exposed to verify permissions and processes.

Apply the following rule: Section 11(1) requires the reporting register to be kept for three years from receipt. It records receipt date, subject, result and completion date, plus the prescribed identifying details for non-anonymous reports. Do not equate the register with every document from other proceedings. Those documents need their own lawful basis, purpose and restricted access. GDPR requires proportionality and minimisation.

2. Practical Implementation & Procedure

List active accounts, compare them with current roles and remove unnecessary permissions. Test changes with fictional data and document results. Check that exports, notifications and support access remain restricted. Repeat affected tests after changes and retain the approved configuration. A review without an owner or evidence is difficult to monitor. Before moving on, turn this procedure into a sequence you could explain to a colleague. Identify the first check, the action that depends on its outcome and the record that allows the decision to be reconstructed. Follow the sequence on screen and identify the point where an error would change the result.

3. Case Study & Compliance Action

A former channel manager moves departments but retains case access. The review identifies the account and removes powers associated with the previous role. The team confirms the block while preserving historical records of legitimate actions performed during the appointment. Now read the case carefully. Separate established facts from information you would still need to confirm. Do not add motives or events that have not been described. This distinction matters when choosing a response proportionate to the information available.

The exercise is as follows: Does revoking someone's access require deleting the history of their actions? Choose an answer and write one sentence explaining it. During the pause, compare your choice with the criteria we have just considered. Also think about the material you would retain to explain the decision later.

No. Future access and retention of historical records serve different purposes. Remove powers that are no longer needed while preserving relevant records under the rules applicable to the case.

One mistake to avoid is: leaving old accounts active to avoid reviewing permissions.

Now apply the national rule to a second decision. The system deletes all data five years after closure. Is that suitable?

No. The section 11 register is kept for three years from receipt of the report. Other documents and related proceedings require their own purpose and legal basis. One universal date may cause premature destruction or unnecessary retention. Record the rule, trigger and deletion owner.