Functionality of the "Parameter to Use For Groups" Setting for the Okta BambooHR App
Last Updated:
Overview
The Parameter to Use For Groups setting in the Okta Integration Network (OIN) BambooHR integration allows administrators to select an employee field to simulate groups within Okta. During setup, this setting provides the options of Departments, Locations, or Divisions from a dropdown menu under the Integration tab. Okta creates one group for each distinct active value found in the selected field and assigns employees to the corresponding group based on their profile data.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- BambooHR Integration
- Provisioning
Solution
How does Okta utilize the Parameter to Use For Groups setting?
During BambooHR application setup, administrators access the Parameter to Use For Groups setting via the dropdown menu under the Provisioning > Integration tab. The dropdown menu provides the choices of Departments, Locations, and Divisions. BambooHR does not have a native groups feature, so this setting allows administrators to select one of these employee fields to simulate groups in Okta. The selected parameter dictates how Okta processes and assigns groups during an import: it creates groups for active values and places employees into matching groups.
- Okta creates one group per distinct active value in the chosen field. For example, if Departments is selected, Okta creates one group per department in BambooHR.
- Okta places each employee into the group that matches their specific value for that field.
- Okta converts only active BambooHR list values into groups. Okta skips inactive or deleted values.
The Setting Has Specific Limitations During and After Configuration
The configuration limitations restrict the setting to apply only to imports and require creating a new integration if modifications are necessary after the initial setup.
- The setting only affects imports, such as new user creation and profile updates. It does not affect pushing data back to BambooHR.
- Okta locks the setting once the application configuration is complete. Administrators cannot change the setting later via the User Interface (UI). Administrators must create a new integration to change the value.
