Design an authorised access matrix before sharing location information

Match each person’s access to a specific agreed task instead of distributing one powerful account.

Start with roles and tasks

Use an invented small fleet scenario and list roles such as an authorised coordinator, an administrator and a person responsible for answering privacy questions. Do not put real staff names or live journey details in the training sheet. For each role, write the specific task it needs to perform. A desire to see everything is not a defined task. This exercise does not grant account access or determine legal authority. It helps an organisation ask whether its proposed sharing arrangement matches the openly agreed purpose and appropriate professional advice.

List information separately from features

Make columns for current status, historical journeys, exports and account administration, using the actual service’s documented categories when one is being assessed. Mark which role needs which information and why. Do not assume that access to one view requires access to every record. Keep the provider’s permission model distinct from your desired policy: a service may not support the separation you want. That mismatch is a question to resolve before use, not a reason to share an administrator’s credentials among everyone who needs a limited report.

Protect authorised accounts appropriately

Use each service’s official account instructions and organisational process. UK NCSC guidance supports two-step verification for important accounts where available; it is general security guidance, not a guarantee against every attack or Zimbabwean law. Never ask another person to send passwords, recovery codes or one-time login codes to complete the matrix. Identify how authorised users will obtain the appropriate help without placing secrets in a shared document. Keep account administration with the responsible people and do not attempt to discover hidden permissions through experimentation on a live service.

Try a Masvingo example

Imagine a Masvingo organisation using fictional roles to discuss who needs an operational summary and who administers accounts. The exercise shows that a person preparing a weekly activity summary may not need a complete location history. The group asks the provider whether the actual service can support the intended separation. No real journey is disclosed and no account changes are made during the lesson. This hypothetical example concerns appropriate information boundaries, not a claim that a particular product provides a feature or that a matrix alone establishes legal compliance.

Include review and removal

Add a review point for changed roles, departing users and a vehicle leaving the arrangement. Ask the authorised administrator to follow the actual service’s process when access needs to change. Do not leave old sharing links or exported copies outside the discussion. POTRAZ’s published legislation and regulations provide the local primary references for questions requiring qualified interpretation. The practical result is a clear proposed access pattern, with limits and unresolved matters visible. It reduces casual oversharing while preserving the distinction between an educational planning sheet and the actual legal and technical permissions governing a service.

Sources & further reading

Use these references to check the underlying guidance and any current local requirements. Practical worksheets and illustrative examples in this guide are original educational material.

  1. UK NCSC: Turn on two-step verification
  2. POTRAZ: Data Protection Act No.5of2021, original publication
  3. POTRAZ: SI155of2024, Data Controllers and Data Protection Officers

This guide is general information. Source notes are not a claim of independent professional review.