Features supporting integration of Tribal Habits with external platforms via SSO, HRIS sync, API, Zapier, webhooks, LMS Link, and embeddable content.
Last updated 27/08/2026
Tribal Habits supports SAML 2.0 Single Sign-On, allowing users to access the portal via their organisation’s existing identity provider – such as Microsoft Azure AD/Entra, Okta, ADFS, or Salesforce. When SSO is enabled, users are redirected to the organisation’s SSO login page and, once authenticated, returned to Tribal Habits without needing a separate password. New users can be auto-provisioned in Tribal Habits on their first SSO login. A LOGIN field on each user profile controls whether they are Internal (SSO) or External (standard login) – enabling mixed environments where some users (e.g. contractors) bypass SSO. A control on the Security page allows admins to enable email alerts when an SSO user logs in using local Tribal Habits credentials rather than via SSO. Admins can also hide the local login fields on the portal’s login page behind a “show link,” reducing confusion for learners who should only use SSO – see Login Page Customisation.
Removes the need for staff to manage a separate Tribal Habits password – they use the same credentials as every other work application. Reduces IT support overhead from password resets and simplifies onboarding. For organisations with Azure AD or Okta already in use, SSO makes Tribal Habits feel like a native part of the work environment rather than a separate system. Combined with the option to hide local login fields, learners see a single clear login path with no risk of confusion over which method to use.
Last updated 13/05/2026
Tribal Habits offers managed integrations with a range of HRIS, payroll, employee engagement, and identity platforms. All managed integrations are built, configured, and maintained by the Tribal Habits team on the customer’s behalf. Typical sync capability includes: new users created in Tribal Habits when approved in the HRIS, user data updated (name, location, job title, manager) when changed, terminated users deactivated. Some integrations also support syncing training completions back to the HRIS. Integrations are customisable for field mapping, user inclusion/exclusion filters, and error notifications. We support over 20 popular HRIS, Payroll, CRM and Identity Management platforms. Managed integrations are available on our Business plan for a small add-on cost.
Eliminates the most time-consuming ongoing admin task for Tribal Habits administrators: manually creating, updating, and deactivating users as staff join, move, or leave. When the HRIS is the source of truth for user data, Tribal Habits stays automatically in sync — meaning managers are correctly assigned, custom fields are populated, and terminated staff are deactivated without any manual intervention. This also dramatically improves data quality in reporting.
Last updated 13/05/2026
Tribal Habits provides a RESTful Public API allowing organisations to build custom integrations between Tribal Habits and other platforms. The API supports operations across users (create, update, deactivate), enrolments (create, update, query), and topics (query). Full developer documentation is available online.
Gives technically capable organisations the flexibility to build bespoke integrations not covered by managed integrations — for example, connecting Tribal Habits to a proprietary internal HR system, a custom-built onboarding tool, or a third-party platform without a managed integration. Organisations with development resources can automate any user or enrolment workflow that can be expressed via API calls.
Last updated 13/05/2026
Tribal Habits has a dedicated Zapier integration, accessible via a separate Zapier API key (distinct from the Public API key). The Zapier integration allows organisations to connect Tribal Habits to thousands of third-party platforms via no-code automation workflows (Zaps). Typical use cases include triggering enrolments or user creation in Tribal Habits when events occur in another platform — for example, enrolling a new user when a record is created in a CRM, or notifying a Slack channel when a learner completes a topic. The Zapier API key is generated and managed in Admin > Account > Integrations.
Extends Tribal Habits integration capability to virtually any platform that has a Zapier connector — without requiring development resources. HR teams and operations managers can set up automated workflows between Tribal Habits and tools like HubSpot, Slack, Google Sheets, Microsoft Teams, or Salesforce without writing any code. Particularly useful for smaller organisations without a dedicated IT team who still need automated workflows.
Last updated 13/05/2026
Tribal Habits supports outbound webhooks that automatically send data payloads to an external HTTPS URL when specific events occur in the platform. Three webhook event types are available: Enrolment Created (triggered on any new topic or pathway enrolment), Enrolment Completed (triggered when any topic or pathway is completed), and Enrolment Deleted (triggered when an enrolment is unenrolled, including reset enrolments). Webhooks are created and managed by admins. Each webhook has a URL, optional notes, an enable/disable toggle, and a log view showing all past occurrences including date, target URL, response code, and payload.
Enables real-time push of training events to external systems without polling the API. When a learner completes a topic, the completion data is immediately pushed to a nominated endpoint — for example, to update a record in a CRM, trigger a downstream workflow, or write to a data warehouse. Unlike scheduled API polling, webhooks are event-driven and instantaneous, making them the right tool for integrations that require immediate response to training activity.
Last updated 13/05/2026
LMS Link allows organisations to make a Tribal Habits topic available inside a third-party LMS via a SCORM 1.2 compatible file. The admin generates an LMS Link for a topic in Tribal Habits and downloads a small ZIP file. This ZIP file is a SCORM wrapper — not an export of the topic content itself. It is uploaded to the external LMS just like a standard SCORM package. When a learner launches the topic from the external LMS, the wrapper connects back to Tribal Habits, where the actual content is hosted and all learner data is recorded. Completion data is passed back to the external LMS. Each LMS Link has optional expiry date, usage limit optional notes. Usage via each LMS Link is reportable. Multiple LMS Links can be created per topic allowing one topic to be shared into multiple external LMSes. This feature is not included in any plan by default and requires a separate add-on.
Critical distinction: LMS Link is not a SCORM export. It is a SCORM wrapper. The value is that organisations can make their Tribal Habits-built content available in another LMS (e.g. a customer’s LMS, a larger enterprise LMS, or a government portal) without losing any of the rich Tribal Habits reporting or content control. You can update your topic in Tribal Habits and it is automatically updated for all users without having to issue new SCORM files. You can also manage licensing, but implementing usage or date limits, while retaining full control of your content. Particularly relevant for training providers selling content to clients, or large organisations where a division uses Tribal Habits but the enterprise uses another LMS.
Last updated 13/05/2026
Two content elements in Tribal Habits enable integration of external content directly into topics. The PDF element allows creators to upload a PDF file which is embedded and viewable inline within a topic — learners can read the document without leaving the platform. The Embed element allows creators to paste a URL to embed external web content directly into a topic — supporting YouTube videos, Google Maps, H5P interactive content, and any other embeddable URL. Both elements are available in the standard content editor alongside all other topic elements.
Allows organisations to incorporate existing documents, videos, and interactive content from external sources into Tribal Habits topics without needing to recreate or re-upload that content. A team can embed a YouTube training video, a Google Maps location for an event, or an H5P interactive activity alongside their own Tribal Habits-built content in a single unified topic experience. PDF upload is particularly useful for attaching policy documents, procedures, or reference materials that learners need to read as part of training.
Last updated 27/08/2026
Tribal Habits supports OAuth2 authentication as a custom-configured alternative to SAML SSO. Standard OAuth2 integrations are available with partner platforms such as EmployeeConnect and Prosper. Where a customer runs their own OAuth2 provider, Tribal Habits can also integrate directly with that platform on request. Once configured, users authenticate via a “Login with [Partner]” button, are redirected to the OAuth2 provider, and are returned to Tribal Habits once authenticated – without a separate Tribal Habits password. New users are auto-provisioned in Tribal Habits on first login, the same as SSO. Unlike SSO, there is no Internal/External LOGIN field or mixed authentication model – all users configured for OAuth2 login are treated as internal and authenticate via the OAuth2 provider only.
Gives organisations that already run an OAuth2-based platform – whether a partner system like EmployeeConnect or Prosper, or their own proprietary platform – a way to authenticate into Tribal Habits without managing separate credentials. Particularly useful for organisations whose staff or members already log in to a core platform daily, letting Tribal Habits sit behind that existing login rather than requiring a new one. Custom OAuth2 integration with a customer’s own platform extends this beyond our named partners, giving technically capable organisations a path to single authentication even without SAML/SSO in place.
| 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. |