Create an employee ready for scheduling
The employee record groups information used to propose a person for work. Creating it does not automatically assign work.
Before you start
You need employee creation permission. Prepare identity, contact details, operational status and known skills. Search archived profiles too to avoid duplicates.
In the web version shown here, open Paramètres → Main-d’œuvre, then the Employés tab and Ajouter un employé. Review prefilled values rather than treating them as confirmed information.
Steps
- In employee management, search for the person before starting creation.
- Enter required fields and verified contact information.
- Set the appropriate status and add genuinely acquired skills.
- Save and reopen the record. Check active status, constraints and availability when used by your planning mode.
Actual French screenshot from the staging test environment, October 17, 2026. Your organization’s permissions and deployed version may produce a different view.
After creation, check the client preferences in the existing planning settings when your permissions allow it. Finish each changed favourite or exclusion with Update, or discard its pending edit with Cancel, then save the employee record. For example, changing the second client’s weekend checkbox must preserve the first client’s note and any historical reference. Reopen the profile to verify the result; this action does not change employment details, rates or assignments.
Verified on staging on October 18, 2026 (version 1.1.0). While editing an existing employee, Cancel asks whether to keep or discard your changes. Continue editing or Escape keeps the unsaved values; Tab and Shift+Tab stay between the two confirmation actions. Only Discard changes exits without saving. For example, Alex can change a fictional city, continue editing, then reopen Cancel before deciding. The profile, employment details and rates remain unchanged until an authorized save.
Verified on staging on October 19, 2026 (version 1.1.0). In the workforce directory, when the pager displays a total, it appears beside the page controls so that the help launcher does not cover it. For example, a fictional list of 46 employees has two pages at 30 employees per page; searching for one person changes the filtered total without changing employee status. On a small screen, the pager adapts and may hide this text.
Example and expected result
Fictional example: Alex has skill A. Record A before proposing Alex for work requiring it. Adding a skill only to obtain a match would distort planning.
If something goes wrong
For blocked creation, review validation and subscription capacity. For a missing candidate, check active status, skills, filters, absences and availability mode. Do not create a second profile to bypass a refusal.
When viewing an employee record, changing the language also updates the Back button. The open record and its return destination are preserved.
If the workforce directory cannot be loaded, an error remains visible with a Refresh action. A failed read does not mean there are no employees: the directory, totals and QuickBooks panel are hidden until loading succeeds. For example, if Alex receives a temporary refusal, restore the existing access or service and select Refresh; do not create duplicate employees to replace an unavailable list. A persistent refusal must be resolved with the administrator and does not grant additional access.