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

Slack recommends for official, organization-wide communications:

"Create an org-wide channel (such as #announcements) where only admins and owners can post. This ensures important messages are visible to all and remain uncluttered by unrelated posts."

Option B and C involve redundancy and fragmentation. Using @channel in #general (D) risks spamming and frustrating members.

(Reference: Slack Administration Study Guide - Best Practices for Org-Wide Announcements)

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 Connect settings allow you to control who can initiate external communications:

"By adjusting the Slack Connect settings for DMs to allow only Org Admins and Org Owners to send and accept DM invitations, you reduce the risk of unauthorized or unapproved vendors initiating contact."

Setting up messaging guidelines (A) informs users but does not block action. Restricting to specific workspaces (C) does not prevent DM invites across the org. Disabling free team access (D) is not directly related to vetting vendors.

(Reference: Slack Administration Study Guide - Slack Connect and External Communications Policy)

===========

—