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

In Enterprise Grid, if auto-provisioning is enabled via an IdP group, when a member is added to that group, they are automatically provisioned to the specified workspace. According to Slack’s official Enterprise Grid documentation:

"When a member is added to an IdP group that’s mapped to a workspace, they will be automatically provisioned (added) to the workspace, unless the workspace is set as hidden."

Hidden workspaces require an invitation or manual addition and are excluded from automatic group provisioning. Therefore, unless the workspace is hidden, members will automatically join it without needing to take any manual action.

(Reference: Slack Administration Study Guide - Enterprise Grid Configuration and IdP Group Management)

Slack recommends:

"Admins can remove external members from all Slack Connect channels in bulk via the External People Management dashboard."

Disconnecting all shared connections (A) is extreme and affects the entire organization. Muting (C) only hides messages for individuals. /leave (D) only removes users themselves, not the offender.

(Reference: Slack Administration Study Guide - Managing External Users)

===========

—

According to Slack’s Enterprise Grid admin settings:

"Org Admins and Org Owners can lock the guest invitation setting at the organization level from the Org Admin dashboard to prevent Workspace Admins from controlling it independently."

Option A only applies to workspace-level settings (not sufficient). Option B is unnecessary because Org Admins also have permission. Option C is just communication without any enforcement.

(Reference: Slack Administration Study Guide - Managing Guest Access in Enterprise Grid)

===========

—