Skip to main content

Bob Manager’s email mapping for Okta provisioning integration

  • December 18, 2024
  • 2 replies
  • 131 views

When updating a manager's details in the Okta provisioning integration, it’s essential to map both the manager's email and the 'Reports to' field. Mapping only the email will not ensure that updates are processed correctly.

Why Mapping 'Reports to' is Crucial: The 'Reports to' field is a virtual field connected to the backend. Updates to virtual fields are not automatically captured. By mapping the 'Reports to' field, you ensure that:

  • Updates to the actual 'Reports to' field are linked to the virtual field.
  • The updated information is synced correctly with the Identity & Access Management  system.

What You Need to Do

  1. Map the Manager's Email: Include the manager's email in your mapping configuration.
  2. Map the 'Reports to' Field: Add this field to ensure synchronization of updates.

 

Here’s an example setup for how the mapping might look:
 

 

If you have any questions or run into issues, don’t hesitate to reach out. We’re here to support you!

2 replies

I don’t know if I have the ability to do this using this flow, but I need the ‘Reports to’ email from bob to feed into an integration with our travel vendor, Navan. This is done with a service user integration. Managers are approvers in that system and Navan prompts asking for the manager email but that isn’t a field on profiles today. Do I have to first add that as a field then find a way for it to auto-populate and feed into the API?


  • March 12, 2025

@Stevie Coleman You should be able to pull manager’s email via API. Please see example of payload when pulled employee details for the manager’s details: