Login and Password: Unterschied zwischen den Versionen

Aus Faces Dokumentation
Wechseln zu: Navigation, Suche
Zeile 30: Zeile 30:
  
 
[[File:Private policy.PNG|250px|private policyt]]
 
[[File:Private policy.PNG|250px|private policyt]]
 +
  
 
== Password ==
 
== Password ==
 +
 +
=== A password must contain at least 8 characters, with a minimum of one digit, one capital letter and one special character. ===
  
 
=== Password renewal ===
 
=== Password renewal ===
  
 
The password must be renewed every 90 days.
 
The password must be renewed every 90 days.
 
A password must contain at least 8 characters, with a minimum of one digit, one capital letter and one special character.
 
  
 
=== New password request ===
 
=== New password request ===
Zeile 49: Zeile 50:
 
=== Change temporary password ===
 
=== Change temporary password ===
  
The first time you log in, the temporary password from the login email must be changed.
+
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.
 
 
The password must contain at least 8 characters, with a minimum of one digit and one letter.
 
  
 
[[File:Change Password.PNG|250px|Change_Password]]
 
[[File:Change Password.PNG|250px|Change_Password]]
Zeile 68: Zeile 67:
 
*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 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.  
  
*The AeTM-Integration will '''never''' check an expired password in Faces.  
+
*The AeTM-Integration will '''never''' check an expired password in Faces.
  
 
== User rights ==
 
== User rights ==

Version vom 8. Januar 2019, 10:58 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.

Login Page


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 three times a wrong password is entered, the user access is blocked for 10 minutes. For instant access a new password will need to be requested.

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 prevent that the AeTM password stored in Faces is not different from that in AeTM, the 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.
  • The AeTM-Integration will never check an expired password in Faces.

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 travelers    
Company admin no X All travelers in same company some data  
Agency admin no X All travelers yes some data