Salesforce Salesforce-Slack-Administrator Exam With Confidence Using Practice Dumps

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 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)

===========

—

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)