Does anyone know what the teamsConfig and slackConfig portions of the new Access Request approval endpoints are meant for? I don’t see anything in the API documentation? ( get-approvals-config | SailPoint Developer Community and put-approvals-config | SailPoint Developer Community do not mention those settings)
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.
Thank you Harish. That is what we’ve done thus far and my assumptions have been the same, but I would really like a SailPoint admin to chime in on any plans for this to see if it will provide any extended capabilities that we can look forward to. 
From what I can tell, teamsConfig and slackConfig appear to be placeholders/config sections for collaboration-based approval experiences, likely Microsoft Teams and Slack notifications or approval actions. They are showing up in the approval config schema, but they do not appear to be documented yet in the public get-approvals-config or put-approvals-config API docs.
Unless SailPoint confirms otherwise, I would treat them as internal/future-use fields