This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
leon:general-setup [2023/05/19 17:51] rafal [Bases] |
leon:general-setup [2024/03/25 11:19] (current) rafal [Automatically mask PAX after given days] |
||
---|---|---|---|
Line 13: | Line 13: | ||
* **Mobile Notifications** - full section explained [[leon: | * **Mobile Notifications** - full section explained [[leon: | ||
* **Fuel** - full section explained [[leon: | * **Fuel** - full section explained [[leon: | ||
+ | * **Phonebook** - settings related to PAX | ||
* **Crew App** - settings that apply to the Crew mobile app | * **Crew App** - settings that apply to the Crew mobile app | ||
* **Security** - settings that apply to the user login settings | * **Security** - settings that apply to the user login settings | ||
Line 115: | Line 116: | ||
---------- | ---------- | ||
+ | ===== 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' ===== | ===== Tab 'Crew App' ===== | ||
Line 148: | Line 206: | ||
---------------- | ---------------- | ||
===== Tab ' | ===== Tab ' | ||
- | [{{ : | ||
In the ' | In the ' | ||
The additional security options are: | The additional security options are: | ||
+ | [{{ : | ||
* **Force two factor authentication for all users** - 'Two factor authentication' | * **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 | * **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. | ||
+ | |||
+ | -------- | ||
---------------- | ---------------- |