Features that control learner enrolment, enrolment management, and automated training sequences. Includes Pathways, documented separately.
Last updated 13/05/2026
Admins can manually enrol individual users or groups of users into topics and pathways directly from the People tab in the Admin area. A single user can be enrolled by opening their profile and selecting topics or pathways from their Topics or Pathways tab, using bulk actions to enrol, unenrol, set due dates, reset, retake, or mark as complete. Groups of users can be enrolled by filtering the People list to the desired subset, selecting all matching users, and using the Enrol in Knowledge bulk action. Admins can also start from the topic or pathway and enrol users from its Enrolments tab.
Gives admins direct, immediate control over who is enrolled in what training. Useful for one-off situations, exceptions, new starters, or targeted rollouts where automation is not appropriate. The ability to enrol entire filtered groups in a few clicks makes even large manual enrolments manageable without needing a CSV file.
Last updated 13/05/2026
Admins can upload a CSV file to create, update, or backdate enrolments in bulk. The CSV uses enrolment codes unique to each topic or pathway. Supported actions per row include: NEW (new enrolment), COMPLETED (mark as complete with optional backdated completion and certified dates), RESET (reset existing enrolment), RETAKE (create a retake enrolment), UNENROL (bulk unenrol), and UPDATE (update dates or apply skills to existing enrolments). Optional columns allow per-row due dates, completion dates, certified dates, and recertification inclusion or exclusion. A maximum of 1,500 records can be uploaded per import.
The primary tool for large-scale onboarding, data migrations, and historical record uploads. Allows organisations moving from another LMS to backdate completion records so that compliance history is preserved in Tribal Habits. Also useful for annual bulk enrolments or when enrolling an entire workforce into a new compliance pathway at once.
Last updated 13/05/2026
Each topic and pathway has a default internal auto-enrol link, accessible from its Access tab. When an existing logged-in user clicks the link, they are automatically enrolled in that topic or pathway. Additional links can be created per topic (not pathways), each with an optional reference label and notes. Links can be temporarily deactivated or permanently deleted. Clicking a link when already enrolled or completed does not reset the enrolment. Links only work for users who already exist in the portal, or for new users provisioned automatically via SSO.
Enables enrolment to be triggered from anywhere outside the platform — emails, intranet pages, SharePoint, Teams, PDFs, or performance review portals. Ideal for pushing training to specific groups without requiring admin intervention for each enrolment. Particularly useful for induction workflows where a new starter welcome email contains a direct link to enrol in their first topic.
Last updated 13/05/2026
Admins can create catalogue rules that make topics or pathways visible to specific users in their training catalogue, based on user attributes such as type (staff/client/prospect), custom fields, groups, or other profile data. Users matching the rule see the topic or pathway in their Catalogue tab and can click to enrol themselves. The catalogue button can be set to ‘Enrol’ (free) or ‘Buy’ (for paid access scenarios). A ‘Run Rule’ option immediately enrols all currently matching users. Topics do not appear in any catalogue by default — a rule must be created first. Rules can be deleted at any time but cannot be edited — they must be recreated if changes are needed.
Allows organisations to maintain a self-service training menu tailored to different user groups without manual admin enrolment. Staff can enrol in elective professional development from their own dashboard. Different catalogues can be created for different roles, locations, or user types — for example, managers see leadership content, while frontline staff see operational topics. Removes the need for admins to manually process individual enrolment requests.
Last updated 13/05/2026
Automated enrolment rules check every two hours and enrol any users who match the rule criteria and are not already enrolled. Rules are built using the same People filter options as catalogue rules — filtering by user type, custom fields, groups, job title, location, date fields (such as created date or last login), and more. Once enabled on a topic or pathway, the rule runs automatically without any admin action. Automated rules only create new enrolments — they do not trigger retakes or resets. Only one rule can run at a time per portal to prevent duplicate enrolments from overlapping rules.
The primary mechanism for ensuring new starters are automatically enrolled in induction or compliance training without any manual admin steps. Once configured, the rule runs indefinitely — every new employee added to the portal with matching attributes is enrolled automatically within two hours. Eliminates a common failure point in compliance management where new staff fall through the cracks because someone forgot to manually enrol them.
Last updated 13/05/2026
When enabled on a topic or pathway, team leaders (managers who are users in the portal) can enrol their direct reports into that training from their Team page on the learner homepage. Admins enable manager enrolments per topic or pathway via the Access tab. Team leaders see a list of their team members and can enrol or unenrol them individually or in bulk. Manager enrolment permissions are scoped to the topics and pathways where the feature has been explicitly enabled — team leaders cannot enrol their team in all training by default.
Distributes enrolment responsibility to line managers without giving them admin access to the portal. Useful in organisations with many managers or multiple sites where centralised admin enrolment creates a bottleneck. Managers take ownership of their team’s training completion, which typically improves follow-through and accountability.
Last updated 13/05/2026
Due dates can be set on any topic or pathway via the Settings tab in the Timing panel. Options are: no due date, a fixed number of days from enrolment, a fixed number of days from a specific date, or a fixed calendar date applied to all enrolments. Due dates are visible to learners on their training dashboard and to admins in reporting. Due date settings only apply to enrolments created after the setting is configured — existing enrolments must be updated separately via bulk action on the Enrolments tab. Admins can update due dates for existing enrolments in bulk. Due dates are required for reminder notifications to trigger.
Creates visible accountability for training completion. Learners see their due date on their dashboard, which drives timely action. Due dates are a prerequisite for reminder and overdue notifications, which are the primary mechanism for chasing incomplete training. Reporting filters by due date status make it straightforward to identify who is overdue at any point in time.
Last updated 13/05/2026
Next Enrolment: When enabled on a topic or pathway, completing that training automatically triggers a new enrolment into a specified follow-on topic or pathway. This daisy-chains training so that learners are progressively enrolled in subsequent modules without admin intervention. Next Certification: Works in conjunction with a Certified Date. When a learner’s certification is approaching expiry (based on a configured lead time), they are automatically enrolled in either the same topic as a retake or migrated to a different specified topic or pathway. This allows organisations to move cohorts from one annual compliance pathway to the next, or from a full induction topic to a shorter annual refresher.
Eliminates the manual work of managing sequential or recurring training enrolments at scale. A new starter can be enrolled in a single induction topic, then automatically progress through a series of follow-on modules without any admin involvement. For compliance, next certification ensures that no learner falls off the recertification cycle — the system handles re-enrolment automatically when certification is approaching expiry.
Last updated 13/05/2026
Admins can manage individual enrolments through a learner’s profile (Topics or Pathways tab) or via the Enrolments tab of a topic or pathway. Available bulk actions include: Unenrol, Reset Enrolment (clears progress and restarts), Retake Knowledge (creates a new enrolment alongside the completed record), Set to Completed (manually mark complete with optional backdated date), Change Due Date, Remove Due Date, Change Completed Date, Change Certified Date, Prevent Recertification, and Allow Recertification. Admins can also add a note to any individual enrolment record, which is visible in the learner’s training history and in admin reporting. Learners can optionally be given the ability to unenrol themselves from elective training.
Provides admins with the full range of tools needed to handle exceptions, corrections, and edge cases in training management. A learner who completed training offline can have their record manually set to complete. An employee returning from leave can have their due date adjusted. A learner who needs to redo training due to a process change can be reset without losing their previous completion record. Notes on enrolment records support audit trails for compliance purposes.
| Cookie | Duration | Description |
|---|---|---|
| __cf_bm | 1 hour | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
| __hssc | 1 hour | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
| __hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
| __stripe_mid | 1 year | Stripe sets this cookie to process payments. |
| __stripe_sid | 1 hour | Stripe sets this cookie to process payments. |
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie records the user consent for the cookies in the "Advertisement" category. |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| CookieLawInfoConsent | 1 year | CookieYes sets this cookie to record the default button state of the corresponding category and the status of CCPA. It works only in coordination with the primary cookie. |
| elementor | never | The website's WordPress theme uses this cookie. It allows the website owner to implement or change the website's content in real-time. |
| JSESSIONID | session | New Relic uses this cookie to store a session identifier so that New Relic can monitor session counts for an application. |
| rc::a | never | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| rc::c | session | This cookie is set by the Google recaptcha service to identify bots to protect the website against malicious spam attacks. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| __hstc | 6 months | Hubspot set this main cookie for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
| _ga | 1 year 1 month 4 days | Google Analytics sets this cookie to calculate visitor, session and campaign data and track site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
| _ga_* | 1 year 1 month 4 days | Google Analytics sets this cookie to store and count page views. |
| hubspotutk | 6 months | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
| sbjs_current | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_current_add | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_first | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_first_add | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_migrations | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_session | 1 hour | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| sbjs_udata | session | Sourcebuster sets this cookie to identify the source of a visit and stores user action information in cookies. This analytical and behavioural cookie is used to enhance the visitor experience on the website. |
| Cookie | Duration | Description |
|---|---|---|
| _cfuvid | session | Description is currently not available. |
| blgj5lst | 5 days | Description is currently not available. |
| m | 2 years | No description available. |
| oxetqk28 | 5 days | Description is currently not available. |
| x4mk8hq1 | 5 days | Description is currently not available. |