Litmos Community Team (Litmos Team) asked a question.
User Provisioning
Originally asked by a community member in the Litmos Community forum on 23 February 2026.
Hey everyone,
We're about to start scoping a revamp to how our user profiles are create/updated/deleted. Currently, we just have a basic SAML setup, which creates the user when they first log in, and updates each time they log in, but it doesn't capture all colleagues, so we fill the gaps through imports.
There are a couple of different avenues we can go down, so I'm keen to hear the experiences of others. How are you all handling your user profile set up? I'm particular keen to hear if anyone has the Workday integration in place, and if it works well as a solution.
Many thanks
Mal
Reply from a community member, 27 February 2026
Hi Mal,
We have a Workday API that does a full file nightly to update current employees and contingent workers, add new hires, and inactivate terminated workers.
The integration is actually three APIs total:
1) Worker information - the API works well and consistently
2) Team information - we (attempt) to mimic the sup org structure of Workday with teams. This API worked well at first, but it needs revamping to better capture org moves and when inherited orgs become un-inherited.
3) Team Assignments - adds workers to the teams and promotes people managers to team leads. Also does not work that well because it doesn't capture all of the nuanced transactions that occur in Workday BPs.
If I were to do it again, I would only do the Worker Information API (sorry not using the technical terminology here) because that's the only integration we've been able to do successfully. If you want to have Litmos teams mimic the Workday sup orgs, I would exercise caution with trying to get an API to meet this need.
--Beth
Reply from a community member, 2 March 2026
[quote data-userid="2375" data-postid="453"]
Hi Mal,
We have a Workday API that does a full file nightly to update current employees and contingent workers, add new hires, and inactivate terminated workers.
The integration is actually three APIs total:
1) Worker information - the API works well and consistently
2) Team information - we (attempt) to mimic the sup org structure of Workday with teams. This API worked well at first, but it needs revamping to better capture org moves and when inherited orgs become un-inherited.
3) Team Assignments - adds workers to the teams and promotes people managers to team leads. Also does not work that well because it doesn't capture all of the nuanced transactions that occur in Workday BPs.
If I were to do it again, I would only do the Worker Information API (sorry not using the technical terminology here) because that's the only integration we've been able to do successfully. If you want to have Litmos teams mimic the Workday sup orgs, I would exercise caution with trying to get an API to meet this need.
--Beth
[/quote]
This is brilliant Beth, thanks for the detailed response. It's interesting that the Team side of things doesn't quite work, with the nuances of our structure, I think we would be in a similar situation 🙂