When adding new users to the platform, you can manage alignment with the company's release schedule.
This option can be configured via a checkbox available in the company's "Options" section and is reserved for users with an MSP role or higher.
- If the checkbox is checked: users are aligned with the release schedule according to the logic described below.
-
If the checkbox is not checked: users start from the first content.
-
New users will start from the first content of the path, which will follow the release schedule set for the company.
-
If the day the user is added does not coincide with a release date, no content will be available until the next scheduled release date.
-
This method ensures that new users follow the training path from the beginning, but it results in misalignment with users who are already active.
-
🧩 User Alignment on Platform – Key Rules
User alignment on the platform is activated only with license assignment, not with path association.
🔁 Alignment Mechanism
- The user aligns with the releases of a specific path only if, at the time of license assignment, the path is already associated with the company.
- Alignment takes into account the last release of the path (e.g., module 10 released → the user aligns with module 10).
- If a path has been fully released (even just for testing) to a user and then the user is DELETED, users created afterward align and still see the entire path.
✅ Alignment Examples
-
Scenario A: I have a path already associated with the company → I create a new user → I assign the license
✅ The user aligns with the last module released of that path.
-
Scenario B: A path has been fully released for a user (even just for testing) → the user is deleted (but not the path) → I create a new user → I assign the license
✅ The user aligns and finds the entire path available. -
Scenario C: I have a path released up to module 10 for some users→ I remove the path's association with the company →reassociate the path with the company→ I create a new user and assign the license
✅ Alignment occurs correctly (the path is indeed present when the license is assigned)
❌ Non-Alignment Examples
- I have a path released up to module 10 → the path is deleted (no longer associated with the company) → I create a new user → I assign the license → then I reassociate the path →
❌ Alignment will not occur, as the path was not present at the time of license assignment.