Login and Password: Unterschied zwischen den Versionen

Aus Faces Dokumentation
Wechseln zu: Navigation, Suche
Zeile 66: Zeile 66:
  
 
[[File:PW gesperrt.PNG|250px|PW_gesperrt]]
 
[[File:PW gesperrt.PNG|250px|PW_gesperrt]]
 +
  
  
Zeile 73: Zeile 74:
  
 
*Faces username and password are only displayed by creating new travellers (mandatory)  
 
*Faces username and password are only displayed by creating new travellers (mandatory)  
*To prevent that the AeTM password stored in Faces is not different from that in AeTM, the [[CRS_Configuration#Community_Settings|Community Settings]] should be adjusted with 'Enable password expiration', so that AeTM passwords never expire. If this is not configured, the user will eventually be forced to set a new password directly in AeTM, while in Faces then still the old password is stored.  
+
*To make sure that the AeTM password stored in Faces is the same as that in AeTM, the [[CRS_Configuration#Community_Settings|Community Settings]] should be adjusted with 'Enable password expiration', so that AeTM passwords never expires. If this is not configured, the user will eventually be forced to set a new password directly in AeTM, whereas in Faces the old password will still be saved.  
  
 
*The AeTM-Integration '''never''' verifies if a password in Faces  is expired or not and it does not realise either if it were.
 
*The AeTM-Integration '''never''' verifies if a password in Faces  is expired or not and it does not realise either if it were.

Version vom 8. Januar 2019, 14:09 Uhr

General

To join Umbrella Faces Suite, the following data are required:

  • User name (Benutzername)
  • Password (Passwort)
  • Agency-Key (Agentur)

Those login data are allocated to a Traveller, Arranger , Approver and Administrator.

Procedures / Processes

Credentials

Credentials are sent via email. Credentials can be sent by an arranger, approver, administrator or a profile manager and a supporter.

Credentials email


Login

The URL https://faces.umbrellanet.ch/faces/login can be accessed with the obtained credentials.

Faces_Loginpage

 

Data protection / Privat policy

After the initial login, the data protection provisions have to be accepted.

private policyt

 

Password

A password must contain at least 8 characters, with a minimum of one digit, one capital letter and one special character.

Password renewal

The password must be renewed every 90 days.

New password request

If a user forgets their password, a new password can be requested.

Passwort_vergessen1

new_password

Change temporary password

The first time you log in, the temporary password from the login email hast to be changed. The new password must conform to the password guideline requirements indicated above.

Change_Password

 

Password locked

After a wrong password is entered three times, the user access is blocked for 10 minutes. A new password must be requested if the user wants to access Faces immediately.

PW_gesperrt


Password including AeTM-Integration

When working with the AeTM-Integration (see AeTM Integration), the Faces credentials are not relevant. Therefore, the login works slightly different:

  • Faces username and password are only displayed by creating new travellers (mandatory)
  • To make sure that the AeTM password stored in Faces is the same as that in AeTM, the Community Settings should be adjusted with 'Enable password expiration', so that AeTM passwords never expires. If this is not configured, the user will eventually be forced to set a new password directly in AeTM, whereas in Faces the old password will still be saved.
  • The AeTM-Integration never verifies if a password in Faces  is expired or not and it does not realise either if it were.

User rights

User level Own traveller profile Edit self Edit other travellers Edit company Edit travel agency
Traveller Yes X      
Approver, Arranger Yes X Only assigned travellers    
Company admin No X All travellers in same company Only some of the data/ fields  
Agency admin No X All travellers yes Only some of the data/ fields