Intro lesson
Who Can View Video, Export It and Keep It?
Create practical rules for camera use, recording retention and controlled access to footage.
Reviewed September 2026 · 3 minute read
Give each role only the needed action
| Practice role | Allowed purpose | Boundary |
|---|---|---|
| Operator | View assigned cameras for the approved task. | No automatic export or configuration authority. |
| Investigator | Review and export an approved incident. | Record request, approval and delivery. |
| Administrator | Maintain systems and permissions. | Named accountable access; review privileged activity. |
The owner should decide where capture is justified, who may access it and how requests are handled. Review privacy, workplace and other applicable requirements before enabling audio, biometrics or sensitive capture. A sign or a privacy mask alone does not settle those obligations.
Retention is a decision, then a capacity test
Specify routine retention by purpose, relevant requirements and the time needed to discover an event. Define who can preserve a particular incident before routine overwrite and when that preserved copy is reviewed or released under the approved process.
Do not advertise a universal “legal retention period.” Storage settings, available capacity and actual bitrate determine whether the designed retention is achieved. Verify the oldest usable recording after the system has operated long enough.
A useful export record
Worked example
An approved warehouse incident request
Record the requester, authorizing role, reason, camera IDs, time range and time zone, export operator, file identity, destination and handoff. Retain the original exported record; use a separate derivative when redaction or conversion is required.
Confirm the recipient and use approved protected delivery. A public social-media post is not the default evidence handoff.
An operator asks for “just one clip”
The operator can view live video but has no export permission. Write the request and approval path, then explain how to test that the role cannot export directly.
A useful answer
Route the request to the approved investigator or owner, limit it to the relevant incident and log the delivery. Keep role permissions in place and test the ordinary account rather than sharing an administrator password.
Put it into practice
Check what you learned
Choose an answer for each question, then check your understanding. Your answers stay in this browser.
Read the answers and explanations
- No; export is a separate permission decision.
Viewing and releasing copies create different responsibilities.
- From the documented purpose and applicable requirements, then verified against actual storage behavior.
A retention policy needs both a reason and a verified implementation.
- Use the authorized preservation process and record the handling.
Preservation should be specific, authorized and traceable.
Sources and further reading
- Axis: privacy in surveillance
Shows how privacy masks can limit unnecessary capture. Product features support a privacy plan; they do not decide the applicable legal requirements.
- Axis: video data as evidence
Explains how design, operation and export affect usable video records. The principles help build a documented handling process.
Keep your momentum
Ready for the next step?
If you can explain the example and your answer, try the next lesson. Revisit the feedback whenever you need it.
FryAVSI · Updated September 10, 2026
Reference this lesson or use a section’s direct link for a particular chart or example. How to cite an example.
FryAVSI · Northeast Ohio and beyond
Turn the learning into a working result.
Share the site, the requirement and the next step with our team.