Skip to content
10.x
Apple10.x
10.x
Apple 10.x Web 5.x

11 Group management ​

Most Enterprise settings are available only to users with the Enterprise Administrator role. On AvPlan Web, Glide Planner is also available to group dispatchers.

Open group management ​

Apple Web
Apple
  1. Open Settings.
  2. Select Enterprise Cloud.
  3. Under the required group heading on the AvPlan Enterprise Cloud screen, select the service to manage.

Select Dismiss when you finish.

Choose a management area ​

Apple Web

Aircraft Profiles and Flight Plans require Enterprise Pro. On AvPlan Web, they are marked Pro when the account does not have access. Company Routes does not require Enterprise Pro.

Apple
  • Group Settings configures credentials, app settings and shared pilot profiles.
  • Users manages group members.
  • Aircraft Profiles opens Manage aircraft.
  • Flight Plans opens Manage flight plans.
  • Saved Routes manages routes shared with the group.
  • Devices, Subscriptions, Documents, Maps, Waypoints, Plates and Map Overlays open the corresponding management page in the browser. Sign in if prompted.

Configure Glide Planner ​

Web

Group administrators and dispatchers with an active AvPlan Operations subscription can select Glide Planner to set Glide Range defaults and operational landing-site rules for the group. For administrators, it appears directly below Company Routes. Ordinary members can use the resulting settings in the planner but cannot change the group configuration.

Set group filter defaults ​

Glide Planner stays visible with an orange upgrade badge when AvPlan Operations is not included in your subscriptions. Enterprise Pro does not include AvPlan Operations.

  1. Select Glide Planner for the required group.
  2. Set Minimum runway (metres), Cruise time (min), Require runway lighting, Require instrument approach, and Exclude departure and destination as required.
  3. Open Landing Sites and select AD, ALA, and AvPlan as required. Helicopter landing sites (HLS) are excluded by default and do not have a general filter, but you can add a specific HLS to the allowed/blocked site table.
  4. Turn on Only use permitted landing sites when members must see only navdata airports explicitly allowed by the group.
  5. Turn on Lock settings for members when the group's cruise time, runway, and filter values must be enforced.
  6. Select Save. A confirmation appears when the settings have been saved.

With Lock settings for members off, the group values provide initial session defaults for members who do not have an applicable personal landing-site preference. Members can then adjust them. With it on, cruise time, runway, lighting, instrument approach, departure/destination, and Landing Sites controls are disabled in the Glide Range popover. Individual airport exclusions are never locked.

If a user belongs to more than one group, locked policies are combined conservatively: the lowest cruise time and highest minimum runway apply; any requirement to use lighting, an instrument approach, or exclude the departure and destination applies; and an aerodrome category is included only when every applicable locked group includes it. The popover lists the groups managing the settings.

Only use permitted landing sites is enforced independently of Lock settings for members. If a user belongs to more than one group that enables this setting, a navdata airport must be allowed by every one of those groups. Groups without saved Glide Planner settings do not change existing Glide Range behaviour.

Manage landing-site rules ​

Use Allowed and blocked landing sites to add one of these rule types:

  • Navdata airport — search for an airport, then choose Allow or Block.
  • Group waypoint — choose a waypoint belonging to the current group. Group waypoints can only be allowed.
  • Custom coordinates — enter a site name, latitude and longitude. Custom sites can only be allowed.

Select Add landing site to save the rule. For a navdata airport, select Allowed or Blocked in the rule list to change its action. Select the remove button to delete a rule.

Use Export CSV to download the group's navdata-airport rules. The file contains ident,action columns and uses allow or disallow for each action. Group-waypoint and custom-coordinate sites are managed in AvPlan and are not included in the export.

Use Import CSV to add or update navdata-airport rules in bulk. The first row must contain ident,action; each following row contains an airport identifier and either allow or disallow. Importing does not remove rules that are omitted from the file. If an identifier appears more than once, its last row is used.

Landing-site rules apply whether or not Lock settings for members is on. An allowed site bypasses that group's aerodrome category, minimum runway, lighting and instrument approach checks. A block from any group wins over an allow. Another group's locked aerodrome-category exclusion can still reject a site, and departure/destination or individual airport exclusions remain final exclusions. Group waypoints and custom coordinates are approval-only candidates; when Only use permitted landing sites is active they must satisfy every applicable group's permitted-site policy. AvPlan derives their ground elevation from terrain data.

Configure group settings ​

Apple Web
Apple
  1. Under the required group heading, select Group Settings.
  2. Under NAIPS Details, enter the group’s NAIPS Login and NAIPS Password as required.
  3. Under App Settings, select the settings that apply to the group:
    • Group Aircraft Only
    • AvPlan Live Enabled
    • AvPlan Live Group Only
    • AvPlan Live Share Active Plan
    • Apply Contingency Fuel to Alternate Legs
    • Burn Contingency Fuel Between Stages
    • Use Advanced Loading
  4. Select Save.

Manage pilot profiles ​

Apple Web
Apple
  1. Under the required group heading, select Group Settings.
  2. Select Add Profile to add a pilot profile, or select an existing profile to edit it.
  3. Enter or update the profile details.
  4. Select Save on the group settings screen.

To remove a profile, swipe it to the left, select Delete, then select Save.

Manage members and services ​

Apple Web
Apple
  • Select Users to open the native Group Members screen. Select Add to search for or create a user, select a member to edit their details or role, or swipe a member to the left to remove them.
  • Select Devices, Subscriptions, Documents, Maps, Waypoints, Plates or Map Overlays to open the corresponding management page in the browser. Sign in if prompted.

Manage company routes ​

Apple Web
Apple

Select Saved Routes to open Shared Routes. Select Add to share a route, select a route to edit it, or swipe it to the left to delete it.

Manage group aircraft ​

Apple Web

See Manage aircraft to share, update or stop sharing an aircraft profile.

Share NOTAM notes ​

Web

Group administrators and dispatchers with Enterprise Operations can share advice about current or upcoming NOTAMs with group members.

  1. Open the group, select NOTAM Notes, then select Add Note.
  2. In NOTAM, enter an Airport or FIR. Optionally enter a NOTAM number or text, then select Search. Select a NOTAM, review its complete text, then select Next.
  3. In Note, enter your advice and select Low, Medium or High in Priority, then select Next.
  4. In Delivery, use Show to to choose All group members or select specific recipients. Choose Members, tech logs, Aircraft registrations or Type profiles. You can combine members and tech logs with either aircraft option.
  5. Review any warnings, then select Save Note. Use Back to review earlier choices before saving.

Select tech logs to send the note to their linked group members, regardless of the aircraft they are currently using. Names entered only as crew text do not receive the note.

Choose Aircraft or Type to reach members using a matching aircraft from the group fleet in an active flight plan. Profiles with the same ICAO type code reach the same aircraft types; choose individual registrations for advice about particular aircraft.

A matching plan on any signed-in device can make the note visible on the member's other devices. Changing aircraft may leave it visible while another device still uses a matching aircraft, or an offline device has yet to reconnect.

Note saved confirms the save. Delivery may take a little time, and you can save even when the recipient preview is temporarily unavailable. If saving fails, your draft stays open so you can retry.

Members see shared notes beside their personal notes in Terminal and structured briefings, labelled with the group name and priority.

Check recipients ​

Use search and column filters to find a note. Open its three-dot menu and select View recipients to check recipients and delivery status.

Delivered means the note is available to the member; it does not confirm they have read it. Syncing or Retrying means delivery is still in progress. The list updates automatically.

Edit or delete a shared note ​

  1. Open the note's three-dot menu and select Edit.
  2. Change its text or priority, then select Next to review Delivery.
  3. Select Save Note.

To write a note for a different NOTAM, select Add Note.

WARNING

Deleting a shared note removes it from recipients. Deleted notes cannot be restored from this screen.

To delete one note, open its three-dot menu, select Delete, then confirm Delete.

To delete several notes:

  1. Select their checkboxes. The header checkbox selects the current page.
  2. Open the three-dot menu beside Add Note and select Delete selected.
  3. Confirm Delete. If any notes remain selected, retry deleting them.

Changing pages, sorting or filtering clears the selection. Notes are also removed when their NOTAM is confirmed cancelled or expired.

Connect an integration to a group ​

Web

Group administrators with an active Enterprise Operations plan can create one API key for an integration. The key allows the operations listed in the API reference. Store it securely and share it only with the integration that needs it.

  1. Open the group and select API access.
  2. Enter a Key name, then select Create key.
  3. Select Copy key and save the key in your integration's secure configuration. This is the only time AvPlan displays the full key.
  4. Use the displayed API base URL when configuring the integration.
  5. Select Hide key when you have saved it.

The key remains valid until it is rotated or revoked. It continues working if the administrator who created it leaves the group. Deleting the group ends its API access.

To rename the key, change Key name and select Save name.

Read the group API documentation ​

Group administrators can browse the API reference, including the supported routes and request and response examples. You can read the documentation before creating a key.

  1. In API access, select View API documentation.
  2. Filter the reference by resource, then expand an operation to see its parameters and examples.
  3. Select Download OpenAPI YAML to save the specification for your integration tools.
  4. Select Back to API access to return to key management.

Replace a group API key ​

Rotating the key stops integrations using the old key immediately. Be ready to update the integration's configuration.

  1. In API access, select Rotate key.
  2. Select Confirm rotation.
  3. Select Copy key and replace the key in the integration's secure configuration.
  4. Select Hide key after saving it.

Revoke group API access ​

Revoking the key stops integrations using it immediately.

  1. In API access, select Revoke key.
  2. Select Confirm revocation.

To reconnect an integration later, create and save a new key.

Operational information should always be verified against current regulations and official sources.