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

Moving sales channels into the Global workspace and making default channels private would:

Create confusion and friction in adoption.

Reduce transparency and cross-functional collaboration.

Slack documentation highlights:

"Workspaces should be structured to align naturally with how teams operate. Making core channels private may limit discoverability and collaboration, which contradicts Slack’s goals for connection and transparency."

Options B, C, and D promote transparency and collaboration, which is the intended use of Slack across cross-functional teams.

(Reference: Slack Administration Study Guide - Change Management and Slack Adoption Strategies)

===========

—

Slack's External People Management dashboard allows Org Admins to:

"View all external users, the channels they are connected to, and remove them, especially if they have 'Can post & invite' permissions."

Admins cannot view all Connect invitations (C) or directly approve/deny Connect requests (D) from this dashboard — that happens in different settings.

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

===========

—

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)

===========

—