Match access to a real task
See this course’s project requirements
Assemble the fictional equipment register and its operating README from all six lessons.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Define the record schema, sample rows and quality checks.
- Document filenames, version history and the approved release.
- Justify retained fields and create a purpose-specific export.
- Specify role-based access with review and removal triggers.
- Provide a retention review schedule, hold checks and tested handoff.
Review and revise
Use these criteria to check your work and choose what to improve.
- Meaning: fields and row definitions support consistent interpretation.
- Traceability: accepted changes and the current release are identifiable.
- Proportionality: data and access match stated purposes.
- Continuity: lifecycle decisions and handoff questions are answerable.
Want more background?
The idea in everyday life
Sharing is not a single yes-or-no choice. A reviewer may need a summary but no editing rights; a steward may need to correct the source; a public audience may need only aggregate counts. You will design permissions for the fictional register and test the logic on paper, avoiding actual invites, account changes or external messages.
A person’s task determines the information and permission they need.
One step at a time.
Use the sample or information you have permission to use. Keep your work as you go. You can pause between steps.
- 1
Define three fictional roles: steward maintains the register, equipment reviewer checks item status, and public reader views session totals. Associate each role with a specific task rather than a broad title alone.
- 2
Give the steward edit permission to the working register. Give the reviewer view access to the minimized export from the previous lesson. Give the public reader only an approved aggregate report.
- 3
Choose named-role access for the practice plan rather than an unrestricted anyone-with-link option. Record the owner responsible for approving additions, changes and removal of access.
- 4
Add an access-review trigger when a person’s role changes or a temporary project ends. For the exercise, temporary reviewers expire after the session review, not at an invented legal deadline.
- 5
Simulate an access test: public reader requests the detailed register and should be denied; reviewer opens the summary and cannot edit the source. Save the expected permission matrix and escalation path.
See how it works.
Fictional permission matrix: steward can view and edit working checkouts; equipment reviewer can view a four-field item-status export; public reader can view totals by session only. A temporary reviewer asks for edit access "just in case." The owner declines because the defined task is review, and corrections can be submitted as a note to the steward. When the review ends, access is removed under the project plan. The public report is checked separately for unintended detail; hiding a column in the source would not be a substitute for creating an appropriately limited export.
Did you cover these?
- Each role has a stated task and data scope.
- Only the steward edits the working register.
- Temporary access has an owner and removal trigger.
What to finish
A three-role permission matrix, access tests and review trigger.
Watch for this
Treating a hidden column or a forwarded link as a reliable permission boundary.
How can I tell I understand it?
Explain why each role’s access matches its task.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-09-10
Read purpose-based adequacy, relevance and minimization guidance. UK-specific legal context is identified; the course teaches a practical design principle, not jurisdiction-wide legal advice.
Access: Free public reading; no account or certificate is required for this Life Starter course.
Reuse: Linked for reference. Examples, activities and assessments here are original; free access alone does not grant permission to reuse source text or branding.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.