Community beta. Guides are pending editorial review. Discussions are demonstrations; comments are not sent.

Cameras · Troubleshooting guide

How do I archive and share the right incident footage?

Create a focused incident clip, verify its contents and choose the recipient’s access deliberately.

Monarch team

Draft · Nov 13, 2026 · 4 min read

Editorial review pending. This sample article demonstrates the design; verify model-specific instructions before use.

Before you start

For authorized users preserving an incident from available camera history. Follow your organization’s evidence-handling and retention procedures; this is a product workflow, not a legal chain-of-custody certification.

Find the right troubleshooting path

Symptoms, possible causes and next checks
What you observeWhat to investigateNext check
Archive action unavailableRole or organization restrictionAsk an administrator to check archive permissions.
Clip still processingArchive is not readyCheck status before promising a completed export.
Recipient can view but cannot downloadSharing permission differsReview the intended view/download setting.

Use these observations to narrow the cause; they are not a definitive diagnosis.

Work through the checks

  1. Define the incident interval

    Record the camera, incident identifier, time zone and start/end times. Include enough context before and after the event to explain what happened. Play that interval before creating the archive so you do not preserve the wrong date or a similarly named camera.

    Reference: Archive Recorded Video Footage (opens in a new tab)
  2. Create and label the archive

    Use the camera’s historical view to create the clip, selecting the required range and an informative title. Check whether the organization permits your role to archive. Private archive visibility differs from ordinary archive visibility; choose according to the audience and your organization’s policy.

    Reference: Archive Recorded Video Footage (opens in a new tab)
  3. Wait for completion and review the result

    A longer clip can take longer to prepare. Open the resulting archive and check its camera, duration and the first and last moments. If using multiple cameras, inspect each output rather than assuming the combined result proves every individual clip is correct.

    Reference: Archive Recorded Video Footage (opens in a new tab)
  4. Choose viewing or download access

    From Cameras > Archives, open the completed archive and select Share. Choose whether the recipient should only view it or also download it, and set an appropriate expiration. Confirm the recipient address before sending. A viewing link and a downloaded file have different lifecycles.

    Reference: Sharing Video (opens in a new tab)
  5. Verify the handoff and record it

    Have the intended recipient confirm access through the approved delivery process. Keep a record of the clip identifier, recipient, sharing settings and handoff time. If the organization requires a local copy, verify the downloaded file plays and store it in the approved location.

    Reference: Sharing Video (opens in a new tab)

Verify the result

Confirm the clip includes the incident, the correct camera and adequate surrounding context. Verify the intended recipient’s access and expiry. Do not close the request solely because an archive job was submitted.

If the issue remains

For processing failures, collect the archive identifier, source camera, requested interval and error message. For missing controls, ask an Org Admin to inspect role customizations and archive restrictions.

Official Verkada walkthrough

Watch the official tutorial

Official Verkada tutorial linked from the product documentation. Interface details may differ from your current Command version.

Official documentation

Sources checked November 13, 2026. Monarch’s diagnostic sequence combines these references with practical verification checks. Editorial review pending.

Join the conversation

Share what worked for you, or ask a follow-up. No account needed.

Demonstration discussion · Fictional people and comments.
Brenna H.

Security coordinator

Checking the first and last frames caught a clip that started after the actual incident in our practice run.

Victor E.

IT operations

I like separating the archive being ready from the recipient actually being able to open it.