Overview
In this step, you’ll review the IT requirements and security features for your portal.
Tribal Habits runs in your web browser and needs no installation or downloads, so this step is usually quick. You may want to involve your IT team.
This is step 1 in the implementation process. After this step, you'll move on to Step 2 - Admins and key contacts.
Warning: Single sign-on (SSO), custom domains and custom email domains are available on Business plans only. They’re not available on Lite plans.
How to complete this step
Review the IT requirements. Share What IT requirements does Tribal Habits have? with your IT team. It covers browser and device requirements, and the emails and domains to safelist.
Safelist emails and domains (if required). Ask your IT team to safelist the listed emails and domains, so that emails from your portal reach your users. Learn more about how email notifications are sent.
Set up a custom domain and custom email domain (optional). A custom domain lets learners access your portal from your own web address, such as training.yourorg.com. A custom email domain sends notification emails from your own email address, such as @yourorg.com. You can set up either or both. Your IT team will need to update your DNS records.
Set up SSO (optional). If your organisation uses SSO, follow How do I set up single sign-on (SSO) - SAML 2.0?. If SSO isn’t enabled in your portal, contact us through Admin Help to discuss activating it.
Review your security settings. Go to Admin → Account → Security to set up features such as MFA, session timeouts and admin monitoring. Learn more about the Security page.
Best practices
Set up custom domains before SSO and user invitations: If you plan to use a custom domain, set it up before SSO and before inviting users. Changing your domain later means setting up a new SSO profile and replacing any links you’ve already shared.
Set up SSO early: Set up SSO before you add or enrol any SSO users. This avoids login problems for your users later.
Supported platforms: We support the SAML 2.0 standard, including Microsoft Entra ID (formerly Azure AD), ADFS, Okta, OneLogin and Salesforce.
SSO and non-SSO users: You can have both SSO users (e.g. staff) and non-SSO users (e.g. contractors or customers) in the same portal. The LOGIN field sets which is which. Learn how to set up both user types.
Prevent SSO auto-provisioning: We recommend turning on Prevent auto-provision of new users via SSO login. This stops new users being created when their details don’t match your SSO environment.
SSO auto-redirect: If all or most of your users log in with SSO, consider turning on Enable auto-redirect for SSO login. Users will go straight to your SSO login page.
Safelisting: Most organisations don’t need to safelist anything. We recommend it if your organisation has strict email filtering or firewall rules.
Embedded third-party content: If your training includes content from other websites, such as YouTube videos, your network needs to allow those sites. If your network blocks YouTube, it will also be blocked in Tribal Habits.
Users outside Australia: Tribal Habits can be accessed from anywhere, but users in some locations may be asked to complete a short security check. If your users access the portal from a fixed IP address, such as an office network, we can add it to our approved list. Learn more about accessing Tribal Habits from outside Australia.
Deactivating inactive users: If you turn on Deactivate stale users, choose a long enough duration, such as 12 to 18 months. This setting also deactivates admins who haven’t logged in within that period.
Examples
Small organisation: This organisation has no SSO and no special firewall rules. Their admin reviews the IT requirements, confirms their browsers are supported and turns on Require MFA for administrators.
Medium organisation: This organisation’s IT team has strict email filtering. They safelist the listed emails and domains so that invitation emails and notifications reach staff.
Large organisation: This organisation uses Microsoft Entra ID. They set up a custom domain and custom email domain first, then set up SSO for their staff before uploading any users. They turn on Prevent auto-provision of new users via SSO login. Their contractors don’t have company accounts, so they’re set up as non-SSO users in the same portal.
Next step
Continue to Step 2 - Admins and key contacts.