Skip to main content

Managing Employees

After adding branches, employees can be added per branch. In the toolbar, you'll find a switch to toggle between branches.

Manual Addition​

The administrator can add employees one by one using the plus button in the toolbar.

Adding Employees via CSV File​

Employees can be uploaded via a CSV list. The list must have 5 columns for first name, infix, last name, email address, and function. The list should not contain column headers.

The email address column is important. If an employee is uploaded to multiple branches, the records will be merged based on the email address. An employee will then be linked to multiple branches.

Creating Employees via Domain Whitelisting​

Employees can also be automatically created by whitelisting domains. When an employee logs in with an email address belonging to a whitelisted domain, an account will be automatically created for them and linked to the correct branch. This saves time because the administrator does not have to create an account for each employee.

See Managing Domains for more information.

Editing an Employee​

The employee can be edited by clicking "Edit" under Actions.

The employee is linked to a primary branch and can be linked to multiple branches. The employee's primary branch must always be in the list of linked branches. Multiple branches can be selected. The employee can change their primary branch in their account. The available options will come from the list of branches.

For each employee, the "Is Instructor?" property can be set to "Yes" or "No". This determines the employee's access rights within the system. Only employees marked as instructors can select the 'Groups' menu item and manage instruction groups.

The login status of an employee can also be updated. The employee can be set to inactive.

Account Creation​

Accounts are automatically created after a successful first login attempt. During account creation, tokens are added to the server that determine the basic role. The default roles are:

  • Employee (yes/no): set to "yes" if the email address matches an email address on the employee list.
  • Branch Admin (yes/no): initially usually set to "no".
  • Environment Admin (yes/no): initially usually set to "no".
  • Super Admin (yes/no): initially usually set to "no".

These tokens are later linked to Permissions. Permissions are set by the administrator (e.g., Environment Admin or Super Admin). This defines the rights assigned to each role.

For employees, there is an option to change the account type from "Federated" (e.g., Microsoft/Google login) to "Email/password". This option is only available when editing an employee record and if the employee does not yet have an active account.

If this option is selected, an email/password account will be created for the employee to log in. However, this requires the login option to be available in the environment, and it is generally less recommended than federated login.

Removing an Employee​

When removing an employee, there are a few scenarios:

  • The employee has never logged in and therefore has no account
  • The employee has an account and is placed in multiple branches
  • The employee has an account and is placed in only 1 branch

Employee Has No Account​

If the employee has no account, the employee record will be deleted. Since there is no account and no data, nothing further needs to happen.

Employee Has an Account and Is Placed in Multiple Branches​

If the employee is removed from a branch, that branch will be removed from the linked branches, and the employee will disappear from the employee overview for that branch. However, the record and related account will remain. The employee is still active in one or more branches.

Employee Has an Account and Is Placed in Only 1 Branch​

If the employee is removed from the only branch where they are active, the employee record will be set to inactive. The account and all data will remain, but the employee can no longer log in. To permanently remove the employee, the account must be deleted.

Deleting an Account​

When deleting an account, the following steps are automatically taken:

  • Chats and chat messages are deleted
  • Files and related documents are deleted
  • The employee or user record is deleted
  • The account record is permanently deleted from Firebase

Retention Period for Employees​

Employees are automatically deleted after the retention period set in the environment. The default is in accordance with company policy and legal requirements (e.g., 8 years after termination of employment).