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

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)

===========

—

Slack's best practices for private, sensitive, or surprise planning activities:

"Create a private channel when planning events that should remain confidential to a specific group of people."

This protects the surprise. Public channels (A) expose planning. Group DMs (B) are limited (maximum of 8 people) and informal. A thread in a public space (C) is risky for surprises.

(Reference: Slack Administration Study Guide - Managing Sensitive Conversations)

===========

—

According to Slack’s role management documentation:

"Roles Admins have the ability to assign and manage system roles for members across the Slack organization."

Compliance Admins (A) manage legal holds and data exports. Channels Admins (C) manage channel structures. Users Admins (D) manage member profiles and deactivations. Only Roles Admins manage assignment of admin permissions.

(Reference: Slack Administration Study Guide - System Roles Overview)

Slack’s recommendation for increasing adoption and productivity states:

"Connect existing tools that users are already familiar with to Slack, so they immediately see value without needing extensive new training."

This approach enhances workflows and familiarity, without adding a heavy burden of learning or complex processes.

(Reference: Slack Administration Study Guide - Accelerating Slack Productivity with Integrations)

===========

—

Slack Enterprise Grid provides an Org-level Members analytics section where you can view and export detailed information about all users, including guest accounts.

"Org Admins and Org Owners can export member lists from the Org analytics dashboard, including guest account details like type (single-channel or multi-channel), status, and associated workspaces."

Gathering from each workspace (A) is inefficient and manual. Exporting from the Export Data tab (D) relates to message and file exports, not member data. Opening a ticket with Slack (B) is unnecessary for this standard administrative task.

(Reference: Slack Administration Study Guide - Org Analytics and Member Exports)

===========

—

According to Slack official documentation:

"Workspace analytics allows Workspace Owners and Admins to view data about members, channels, and activity within the workspace, including daily and weekly active users."

The Org Analytics Dashboard (A) is only available in Enterprise Grid. The Analytics Members Dashboard (C) focuses on member-specific stats, and Message Activity Analytics (D) focuses specifically on message data, not user activity overall.

(Reference: Slack Administration Study Guide - Workspace Analytics Overview)

===========

—

Slack's best practice for maintaining security is:

"Deploy the Slack desktop app to users and allow automatic updates to ensure that users are always running the latest, most secure version."

Disabling updates (Option B) would increase security risks. Browser usage alone (Option A) is insufficient for a full Slack experience, and Option D relies too much on user compliance instead of ensuring deployment at scale.

(Reference: Slack Administration Study Guide - Deployment and Security Best Practices)

===========

—

The Business+ plan is the appropriate recommendation here because:

It includes full message history access (unlike the Free plan, which limits access to recent messages only).

It supports SAML-based SSO integrations like Okta, allowing for secure user provisioning and onboarding.

It provides Enterprise Mobility Management (EMM) integrations for managing and securing Slack access on company-owned mobile devices.

Official Slack documentation confirms:

"Slack Business+ includes enhanced administration and security controls, including SAML-based SSO, user provisioning with supported IdPs, and mobile device management (MDM) support via EMM."

Enterprise Grid (option D) would be overkill for a small growing business unless they required multi-workspace organization and complex compliance features.

(Reference: Slack Administration Study Guide - Plans and Feature Comparison)

===========

According to Slack Enterprise Grid documentation:

"To allow users to integrate external tools into workflows, admins must enable steps from apps and allow workflows to include webhook triggers."

Also,

"Enabling Workflow Builder and allowing users to create workflows (except Guests) ensures flexibility."

While A (App Managers) grants permission to approve apps, it is not needed for creating workflows. Channel emails (C) are unrelated. Workflow creation policy (E) is important too but the critical steps for app usage and webhook integration are B and D.

(Reference: Slack Administration Study Guide - Workflow Builder with External Integrations)

—

In Enterprise Grid, you can:

"Delegate app management by selecting specific members or user groups who are allowed to review, approve, and manage app requests."

This provides a controlled and efficient way to expand app review capabilities without elevating users to Workspace Owner or Admin roles.

(Reference: Slack Administration Study Guide - App Management and Delegated App Approvals)

===========

—