DocsBeta

About

About these docs

Scope, audience, structure, and conventions used in the Aerolync documentation — plus how to get additional help.

Last updated 2026-03-28

Who this documentation is for

These pages are written for all Aerolync users:

  • Platform users — administrators, flight instructors, operations staff, and finance staff who use the web-based management platform
  • Pilot App users — pilots, students, and other users who use the mobile app for day-to-day operations

Whether you are configuring the system for the first time or looking up how to perform a specific task, this documentation is designed to help.

How the documentation is organised

Module-based navigation

The documentation follows the same structure as the Aerolync Platform and Pilot App. Each module has its own section in the left-hand navigation:

  • Platform modules are grouped under "Apps" — Relations, Schedule, Fleet, Finance, Flight Training, and so on
  • Pilot App has its own section covering each screen in the app
  • Settings covers all organisation-wide configuration
  • Getting Started provides orientation for new users

Page structure

Most pages follow a consistent pattern:

  1. What you see — a description of the screen or feature and the information it shows
  2. How to use it — step-by-step instructions for common actions
  3. Common tasks — practical scenarios with numbered steps
  4. Good practice — operational tips and recommendations

Platform vs Pilot App pages

  • Platform pages explain how modules work, how they connect to each other, and how to manage data. These pages are typically aimed at administrators and flight instructors.
  • Pilot App pages explain the app workflow itself and are written for end users. They stay intentionally focused on the app experience without requiring platform knowledge.
  • When the same process spans both products (for example, flight logging), cross-references link the relevant pages.

Documentation conventions

  • Module names and button labels appear in backtick formatting
  • Steps are numbered when order matters
  • Bold text highlights important concepts or field names
  • Internal links like Schedule take you to other documentation pages
  • Each page lists the user roles it is relevant to in the metadata

Getting additional help

If you cannot find the answer you need in this documentation:

  • Contact your organisation's administrator — they can help with organisation-specific questions, account issues, and configuration
  • Contact Aerolync support — email support@aerolync.com or call +32 2 669 6009 for technical support and platform issues

Contributing to these docs

This documentation is maintained by the Aerolync team. If you notice an error, find a gap, or have a suggestion for improvement, contact support and we will review it.