Leon Software manual
Auto Light Dark
Auto Light Dark
Breadcrumbs

Managing User Access in Leon

Leon does not rely on a single switch to decide what a logged-in user can see. Instead, several independent layers work together: privileges decide which parts of the system are available, bases limit the user to their own organisational unit, aircraft settings narrow the fleet in scope, and dedicated rules apply to the Crew App and to aircraft owners. Each layer is described below.

1. Privileges - general information

Privileges are the first layer of access control. A privilege group defines which modules and views its members can open and whether they can only view the data or also edit it. Anything not granted to the group stays hidden: it does not appear in the menu and cannot be reached directly.

Privilege groups are managed by an administrator in Settings > Users > Privilege Groups. A group can be narrowed further by assigning aircraft to it, so that its members see only the flights, maintenance and other activities related to those tails (see section 3).

Each user belongs to exactly one privilege group. Leon does not combine several groups on one account, so a user's access is always the access of their single group.

When someone needs broader or different access than their colleagues, create a dedicated privilege group that contains exactly the permissions they require, and assign the user to it.

For full details, see the Privileges article in Leon Wiki.

2. Bases — Access Scoped to Organisational Units

Bases restrict access on a different principle than privileges. Instead of controlling individual views, they limit the user to the organisational unit they belong to. A user assigned to a base sees that base's fleet, crew and operations, while data from the operator's other bases remains hidden.

Two settings located in the SETTINGS tab control this behaviour:

  • Limit users to their own base — an option in the Settings tab. When it is enabled, every user sees only the data of their assigned base.

  • User base aircraft — an option in the dropdown on the Aircraft tab of a privilege group. It limits the aircraft available to group members to those registered at the user's base.

For a complete explanation of multi-base setups, see the Multi-Base Operations article in Leon Wiki.

3. Aircraft Assigned to Privilege Groups

The AIRCRAFT tab of a privilege group decides which aircraft its members can see and work with.

This allows restricting the user view to the activities performed on:

  • selected aircraft

  • such as flights

  • reservations

  • scheduled maintenance

These restrictions do not apply to:

  • duties

  • non-aircraft configurations


The Aircraft list dropdown in the AIRCRAFT tab in Privileges selects how that scope is determined, with four modes available:

  • Fixed

  • Aircraft preferred crew

  • Aircraft owned

  • User base aircraft

For all configuration options, see the Privileges — Aircraft tab article in Leon Wiki.


3.1. ‘Fixed’ mode

Members see only the aircraft ticked in the table below the dropdown. The administrator picks the registrations manually, as per the screenshot below

1.png

Once the aircraft list is selected, a User assigned to the particular group can only access data on the available aircraft.

Example

As an example, we can look at Aircraft A-BCDE, which is not available for the User.

In the OPS section, a user can only access the aircraft one has access to, excluding A-BCDE

2.png

In the Sales section, a User can see the requests on the unavailable aircraft, but will not be able to access the details:

3.png

In the crew planning sections, Crew Timeline and Crew Calendar, the User will not be able to filter by the registration to which the User does not have access, nor will the User be able to assign the crew to a duty on the aircraft to which the User does not have access:

4.png

The same logic applies to the MX sections. There, any User has access to the aircraft that is available by the privileges setup. Below, the example from the MX > Fleet section:

5.png

Exemptions

The best example of an exemption from the standard rules is the Crew Qualification configuration.

The aircraft privileges rule applicable to this section is ‘all or nothing’, which means that the aircraft selected in the Privileges > Aircraft tab does not apply to the Crew Qualification configuration section.

Despite the lack of access to the A-BCDE aircraft, a User can still select the tail in the Certificate configuration:

6.png

A user can only be limited by either accessing the section or not - Privileges > Details tab > Admin-Operational Administrator setting.


3.2. ‘Aircraft preferred crew’ mode

Members see the aircraft on which they are listed as preferred crew, as set in the Fleet > Crew tab.

As an example, we can use the D-LEON aircraft and the crew directly assigned to this aircraft:

7.png


Access level-wise, a separate group of privileges needs to be set up, and the ‘Aircraft list’ mode is set to ‘Aircraft preferred crew’:

8.png

This mode is important for one main reason - View for the Crews.

It allows creating only one group of privileges for all the crew assigned to different aircraft, considering the crew have the same access levels to Leon. There is no need to create numerous groups for the crew assigned to each aircraft. Crew from the screenshot below is assigned to two aircraft, A-BCDE and D-LEON, and can see the flights unassigned to any tail:

9.png

It also applies to the Crew App.

3.3. ‘Aircraft owned’ mode

Members see the aircraft they own, with ownership set in the Fleet > Sales tab.

More information in pt. 5 in this article

3.4. ‘User base aircraft’ mode

Members see every aircraft registered at their operator base.

More information in pt. 2 in this article

4. Crew App Access

What a crew member sees in the Crew App is controlled in two places.

The first is the DETAILS tab of the privilege group, which holds Crew App–specific permissions defining what the user can see and do after logging in to the app.

10.png


The second is the operator-level settings. For example, Show "My aircraft schedule" in Crew App → My Schedule decides whether the My Schedule view also shows the schedule of the aircraft the crew member flies, or only their own duties.

11.png


To further limit user access within the app the “Schedule” setting in the DETAILS tab can be set to DENY, preventing a user from seeing any other aircraft schedules, especially if the aircraft mode is set to ‘Fixed’:

12.png



5. Access for Aircraft Owners

Aircraft owners can follow their own fleet in two ways: through the Owner Board in the leon.aero web version, or through the Owner App, a mobile application for iOS and Android in which owners view and manage flight requests for their aircraft. See the Owner Mobile Application article in Leon Wiki for details.

For an owner to access their fleet, four conditions must be met:

  • User access — the Owner has to have a User account created in Leon

  • Fleet assignment — the user is selected as the aircraft owner in the Settings > Fleet > Sales tab.

  • Phonebook setup — the user is set up as a Client in the Phonebook, with the Account field filled in.

  • Privilege configuration — a separate group of privileges should be created for the Aircraft Owners, and the following have to be set:

    • DETAILS tab - the privileges below should be selected as a minimum:

      • Owner App - set to EDIT

      • Owner Board - set to VIEW

    • AIRCRAFT tab - the Aircraft list mode should be set to Aircraft owned


Once the above-mentioned settings are applied and the conditions are met, an Owner will be able to access Leon with the correct overview:

  • Owner Board in Leon web-based version

13.png
  • Owner App

14.png



Last updated: