Okta fails to synchronize the manager attribute to Slack when the attribute format is incorrect or the manager profile does not exist in Slack. Specifying the managerId sub-attribute with a valid Slack ID, primary email, or username resolves this issue.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Integration Network (OIN)
• Slack
• System for Cross-domain Identity Management (SCIM) Provisioning
• Universal Directory

The manager attribute fails to synchronize with Slack due to an incorrect format. Additionally, the attribute fails to synchronize if the manager profile does not exist in Slack.

How is the manager attribute synchronized from Okta to Slack?

Configure the manager attribute mapping with the following requirements to ensure the attribute synchronizes successfully.

• Specify the managerId sub-attribute when providing the manager attribute.
• Use a valid Slack ID, primary email, or the userName attribute of the respective individual for the managerId sub-attribute value.
• Ensure the provided value aligns with an active user account that currently exists within the Slack platform.

NOTE: If attributes such as the manager attribute are blank in the Slack application assignment in Okta, Okta overwrites the attribute in the Slack profile as blank.
 

Related References

• Slack API Documentation

• Okta Does Not Support Partial Profile Push During Subsequent Profile Update Push from Okta to External Application