This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:general-setup [2019/09/05 12:48] ksenia |
leon:general-setup [2024/03/25 11:19] (current) rafal [Automatically mask PAX after given days] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== General Settings ====== | ====== General Settings ====== | ||
- | <box tutorial> | + | <box tutorial> |
- | This page includes many options/ | + | This section |
- | **__General settings__** | + | |
+ | * **Flight editing** - full section explained [[leon: | ||
+ | * **GAR emails** | ||
+ | * **Documents** - full section explained [[leon: | ||
+ | * **Sales Module** - full section explained [[leon: | ||
+ | * **Crew Planning** - full section explained [[leon: | ||
+ | * **Mobile Notifications** - full section explained [[leon: | ||
+ | * **Fuel** - full section explained [[leon: | ||
+ | * **Phonebook** - settings related to PAX | ||
+ | * **Crew App** - settings that apply to the Crew mobile app | ||
+ | * **Security** - settings that apply to the user login settings | ||
+ | ===== Tab ' | ||
- | | + | This tab consists of 3 subsections: |
- | * **Region** - select between EN & US to define the date-format. Also, when US region is selected Leon changes the date format displayed in the OPS section. Also, Flight Watch times indications: | + | |
- | * **Default | + | |
+ | * **Leon inbox settings** | ||
+ | * **Bases** | ||
+ | ==== General settings ==== | ||
+ | |||
+ | * **Operator ICAO** - an ICAO code by which an operator is recognizable by **Eurocontrol** (so that flight times can be imported from Eurocontrol straight to Leon's ' | ||
+ | * **Operator IATA** - an operator IATA code, used in 'Show Schedule' | ||
+ | * **Region** - select between EN & US to define the date-format. Also, when US region is selected Leon changes the date format displayed in the OPS section. Also, Flight Watch times indications: | ||
+ | * **Default weight | ||
* **Default airport category** - here you can set a default airport category for all airports available in [[leon: | * **Default airport category** - here you can set a default airport category for all airports available in [[leon: | ||
- | * **Default local currency, currency in Price lists or currency for fuel prices** - you can define them by selecting the currency from the drop-down box. | + | * **Default local currency** - you can define them by selecting the currency from the drop-down box. |
- | * **Options will change position of aircraft on planned flights** - when this box is ticked, a flight-option added in [[leon: | + | * **Options |
* **Display the experience table** - the table can be input to the user's profile, where you can add the past crew-experience before joining your company. More information [[leon: | * **Display the experience table** - the table can be input to the user's profile, where you can add the past crew-experience before joining your company. More information [[leon: | ||
* **Crew Panel** - option to choose between 'Auto publish' | * **Crew Panel** - option to choose between 'Auto publish' | ||
- | * **Crew age validation** - setting that validates age of cabin crew. There are 3 options available: ' | + | * **Crew age validation** - setting that validates age of cockpit |
+ | * **System notification recipients** - in this field, you can define a list of mail addresses that will receive system notifications. System notifications include notifications about integration errors, mailbox suspensions, | ||
* **Timeline additional markers** - section where you can create the ' | * **Timeline additional markers** - section where you can create the ' | ||
| | ||
- | **__Leon | + | ==== Leon inbox settings ==== |
- | You can send messages to Leon users by using ' | + | You can send messages to Leon users by using the ' |
{{: | {{: | ||
Line 27: | Line 47: | ||
| | ||
- | **__Bases__** | + | ==== Bases ==== |
If a company has more than one main **base** where the staff is located then you can define in Leon more bases and assign them to particular aircraft as well as to a proper crew and other staff members. Then you can filter particular pages by a proper base and view flights or duties only for that base. | If a company has more than one main **base** where the staff is located then you can define in Leon more bases and assign them to particular aircraft as well as to a proper crew and other staff members. Then you can filter particular pages by a proper base and view flights or duties only for that base. | ||
- | By selecting a **time zone** you can then select **Base Time** in a section OPS, right-hand filter (at the bottom). | + | By selecting a **time zone** you can then select **Base Time** in a section OPS, right-hand filter (at the bottom). |
+ | |||
+ | Bases can be used in [[leon: | ||
+ | |||
+ | [{{: | ||
+ | |||
+ | |||
+ | < | ||
+ | <span style=" | ||
+ | </ | ||
+ | |||
+ | ------------------------ | ||
+ | |||
+ | It is also possible to set up the **'OPS emails' | ||
+ | |||
+ | Once emails for bases are inserted, they can be selected as the 'Reply to' emails in the 'Email Templates' | ||
+ | |||
+ | __**EXAMPLE**__ | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | User is assigned to MEL user base in the profile (full edit profile, ' | ||
+ | |||
+ | Based on the 'User base', the assigned 'OPS email' is melops@man.com and the 'Sales email' is melsales@man.com. | ||
+ | |||
+ | In the 'Email Templates' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Once this template is used, the relevant base email will apply to the 'Reply to' field. Below, 'Sales email' assigned to MEL base: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The abovementioned functionality can apply to any email template in Leon. | ||
+ | |||
+ | |||
+ | ---------- | ||
+ | ==== Days off ==== | ||
+ | |||
+ | [{{ : | ||
+ | In this section, it is possible to select: | ||
+ | |||
+ | * **Weekend** - weekend days selection | ||
+ | * **Days Off List** - option to insert days off such as Bank Holidays, Christmas, etc. These selected days will be highligted light-green in the OPS CALENDAR and the CREW CALENDAR sections | ||
+ | |||
+ | |||
+ | ---------- | ||
+ | ===== Tab 'GAR emails' | ||
+ | |||
+ | [{{ : | ||
+ | |||
+ | **GAR** emails configuration can be found in a section Settings > General Settings as a separate tab. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | In this page you can insert a default ' | ||
+ | |||
+ | Here you can also choose the **format** of the file itself. Attached file can be sent either as **PDF** or **XLS**. The format can be switched to a different one before sending GAR in GAR window. | ||
+ | |||
+ | |||
+ | More information regarding GAR functionality in Leon can be found under [[leon: | ||
+ | |||
+ | < | ||
+ | |||
+ | ---------- | ||
+ | ===== Tab ' | ||
+ | |||
+ | The ' | ||
+ | |||
+ | * **Is account required** - checkbox that, if ticked, requires the new Phonebook entry to be assigned to an Account | ||
+ | * **Automatically delete PAX after given days** - option to set up Leon to automatically remove passenger details from the system if they are not assigned to flights within a specified timeframe. By default, this function will be turned off for all operators. More information below | ||
+ | |||
+ | ==== Automatically delete PAX after given days ==== | ||
+ | |||
+ | |||
+ | The ' | ||
+ | [{{ : | ||
+ | * **Delete PAX enabled** - option to enable automatic deletion. | ||
+ | * **Send notification 7 days before deletion to:** - specify an email address where a notification containing passenger names scheduled for deletion will be sent seven days before the deletion date. This field is mandatory if the **' | ||
+ | * **Delete PAX after** - a field where it will be possible to indicate the number of days (by entering a numerical value) after which PAX data will be deleted if PAX is not assigned to the flight within the specified timeframe. The minimum threshold for deleting PAX is 30 days. | ||
+ | |||
+ | < | ||
+ | |||
+ | It is **possible to exclude the PAX** that are not to be automatically deleted by selecting the **Never delete automatically** setting in the Phonebook > Passenger profile > ' | ||
+ | |||
+ | -------------- | ||
+ | ==== Automatically mask PAX after given days ==== | ||
+ | |||
+ | This setting automatically masks passenger (PAX) contact information not used in trip bookings or sales quotes within the past days. This function enhances data privacy and security. | ||
+ | [{{ : | ||
+ | The ' | ||
+ | |||
+ | * **Mask PAX enabled** - Activates the functionality | ||
+ | * **Mask PAX after** - Number of days after which PAX will be masked. | ||
+ | |||
+ | === Conditions === | ||
+ | |||
+ | For this functionality to work the following conditions have to be met: | ||
+ | |||
+ | * PAX cannot be a User | ||
+ | * PAX cannot be marked as ' | ||
+ | * PAX cannot be marked as 'Is representative' | ||
+ | * PAX is selected as a passenger on a past flight but was not assigned to a flight within the days indicated in the 'Mask PAX after' | ||
+ | |||
+ | === How it works === | ||
+ | |||
+ | [{{ : | ||
+ | Once the conditions for masking PAX data are met, the PAX details (currently ' | ||
+ | |||
+ | Additionally, | ||
+ | |||
+ | {{: | ||
+ | |||
+ | A User with the **Contact Mask** privilege set to ' | ||
+ | |||
+ | * **preview** the masked details in the PAX profile by clicking on the {{: | ||
+ | * **unmask** the details by clicking on the ' | ||
+ | |||
+ | If a User's **Contact Mask** privileges are set to **DENY**, the user will see the {{: | ||
+ | |||
+ | |||
+ | ---------------- | ||
+ | ===== Tab 'Crew App' ===== | ||
+ | |||
+ | In this tab, it is possible to implement the default settings for [[mobile: | ||
+ | |||
+ | ==== Fixed locations ==== | ||
+ | |||
+ | In this section, it is possible to add the fixed ' | ||
+ | |||
+ | If the clock-in/ | ||
+ | |||
+ | It is possible to add multiple locations. | ||
+ | [{{ : | ||
+ | To add the new location click on the 'Add New' button, fill in the required fields, and press ' | ||
+ | |||
+ | There are three columns available: | ||
+ | |||
+ | * **Location name** - Name of the location | ||
+ | * **Latitude** - Latitude in decimal | ||
+ | * **Longitude** - Longitude in decimal | ||
+ | [{{ : | ||
+ | __**EXAMPLE**__ | ||
+ | |||
+ | There are 3 locations inserted, as per the screenshot. | ||
+ | |||
+ | 'Hotel and ' | ||
+ | |||
+ | Clock-in happened between the two abovementioned locations and within a radius of 1km from each of them. | ||
+ | |||
+ | In this case, location Rental was picked by the Crew App automatically, | ||
+ | |||
+ | |||
+ | ---------------- | ||
+ | ===== Tab ' | ||
+ | |||
+ | In the ' | ||
+ | |||
+ | The additional security options are: | ||
+ | [{{ : | ||
+ | * **Force two factor authentication for all users** - 'Two factor authentication' | ||
+ | * **Trusted IP** - a section where trusted IP addresses can be inserted. IP addresses listed here will not be subject to 2FA authentication | ||
+ | * **Single sign-on settings** - a section where alternative way of signing in to Leon can be set up | ||
+ | * **Second factor validity time [h]** - This setting decides, that after logging in using two-factor authentication, | ||
+ | |||
+ | ------------------ | ||
+ | ==== Single sign-on settings ==== | ||
+ | [{{ : | ||
+ | The configuration panel can be accessed in the ' | ||
+ | |||
+ | It contains the following options: | ||
+ | |||
+ | * **Enable SSO ** - In order to enable SSO the box must be checked. | ||
+ | * **Operator domain ** - Enter your company' | ||
+ | * **Disable login and password access ** - If you check this checkbox, you will only be able to log in using Microsoft SSO credentials, | ||
+ | * **Provider ** - Choose Microsoft as a provider. | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Once it is configured, Users will be able to **log in using the Microsoft account instead of Leon-generated login and password**, as per the screenshot on the right-hand side. | ||
- | {{: | + | -------- |
- | ---- | + | ---------------- |