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

Slack documentation states:

"To add Multi-Channel Guests, workspace admins or owners should invite them via the workspace menu, and if necessary, route the requests through an approval process."

Adding them as full members (B) would grant excessive access. DMing Org Owners (D) is inefficient and informal. @mentioning (C) is not the standard request process.

(Reference: Slack Administration Study Guide - Managing Guest Accounts on Enterprise Grid)

===========

—

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)

Slack’s best practices for promoting open communication are:

"Keep everything in public channels for transparency and collaboration. Set public channel message retention to 'Keep Everything' and restrict DM retention to minimize private, siloed communication."

Also:

"Allow everyone to create channels to lower barriers to collaboration and prevent bottlenecks."

Restricting channel creation (Option C) would hinder users and reinforce the DM reliance problem.

(Reference: Slack Administration Study Guide - Messaging and Retention Policies)

===========

—