Public Safety & Security with FlightHub 2
A useful aerial view should reach the people who need it.
A pilot may see an important detail while command is looking at an older map and a ground team is working from a radio description. The coordination challenge is not simply getting a drone airborne. It is getting timely, understandable information to the right people without confusing an observation with a confirmed fact.
DJI FlightHub 2 provides tools for livestream collaboration, telemetry viewing and shared map annotations. Used within a clear operating process, these can help pilots, supervisors and field teams build a shared picture of an incident or site.
This is Part 3 of our FlightHub 2 series. Read Part 1: Starting and Scaling a Drone Program for fleet and team foundations, and Part 2: Inspection, Monitoring and Surveying for repeat collection and post-mission analysis.
More than a livestream window.
Combine a relevant camera view with location, timing and an understood task.
Livestream sharing
DJI describes shareable livestream links so stakeholders can view operations without direct platform access. Its August 2026 public-cloud update adds multiple device feeds within one sharing link.
Live annotations
Points, lines and polygons can provide common map references. A search area, observation or route is easier to discuss when the team understands the same labelled location.
Telemetry and device context
DJI’s public-safety guide describes telemetry viewing alongside livestreams and annotation synchronization. Use this context to support coordination, not to assume an unbroken or delay-free view.
Multiple perspectives
DJI describes simultaneous livestream viewing. Additional perspectives can be useful when each has an assigned purpose; more windows do not automatically mean better situational awareness.
Before an incident, decide who watches each feed, who can request a different view and who communicates observations to field teams. Without that structure, several people may see the same event while nobody owns the handover.
Confirm current availability for the intended deployment. The August 2026 sharing enhancements are described for public cloud; this article does not assume identical features in every plan or in On-Premises.
Use aerial information to support a defined response.
The following are illustrative workflows, not claims of adoption by a Canadian agency.
| Scenario | Potential FlightHub 2 contribution | Human confirmation needed |
|---|---|---|
| Search support | Share an aerial view, mark an observation and identify an assigned search area on the common map. | Verify what was observed and its location. Coordinate with the search lead; an image or thermal signature does not establish identity. |
| Fire or hazardous-site observation | Provide command with a relevant camera view and mapped points of interest while field personnel remain in their assigned roles. | Interpret conditions with the responsible incident team. Do not treat aerial appearance as proof that an area is safe to enter. |
| Flood or storm assessment | Share current visible conditions around access routes, facilities or affected areas. | Confirm observation time, coverage gaps and field conditions before making access decisions. |
| Scene documentation | Organize imagery and share context for subsequent review or reconstruction work. | Use an approved collection and evidence-handling method. A livestream is not automatically a validated measurement or evidentiary record. |
Make uncertainty part of the handover.
“Possible person near the marked location, observation time 14:32, not yet confirmed” is more useful than an unqualified declaration. Agree on terms that distinguish a suspected observation, a verified finding and an action already completed.
Keep the pilot's responsibility clear.
Command may need a particular view, but the pilot and responsible operational team still need to assess whether the request can be performed safely within the approved operation. A software control or remote-dispatch option does not itself establish permission to fly.
Verify the alert before deciding the response.
For an industrial site, the useful sequence is often alert, review, verification and an accountable handover.
A security operation may use recurring observation routes, an operator-requested check or an integrated alert to initiate a review. FlightHub 2 can provide shared aerial information and, with supported configurations, remote mission workflows. That does not mean every alarm system connects directly or that an alert should automatically trigger a flight.
Illustrative example: an after-hours facility alert.
A designated operator receives an alert through the site's established process. After confirming that a drone task is appropriate, the operator uses an approved mission to obtain a relevant view. A supervisor reviews the feed, the team records what was actually observed and authorized site personnel handle any ground follow-up.
The operator might identify an ordinary explanation, an unresolved condition or a reason to escalate. A person or vehicle appearing in an unusual place is not automatically evidence of wrongdoing. Keep observation, interpretation and response separate.
Automate only after commissioning the process.
DJI’s August public-cloud update describes configurable scheduled and triggered workflows, AI analysis and notifications. Treat a proposed integration as a project requiring compatibility checks, testing and exception handling. Confirm what happens with a false alert, failed launch, interrupted stream or missing recipient before relying on it.
For broader application context, see our Dock-based security applications guide. Hardware and software support must still be checked for the exact configuration; a concept article is not a compatibility certificate.
Start narrow. One clearly defined area, one justified mission and one accountable recipient are better pilot-project foundations than an open-ended promise to monitor everything.
Brief, observe, locate, confirm and hand over.
A recommended operating sequence to test in an exercise before depending on it during an event.
Brief the information need.
Identify the question, area of interest, intended viewers and operational lead. Confirm who can request changes and how the pilot will receive them.
Establish the shared view.
Check that the authorized viewers can open the feed and understand its source and observation time. Confirm voice or other fallback communications separately.
Mark the relevant observation.
Use an agreed map reference and a concise label. Communicate uncertainty and verify location confidence rather than treating every pin as a precise surveyed position.
Confirm the recipient and action.
Ask the responsible person to acknowledge the observation. Record whether the next step is further aerial review, a ground check, escalation or no action.
Close out and review.
Preserve the records needed under the organization's process, document outcomes and review gaps in coverage, connectivity or handovers. Remove temporary access when it is no longer needed.
This sequence is editorial guidance, not a claim that FlightHub 2 automatically records every decision or enforces every step. During evaluation, test which records the selected deployment actually captures and what must remain in the incident-management or reporting system.
Sharing should be intentional, not unlimited.
Decide who needs access, what they need to see and what happens to the information afterward.
DJI offers project permissions and public-cloud and On-Premises deployment options. Those are useful components of an information-management design, not automatic proof that a particular organization's privacy, security or procurement requirements are satisfied.
Set access before the incident.
Differentiate administrators, operators and viewers. Test the actual access controls and sharing behaviour. Establish who may create a link, distribute it, record a stream or retain an output, and how temporary sharing will be ended.
Keep live coordination separate from evidence handling.
A stream used for situational awareness may not provide the original files, metadata or handling history required by the receiving team. Agree on the evidence workflow with the responsible specialists before collection. Do not assume a downloaded clip or generated report satisfies it.
Evaluate the architecture, not just the interface.
Review hosting, access, retention, exports and integrations with the organization's IT, security and information-governance team. Do not assume On-Premises and public cloud have the same features, or that choosing either architecture establishes compliance.
Our DJI Enterprise drone data-security guide for Canadian buyers provides context for that discussion. Organization-specific requirements should be assessed by the responsible team.
Test what happens when things do not go to plan.
A successful demonstration is a starting point, not a complete readiness assessment.
Technical readiness
- Confirm aircraft, Dock, controller, payload and firmware compatibility for each required feature.
- Verify the plan and public-cloud or On-Premises capabilities being proposed.
- Test stream quality, delay, mobile access and realistic viewer numbers.
- Budget applicable streaming usage, storage and integration costs.
- Exercise connection loss, unavailable feeds and failed notifications.
Operational readiness
- Assign flight, command, viewing and ground-response responsibilities.
- Agree on labels for suspected and confirmed observations.
- Verify handovers, map references and fallback communications.
- Set access, sharing, retention and evidence-handling procedures.
- Confirm the proposed operation is within the team's applicable authority and procedures.
Measure coordination, not just flight time.
Useful exercise measures include time to establish a shared view, successful access by intended viewers, acknowledged observations, location clarification requests and unresolved handovers. These are suggested evaluation measures, not a list of guaranteed native FlightHub 2 reports.
For the organizational structure behind this work, return to Part 1. For post-mission comparison and reviewed reporting, continue with Part 2.
Public-safety and security FAQs
Can a stakeholder view a livestream without full platform access?
DJI describes shareable livestream links for that purpose. Verify access controls, recipient experience and current deployment support before using sharing for sensitive operations.
Can one sharing link show multiple devices?
DJI’s August 2026 public-cloud update describes that capability in Livestream Sharing 2.0. Confirm current availability and test the required devices, layouts and viewer conditions.
Can shared annotations help organize a search?
Points, lines and polygons can provide common references for areas and observations. They support coordination, but do not prove that an area was completely searched or that an observation was correctly identified.
Does a map pin establish an exact target location?
Do not assume that. Confirm how the location was produced and its suitability for the task. Communicate uncertainty and verify the reference with the receiving team when location is consequential.
Does FlightHub 2 authorize BVLOS or automated response flights?
No. Software capability is not aviation permission. The responsible operational team must confirm the applicable authority and conditions for the proposed flight.
Will it replace incident command, dispatch or evidence systems?
This guide does not establish that it replaces any of them. Define the needed workflow, test integrations and records, and keep accountable decisions and required information in the systems designated by the organization.
Does the same feature set apply to On-Premises?
No parity is assumed here. Check the documentation and entitlements for the exact deployment. Features explicitly announced for public cloud should not be promised for On-Premises without verification.
From program foundations to operational use.
Part 1 · Build the program
Fleet tracking, teams and operational control: organize projects, access and handovers before expanding.
Part 2 · Deliver useful results
Inspection, monitoring and surveying: repeat collection, compare evidence and validate outputs.
Part 3 · Coordinate the response
This guide: share relevant views, locate observations and hand information to accountable people.
Related application guides
For broader scenarios, read our Dock 4 and Matrice 5TD public-safety guide and emergency-response applications article. These complement the workflow discussion; they do not establish support for every FlightHub 2 feature on every configuration.
Official DJI sources
- DJI Enterprise public-safety feature guide: FlightHub 2 annotation synchronization, telemetry viewing, location-sharing context and public-safety workflows. Source of the credited illustration and annotation demo. Historical hardware-specific instructions should be checked against current documentation.
- FlightHub 2: A New Era of Cloud-Based Drone Intelligence: dashboard, live annotations, stakeholder livestream sharing and simultaneous views.
- August 2026 FlightHub 2 public-cloud update: multi-device livestream sharing and configurable workflow capabilities.
- FlightHub 2 project-permission update: customizable project roles and separation of output, device-operation and administration responsibilities.
- FlightHub 2 official FAQ: deployment options, device support and usage accounting. Official regional page; verify the intended Canadian configuration.
Prepared November 2026. Product capabilities are described from DJI manufacturer sources, not independently validated operational outcomes. Compatibility, plans, usage allowances and feature availability can change. Scenarios, checklists and exercise measures are editorial recommendations, not claims of adoption by a Canadian agency or site. Manufacturer credits identify image sources; no open reuse licence is asserted. This article does not establish organizational compliance, evidentiary admissibility, target identity or aviation authorization.
Build a shared picture your team can act on.
Talk with Unmanned Canada about the people, sites and information flows behind your proposed drone operation. Start with a defined mission and a testable handover, then evaluate the supporting equipment and software.
