The Settings module is the central control area for your entire organisation in Aerolync. Every option you configure here applies organisation-wide and can affect pilots, flight instructors, staff, and automated workflows immediately.
Only users with the admin role can access and modify Settings.
How to open Settings
- Navigate to Settings in the main menu.
- Select one of the settings groups listed below.
- Review the current values before making any changes.
- Save your changes when you are satisfied.
Settings groups
The module is divided into eight groups, each covering a distinct area of your organisation's configuration.
- Aerodrome -- Local operational defaults such as landing fee amounts and whether landing fee logic is active. See Aerodrome.
- Flightlogger -- Rules that govern how the flight logging flow can start, including subscription requirements for rental aircraft. See Flightlogger.
- Scheduler -- Booking rules, planning cell behaviour, scheduler display hours, scheduler groups, and access conditions for reservations. See Scheduler.
- Finance -- Finance-wide defaults including minimum account balance requirements, invoice template configuration, and billing defaults. See Finance.
- Subscriptions -- Creation and management of subscription types that are later assigned to relations. See Subscriptions.
- Relations -- Reusable organisational items such as roles and labels used for classification, filtering, permissions, and communication targeting. See Relations.
- Aeromail -- Sender-side email configuration including sending profiles, sending domains, and domain verification. See Aeromail.
- e-Mail notifications -- Automated outgoing messages that Aerolync sends for operational events such as booking confirmations, schedule overviews, defect alerts, and licence expiration warnings. See e-Mail notifications.
Before you change anything
Most changes in Settings take effect immediately and apply across the entire organisation. A single toggle or value change can alter how bookings work, whether pilots can start flights, or what automated emails are sent.
Good practices
- Review the current value of a setting and understand its purpose before modifying it.
- Communicate upcoming changes to affected staff or pilots in advance, especially for scheduler rules and subscription requirements.
- If your organisation has multiple administrators, agree on a change process to avoid conflicting edits.
- After making a change, verify the expected behaviour by testing the affected workflow (for example, attempt a booking after changing scheduler rules).
How Settings relates to other modules
Settings provides the defaults and rules that other modules rely on.
- Scheduler module uses the booking limits, planning cell duration, and scheduler groups defined here.
- Flightlogger module enforces the subscription requirement configured in Settings when starting flights.
- Finance module applies the minimum balance and invoice template settings when processing transactions.
- Relations module uses the roles and labels you define here for access control and classification.
- Aeromail module uses the sending profiles and verified domains configured here when sending campaigns.
- e-Mail notifications use the recipient lists you configure here when dispatching automated messages.
Some settings, particularly scheduler rules, can be overridden at the individual relation level through the Relations module's Account section. The values in Settings serve as the organisation-wide defaults.