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. The demonstration uses a fictional platform. Seven-day written acknowledgement and the Hungarian investigation limits are separate events.

Staffing and procedure changes can make permissions obsolete. Revoking access and deleting history are different decisions. Continued retention requires its own purpose and lawful basis under section 26 and GDPR. Keep necessary historical evidence only within those limits.

Apply the following rule: Section 26 limits internal-system personal data to what is indispensable for investigation and remediation. Data outside that scope must be deleted without delay. The five years in section 12 concerns the Commissioner’s protected electronic public-interest system, running from completion of the last investigative act or measure, followed by deletion. It is not a universal employer internal-system retention period. Document the specific purpose, lawful basis and review event.

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 every case five years after receipt, regardless of the country and any pending proceedings. Is that appropriate?

No. Identify the local rule, starting event and any limits or extensions. A uniform schedule may delete records too early or retain them too long. Document the decision by category, include copies and define who reviews a suspension of deletion, rather than keeping everything indefinitely.