We would like to request an enhancement to the Fivetran Okta connector to support Okta Linked Objects, specifically managerObject.

Current behavior

The current Okta connector syncs custom attributes returned in the user profile object from the Okta Users API into the USER_CUSTOM_PROFILE table. However, managerObject is not a standard profile attribute. It is an Okta Linked Object and must be retrieved separately through the User Linked Objects endpoint.

At this time, the connector does not appear to expose Linked Object definitions or user-to-user Linked Object relationships in the destination schema. As a result, managerObject is not being synced into USER_CUSTOM_PROFILE or any other destination table.

Requested enhancement

Please add support in the Okta connector for syncing Okta Linked Objects, including user-to-user Linked Object relationships such as managerObject.

An acceptable solution could include one or more of the following:

• Sync managerObject directly into an existing destination table when appropriate
• Add a dedicated table for Linked Object definitions
• Add a dedicated relationship table for user-to-user Linked Object mappings
• Document how Linked Object data is represented so downstream consumers can use it reliably

Why this matters

managerObject is needed downstream for validation, reconciliation, and reporting use cases that depend on accurate manager-to-agent relationships.

Without Linked Object support, customers using Okta as a source for organizational hierarchy and manager relationships cannot fully represent that data in their warehouse through the Fivetran Okta connector.

Documentation gap

Fivetran documentation indicates support for custom profile fields in USER_CUSTOM_PROFILE, but it does not clearly call out Linked Objects as an unsupported limitation. Even if feature delivery takes time, explicit documentation of this limitation would help set correct expectations for customers.

Requested outcome

We are requesting that Fivetran:

• consider native support for Okta Linked Objects in the Okta connector
• prioritize support for managerObject as a common and useful relationship field
• clarify connector documentation to distinguish standard custom profile attributes from Linked Object relationships

Short version for portal submission

Please enhance the Fivetran Okta connector to support Okta Linked Objects, including managerObject. Today the connector syncs custom profile attributes from the Okta Users API into USER_CUSTOM_PROFILE, but managerObject is a Linked Object that must be retrieved through the User Linked Objects endpoint and is not currently synced into any destination table. We need this data for downstream validation, reconciliation, and reporting. If native support is not yet available, please also update the connector documentation to clearly state that Linked Object relationships are not currently supported.