Salesforce Salesforce-Slack-Administrator - Salesforce Certified Slack Administrator Exam

Slack officially supports configuring Default Channels for workspaces:

"Default channels are channels that new members will automatically join when they first sign in to Slack."

Creating workflows (A) or pinning channels (B) are helpful for awareness but don't enforce automatic joining. Training managers manually (C) is inefficient and prone to errors.

(Reference: Slack Administration Study Guide - Managing Default Channels)

===========

—

Slack best practices state:

"SAML-based SSO and SCIM provisioning (through IdP groups) are available on the Business+ plan. This enables automation of user management and enhances login security."

Google Workspace SSO (A) without SAML lacks the full control needed. 2FA (B) is a good practice but doesn't automate provisioning. Enterprise Grid (C) would be overkill and costly for a small organization.

(Reference: Slack Administration Study Guide - Identity and Access Management)

===========

—

Slack’s Enterprise Grid security recommendations state:

"Org Admins can remotely sign a member out of all sessions (desktop, mobile, web) via the admin dashboard to immediately prevent further access without deactivating the user."

Asking the user (A) is unreliable because they lost the device. Deactivation (B) is extreme if the device may be recovered. Workspace-level action (D) is insufficient for org-wide risk.

(Reference: Slack Administration Study Guide - Managing Lost or Compromised Devices)

===========

—

Slack clearly states:

"If Slack Connect DMs are disabled for your organization, users cannot initiate or receive direct messages from users in external organizations, even if they share Slack Connect channels."

Thus, users cannot DM external users if Connect DMs are disabled, regardless of their presence in shared channels. Options A, B, and D incorrectly suggest DMs would still function.

(Reference: Slack Administration Study Guide - Slack Connect Security Settings)

===========

—

Slack documentation states:

"When public file sharing is enabled, file sharing settings apply to files uploaded by any organization participating in a Slack Connect channel."

DLP monitoring (A) is separate and applies differently. File upload permissions (C) can be restricted through Slack Connect settings. Any user, not just admins (D), can create external file links if allowed.

(Reference: Slack Administration Study Guide - Managing Public File Sharing in Slack)

===========

—

Slack's Workflow Builder allows users to create workflows without writing code, and Admins have visibility over workflows to maintain governance.

According to Slack documentation:

"Workspace Owners and Admins can view and manage all published workflows in their workspace." "For Enterprise Grid organizations, Org Owners and Org Admins can see workflows across all workspaces."

Option A is false — creating a workflow is a quick process requiring fewer than five clicks. Option C is inaccurate because regular members can also view workflows they have access to via Workflow Builder, not just Owners or Admins.

(Reference: Slack Administration Study Guide - Workflow Builder and Admin Controls)

===========

—

To balance security, culture building, and minimize admin burden, the best practice is to allow members to upload emojis with clear guidelines.

Slack documentation recommends:

"Allowing users to upload custom emoji fosters creativity and engagement. Setting clear policies and communicating acceptable use ensures that the benefits are realized while minimizing the risk."

Restricting uploads entirely or centralizing all requests would hinder the cultural goal of promoting collaboration.

(Reference: Slack Administration Study Guide - Change Management and Culture Building with Slack)

Slack's documentation on EMM policies specifies:

"Enterprise Mobility Management (EMM) requirements apply only to full members of your Slack organization. Guest accounts (Single-Channel or Multi-Channel Guests) are not required to use the Slack for EMM app."

Thus, guests are exempt from EMM enforcement. Options B and C incorrectly state guests can be controlled via EMM. D is unrelated.

(Reference: Slack Administration Study Guide - EMM and Guest Account Behavior)

Slack recommends:

"When using SCIM provisioning, admins can automate the deactivation of user accounts through the SCIM API, ensuring synchronization with identity provider (IdP) data."

Deactivating manually through the Org Settings (A) is possible but less efficient and scalable. Contacting Slack via /feedback (B) is not appropriate for standard admin tasks. Deactivation is not limited to Primary Org Owners only (D).

(Reference: Slack Administration Study Guide - User Lifecycle Management with SCIM)

===========

—

Slack provides an option to restrict the use of @channel, @here, and @everyone mentions to Workspace Owners and Admins only.

Slack’s guidance states:

"To prevent disruption, you can limit the ability to use @channel, @here, and @everyone mentions to only Workspace Owners and Admins."

This prevents misuse in large public channels while still preserving structured communications.

(Reference: Slack Administration Study Guide - Notification Settings and Messaging Restrictions)