Salesforce-Slack-Administrator Exam Dumps : Salesforce Certified Slack Administrator (Slack-Admn-201)

According to Slack’s official documentation on IdP group management:

"Mapping IdP groups to Slack allows automatic provisioning and deprovisioning of users to workspaces and user groups. Members added to an IdP group are automatically added to associated Slack user groups and workspaces."

This dramatically reduces manual effort and ensures correct workspace and channel access is kept current.

Slack Connect (C) is external collaboration and not managed directly via IdP groups. D and E are unrelated to IdP functionality.

(Reference: Slack Administration Study Guide - Identity Provider Group Mapping)

===========

—

The scopes mentioned allow the following:

channels:write — allows the app to create, archive, or modify public channels.

chat:write:user — allows the app to send messages on behalf of a user.

According to Slack’s API documentation:

"channels:write grants permission to manage public channels, while chat:write:user grants permission to send messages as a user rather than as the app."

Uploading files would require the files:write scope, and accessing group DMs would require groups:read or groups:history, neither of which are mentioned.

(Reference: Slack Administration Study Guide - App Scopes and Permissions)

To automatically manage user deactivation:

"If your Identity Provider supports SCIM provisioning, and it is correctly configured with Slack, user deactivation in the IdP will trigger automatic deactivation of the user's Slack account."

SCIM ensures seamless deprovisioning. Just-in-Time deactivations (D) are not a Slack feature, and changing the email manually (A) is not secure or scalable.

(Reference: Slack Administration Study Guide - User Deprovisioning with SCIM)