Vitre system is an open platform with a full API, allowing actions to be performed automatically, manually via the UI, or by uploading a file.
Synchronization Steps
Organizational Units Synchronization – automatic or manual from source systems (e.g., SAP, Priority).
Employee List Synchronization – including team assignment. All employees can be synchronized without limitation.
User Definition – not every employee is a user. Users can be defined manually or through synchronization.
Permission Assignment – regular user or admin.
Entity Assignment – manually link employees/teams to locations, equipment, training sessions, and certifications.
Employee Synchronization
Can be synchronized via API (single or bulk).
When creating, it is mandatory to provide: Employee Name + External ID.
Contact details (phone/email) are not required if the employee is not a user.
Each employee is assigned to one team (default: ROOT).
Additional identifiers (ID number, passport, employee number, etc.) can be defined – values must be unique.
User Synchronization
In organizations where the employee management system = the user management system → an employee can be defined as a user during creation.
In organizations where the systems are separate → the employee must first be created, and only then defined as a user.
If no identity management system exists → users can be created manually via the UI or from a file.
User requirements:
Phone number or email is mandatory (depending on the authentication type: OTP = phone, SSO = email, Username/Password = email).
Define User = Yes.
Username (default = email, but can be changed).
The username is different from the External ID (which is only a technical identifier).
SSO Authentication
Allows login with organizational username and password.
Does not replace the standard login option (username/password).
When creating a new user, an email with initial login details is sent, even if SSO is used.
Password reset is always possible – it will only affect Vitre, not the organization’s systems.
Organizational and Non-Organizational Users
The system supports hybrid management: internal employees alongside external users such as suppliers, contractors, and guests.
The admin must ensure usernames are unique to avoid overwriting existing user data.
End of Employment
An end-of-employment date can be defined (past, present, or future).
Once the date is reached:
The employee can no longer log into the system.
The employee will not appear in screens or forms.
Removing the end date will restore the employee’s access.