What does the managed integration with TASS do?
This integration populates Tribal Habits with new and updated users from TASS on a scheduled basis, including:
New users are created in Tribal Habits
Updated users are updated in Tribal Habits
User data is populated (e.g. campus, employment status, position title, faculty/department)
Manager data is populated (including email), where reliable manager data is available in TASS
Departed staff are automatically deactivated in Tribal Habits
THIS FEATURE REQUIRES A BUSINESS 50 PLAN OR LARGER.
This integration is not available on smaller plans (such as Lite) or legacy plans (older monthly plans). Contact our team if you would like access to this integration but it is not activated in your portal.
What are the benefits of this managed integration with TASS?
What is a 'managed integration'? This integration is managed by Tribal Habits. This means we build and manage the integration on your behalf. The integration can be customised for data mapping, user inclusion/exclusion, notifications and more, allowing us to create a bespoke integration to suit your school's requirements.
Reduced administrative workload
This integration reduces the workload for your Tribal Habits administrators by automating user creation. New staff will be automatically populated in Tribal Habits from TASS as soon as they're added. Departing staff are automatically deactivated, so nobody has to remember to remove access manually.
Data consistency
The integration eliminates data inconsistency. Users are updated automatically from TASS, ensuring your Tribal Habits data matches your TASS data. This allows your school to use TASS as a single source of truth for staff data.
Improved reporting
With more (and more accurate) staff data - including campus, employment type, and faculty/department - your Tribal Habits reporting and administration is also improved. This makes it easy to assign training and run reports by campus, faculty, or staff type.
What's required to set up the integration?
The integration is managed by Tribal Habits. Our team will set up the integration and manage it on your behalf. Error messaging for a failed user sync can be enabled and sent to a specified email address at your school, so your TASS or Tribal Habits administrators are notified if anything needs attention.
IMPORTANT
The integration requires API access in your TASS instance. Your school's TASS administrator will need to generate API credentials for us - our team will guide you through exactly what's needed and where to find it in TASS web during the set-up process.
What is the integration process?
Our integration with TASS is a ‘managed integration’. This means our Support team will create and run the integration on your organisation’s behalf. It also means that each integration can be slightly customised to suit your organisation. Here are the major steps and options as we set-up this integration.
1 - Kick-Off Call
We begin with a short call with your team to discuss your integration.
We determine the appropriate 'username' for your staff in Tribal Habits - typically their school email address.
We review which additional staff data you'd like synced into custom fields in Tribal Habits - such as campus, employment status, position title, and faculty or department.
We discuss any filtering you'd like on the user sync - for example, only syncing staff with a school email address, or excluding specific record types (such as placeholder or test accounts some schools keep in TASS for internal purposes).
We also discuss your initial user load, so all your existing active staff can be populated into Tribal Habits from day one.
2 - Integration Preparation
Our team then prepares the integration to your agreed specification, which typically takes a few days. During this time, your team can create any additional custom fields we've agreed on in Tribal Habits - our support team can assist with this.
3 - Set-up Call
We then organise a second call with your team for testing. We require one of your TASS administrators for a short session to confirm API access and run through the initial data load together.
Specifically, we will:
Confirm the API credentials and access required in TASS
Run the initial sync to populate your existing active staff into Tribal Habits
Review the results together and confirm the data mapping looks right
Test the ongoing scenarios (a new starter, an updated record, a departing staff member)
4 - Go Live
Once your integration is tested and ready, we activate it on your agreed schedule. We actively monitor your integration for the first few weeks to make sure everything is running smoothly, and to fine-tune anything as needed. Your integration is then all set!
FAQs
What staff data is typically synced from TASS?
We can customise the data synced from TASS to suit your school. Commonly synced fields include campus, employment status, position title, staff type, and faculty or department. If your school uses TASS's User Defined Areas to track other staff information, we can generally map these into Tribal Habits too.
Can we filter which staff are synced from TASS?
Yes. We don't have to sync everyone in TASS. Common filters include only syncing staff with a school email address, or excluding specific record types your school may use internally (for example, placeholder or test records). We'll work through the right filters for your school during the Kick-Off Call.
Can we sync manager or supervisor information?
We can, where your TASS data reliably reflects each staff member's actual manager. Some schools use TASS's supervisor field for payroll or leave-approval purposes rather than a direct reporting line - we'll check this with your team during set-up so manager-based features (like team reporting or escalations) are only enabled where the underlying data actually supports them.
How quickly does information sync from TASS?
User data syncs from TASS to Tribal Habits on a scheduled basis - typically several times a day on weekdays. We agree the exact schedule with your school based on how frequently your staff data changes and how quickly you need updates reflected.