The best way to manage noise while protecting sensitive information includes:

• Limiting posting permissions — According to Slack’s official guidance:

" You can restrict who can post to a channel by limiting posting permissions to specific people, ensuring that only authorized individuals can post while others can read. "

• Creating a private channel with a personal benefits workflow:

" Private channels are suitable for discussions requiring confidentiality. Workflows can route sensitive questions to HR without public visibility. "

Encouraging DMs (option C) helps, but it is not a structured or scalable solution for organizational processes. Archiving the channel (option D) would disrupt access to the historical benefits information and is unnecessary.

(Reference: Slack Administration Study Guide - Channel Management Best Practices and Workflows)

—

Slack best practices encourage public discussions to:

" Make answers discoverable to others who might have the same question later, reduce redundant inquiries, and model a culture of openness. "

By encouraging employees to post their questions in a public help channel, Jose reinforces using public channels and helps build a searchable knowledge base.

(Reference: Slack Administration Study Guide - Promoting Open Communication and Knowledge Sharing)

===========

—

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)

—

Slack advises:

" Turning on Mobile Session Duration policies allows admins to automatically log users out of Slack mobile apps after a set period, reducing risk if a device is lost or stolen. "

Requiring a passcode (B) is good mobile practice but not Slack-specific. A (manual sign-out) is unreliable. D (no app downloads) would block necessary communication entirely.

(Reference: Slack Administration Study Guide - Mobile Security Features)

Security-critical settings involve decisions that could expose the organization to risk through external access or the addition of third-party apps. Slack documentation specifies:

" App management and member invitation settings are critical security configurations. Restricting who can add apps (admin-approved apps) and who can invite new members ensures better control over external access and data exposure. "

Custom emoji (B) and channel creation (C) impact user experience but are not considered critical security matters.

(Reference: Slack Administration Study Guide - Enterprise Security Controls and Settings)

===========

—

Slack recommends for mobile session management:

" Setting a mobile session duration of around two weeks provides a good balance between security and usability, ensuring users aren ' t prompted to log in too frequently. "

Allowing users to set their own session length (A) would reduce security controls. Logging everyone out during any threat (B) is too disruptive for normal operations. Allowing infinite sessions (D) risks serious security exposure.

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

The most accurate approach is to use Slack’s analytics to compare direct message usage across different workspaces.

Slack documentation states:

" Workspace-level analytics allow Admins to view the percentage of messages sent via direct messages versus public or private channels. Comparing this across teams highlights differences in Slack usage patterns. "

Only option A directly provides a comparative analysis to see if HR’s behavior is different from the rest of the org.

(Reference: Slack Administration Study Guide - Workspace Analytics and Communication Patterns)

===========

—

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 Clips are recommended for asynchronous communication:

" Slack Clips allow users to record video, screen shares, and voice messages directly in Slack, which teammates can view at their convenience. "

Starting a Huddle (C) is synchronous and not asynchronous. Recording outside Slack (B) and importing is less efficient. Public channels limited to specific workspaces (D) won’t reach the entire org unless users join manually.

(Reference: Slack Administration Study Guide - Using Clips for Asynchronous Communication)

===========

—

Slack recommends converting public channels to private when:

" Sensitive or confidential information (e.g., financial results, M & A activity) begins to be discussed and needs to be restricted to a limited group. "

Quarterly earnings (D) are sensitive, non-public information, justifying the need for a private channel. Options A and B refer to comfort and tone but not confidentiality. Option C relates to relevance, not security.

(Reference: Slack Administration Study Guide - Channel Privacy and Confidential Conversations)

===========

—