I tried to dig into this & those fields look real, but the public endpoint docs don’t currently explain them.
There’s a related prod thread where a Jackson UnrecognizedPropertyException dumps the known properties on com.sailpoint.approval.ApprovalConfig, and both slackConfig and teamsConfig are on that list. So this doesn’t look like tenant-specific noise or a random leaked field. The schema is just ahead of what the public get-approvals-config / put-approvals-config docs currently describe.
Based on the field names and SailPoint’s documented chat approval features, these appear tied to the collaboration integrations: SailPoint for Slack, SailPoint Gov for Slack, and SailPoint for Microsoft Teams. Those integrations let users approve/deny access requests from Slack or Teams, so these config blocks are most likely related to that approval/chat behavior. I wouldn’t try to author them manually yet. I don’t see a public field-level contract for what belongs inside slackConfig or teamsConfig.
Safe approach for now: GET the approval config, change only the documented fields you need, and on PUT, preserve slackConfig and teamsConfig exactly as returned. I would not remove, null, or reshape them until SailPoint documents the schema or Support confirms the expected payload.