MAINSYSTEMS 
recognise limits on using organisational assets, access and information
1. Regulatory Concept & Core Standards
Today we will learn to recognise limits on using organisational assets, access and information. Throughout the video, consider the difference between knowing a rule and applying it to a decision. We will work through an example, identify a possible failure and develop a response that can be used at work. A code of conduct translates principles into guidance for workplace decisions. Present this course alongside the code actually adopted by the entity. Examples help interpret situations without creating internal rules that the organisation has not approved.
Entrusted access serves an authorised purpose. Technical ability to open data does not authorise reuse. Civil-service rules emphasise economical, effective use of entrusted resources for their assigned purpose; private organisations have their own applicable rules. Whistleblowing files additionally remain subject to section 21 access restrictions.
Apply the following rule: Section 21(2) requires reports and related documents to be retained for five years from receipt. Earlier closure does not change that starting event. The Act separately requires an electronic register with specified particulars. Under section 21(3), only the competent person may access internal reports, related documents and the register; the Ministry uses its authorised employee. Assess irrelevant data and other legal retention grounds separately.
2. Practical Implementation & Procedure
Before using a resource, check purpose and authority. Before sharing, verify recipient and need. Use approved methods and avoid personal accounts where procedures prohibit them. Report mistakes promptly through the proper route. Contain the problem and preserve records rather than conceal it. 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
An employee accesses tender information to help a friend bid. The system permits access, but the purpose falls outside their duties and may compromise equality and confidentiality. Technical permission does not legitimise use. 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: If the system allows a document to be opened, may it be used for any purpose? 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. Authority depends on role and purpose. Technical permissions are an operational boundary, not unlimited permission. The code and procedures guide legitimate information use.
One mistake to avoid is: confusing technical capability with functional authorisation.
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.