Permission
A Permission records whether an operation may use a specific Airspace Zone. Permissions are created against a Mission when that mission’s envelope intersects managed or restricted zones. Flight Plans inherit those mission permissions by reference.
Role in the platform
Permissions connect operational envelopes to published Airspace Zones. Creation is normally automatic at mission create time. Airspace Managers grant or deny pending permissions for zones they manage. Automatic zone evaluation never rejects: it returns Approved or Pending. Rejection is either an Airspace Manager decision on a pending row, or the flight-plan strategic deconfliction override.
Core fields
| Field | Description |
|---|---|
permission_uuid / permission_udai_id | Public identifiers |
parent_type | MISSION or FLIGHT_PLAN |
parent_uuid | Parent mission or flight plan |
zone_uuid | Target Airspace Zone |
manager_org_uuid | Approving Airspace Manager organisation |
airspace_type | Derived from the zone type |
permission_status | Requested, granted, denied, and related states (see Enums) |
permission_reference | Optional manager reference identifier |
valid_from / valid_to | Validity window |
remarks | Optional manager or system notes |
Behaviour summary
| Event | Permission outcome |
|---|---|
| Mission created; zone is AwarenessZone and GreenZone | Auto-Approved |
| Mission created; any other intersecting zone | Pending for Airspace Manager |
| Flight plan created | Inherits mission permission rows by reference |
| Flight plan envelope overlaps an active approved plan | Intersected zones on this plan force-Rejected (deconfliction) |
Airspace Manager PUT /permissions/{uuid} | Grant or deny from Pending |
Full matrices: Mission Planning API: Permission Auto-Approval Rules.
Related APIs
Last updated on