Using Employee Status to Drive Okta Workflows



In the world of workforce Identity and Access Management, a person’s employee status is critical. Whether they are full-time, part-time, a contractor – these designations of employment are important considerations when dealing with lifecycle management.



BambooHR is an HR SaaS platform that is becoming increasingly popular with small and medium sized businesses. Within BambooHR, Employment Status is one of those critically important attributes that is displayed by default along with other important information like name and job title.



As of this writing (March 2022), Employment Status is not an attribute that is exposed in the same way as other attributes and cannot simply be retrieved directly. Based on our research, the values for BambooHR’s “employmentHistoryStatus” attribute appear to be derived from another table instead of being stored for each user.


A TechJutsu client approached us with a requirement to integrate BambooHR with their Okta implementation. The employment status attribute was critical to the client’s needs. BambooHR would be used as the source of user profile data, and some users would need access to different resources (applications, network shares, etc.) depending on whether they were a full-time employee or a contractor.



The first step was easy – connecting Okta to BambooHR was a snap with the use of Okta’s pre-built BambooHR app integration. The next part was a little more of a challenge!


Fortunately, much like many SaaS offerings these days, BambooHR has an API. We logged into their BambooHR domain and set up a “non-employee user” service account with read-only access, then set the account up with an API key that could be used to securely connect.



Are you looking to implement the same sort of thing? Similar results can be achieved with a variety of HRIS systems and IAM platforms. Click the red Book Now button at the top of the page to learn more.