Moving sales channels into the Global workspace and making default channels private would:

Create confusion and friction in adoption.

Reduce transparency and cross-functional collaboration.

Slack documentation highlights:

"Workspaces should be structured to align naturally with how teams operate. Making core channels private may limit discoverability and collaboration, which contradicts Slack’s goals for connection and transparency."

Options B, C, and D promote transparency and collaboration, which is the intended use of Slack across cross-functional teams.

(Reference: Slack Administration Study Guide - Change Management and Slack Adoption Strategies)

===========

—

The best practice in Slack for securely collaborating with external partners is:

"Use Single-Channel Guests for external users when collaboration is limited to specific channels. Admins should control guest approvals, ideally via a private approval workflow, and set expiry dates for guest accounts to ensure access is revoked after projects end."

Multi-Channel Guests (Option B) provide broader access than necessary, and manually inviting guests (Option C) does not scale well. Asking companies to upgrade (Option D) is unrealistic for scalable collaboration.

(Reference: Slack Administration Study Guide - Guest Management and External Collaboration)

===========

—

Slack domain claiming is:

"Only available on Enterprise Grid, allowing an organization to reserve its domain and prevent users from creating independent Slack workspaces with corporate emails."

Pro plan (A) cannot support domain claiming. EKM (B) secures encryption keys, unrelated to domain claiming. 2FA (D) enhances authentication but doesn’t block workspace creation.

(Reference: Slack Administration Study Guide - Domain Management on Enterprise Grid)

===========

—

Slack best practices recommend:

"For external users who need access to multiple channels but not the entire workspace, a Multi-Channel Guest account is the ideal solution."

Full member access (D) is inappropriate for external users. Slack Connect DMs (B) would not provide full channel collaboration. Single-Channel Guest (C) would limit the contractor unnecessarily.

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

===========

—

Slack’s Workflow Builder is designed to:

"Allow non-developers to automate routine tasks without writing code, support integrations with apps and services for enhanced workflows, and provide templates that users can customize."

While developers can use Workflow Builder, it is primarily aimed at non-technical users; developers usually prefer building custom apps or using Slack APIs.

(Reference: Slack Administration Study Guide - Workflow Builder Overview)

===========

—

Slack warns that:

"Having too many workspaces can create challenges with context switching, where users need to frequently switch between workspaces to find information, reducing efficiency. It also impacts scalability as the organization grows."

While admin and user management complexity (C) can exist, context-switching (D) is the most relevant and critical issue in multi-workspace designs like the one proposed.

(Reference: Slack Administration Study Guide - Enterprise Grid Design Best Practices)

===========

—

Slack recommends using an org-wide channel for announcements:

"An org-wide channel ensures that important updates reach every member across all workspaces. Bookmarking learning materials in the channel also provides members with easy access to ongoing resources and updates."

Options B and C place too much burden on members to seek out information. D is reactive (waiting for questions) rather than proactive enablement.

(Reference: Slack Administration Study Guide - Managing Change and Member Enablement)

===========

—

Slack recommends for sensitive or confidential projects:

"An 'Invite Only' workspace allows Org Admins or Workspace Owners to control membership, ensuring sensitive topics remain private until disclosure is appropriate."

Hidden (C) conceals the workspace name, but Invite Only (D) is the correct choice for manually controlling access during sensitive phases.

(Reference: Slack Administration Study Guide - Workspace Access Management)

Slack recommends using public channels for community-building and location-specific discussions:

"Public channels allow easy discoverability and participation by members who might also be interested, even if they aren't part of the initial group."

DMs (A, C) are not scalable or discoverable. Slack Connect (B) is for external collaboration, not internal teams.

(Reference: Slack Administration Study Guide - Best Practices for Organizing Community Channels)

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 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 SCIM API documentation states:

"SCIM provisioning can be used to sync user attributes, like department, title, and location, from an Identity Provider to Slack profiles."

Analytics API (A) and Custom Profile API (C) focus on reporting or manual updates, not syncing at scale. Manual field creation (D) does not automate the syncing.

(Reference: Slack Administration Study Guide - SCIM Attribute Syncing)

===========

—

In Enterprise Grid, to manage who can invite guests:

"Org Admins can configure organization-wide policies that set permissions for inviting external users, including granting specific non-admin users the ability to invite guests."

This is handled under Organization Policies, not through workspace-specific settings or ownership transfer.

(Reference: Slack Administration Study Guide - User Management and Org Policies)

===========

—

Slack API best practices specify:

"The channels.rename method within the Slack API allows admins to programmatically rename channels, making bulk updates efficient and standardized."

Manually managing through Channel Manager roles (B) or joining channels (D) is slow and error-prone. Keyword notifications (A) don’t rename channels.

(Reference: Slack Administration Study Guide - Managing Channels and Using APIs)

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)

===========

—

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 the Slack Enterprise Grid documentation:

"Org Owners and Org Admins can use the Discovery API to export messages and files sent by their organization in Slack Connect channels. Messages and files sent by external partners must be requested from the respective organizations."

Because Slack Connect involves multiple organizations, each organization retains ownership of its own data. Thus, you can only export your company's messages/files via the Discovery API; partners must export their own data.

(Reference: Slack Administration Study Guide - Security and Compliance - Discovery API and Slack Connect)

===========

—

With Slack's data residency, the following data types are stored in the selected region:

"Messages, files, snippets, posts, and member profiles."

Data used for analytics and some metadata may still be processed globally, but the primary user-generated content is kept within the specified region.

(Reference: Slack Administration Study Guide - Data Residency Overview)

===========

—

Slack's official administration documentation confirms that when integrating Slack with an external IdP like Google Workspace, the correct method is to set up SAML-based SSO (Single Sign-On).

"You can configure SAML-based SSO with Slack to manage access via your IdP. When transitioning from username/password to SSO, you'll need to send out binding emails to link existing Slack accounts with the IdP profiles."

Google Workspace supports SAML 2.0 standard integration with Slack, and the binding process ensures existing users' Slack accounts are properly connected to their new IdP credentials.

Options A and C are incorrect because Slack natively supports Google Workspace SAML without needing a custom SAML setup, and option B incorrectly suggests setting up a new workspace, which is unnecessary.

(Reference: Slack Administration Study Guide - Integrations and Authentication Management)

===========

—

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 for Enterprise Grid states:

"Org Owners and Org Admins can enable workspace creation requests via Org Settings, making the process efficient and standardized."

Posting requirements (B) is not a controlled or actionable system. DM requests (C) are informal and untrackable. Workflows (D) are helpful, but Slack has built-in support for workspace creation requests through Org Settings, which is more efficient.

(Reference: Slack Administration Study Guide - Managing Workspace Creation on Enterprise Grid)

===========

—

When users are deprovisioned via SCIM or IdP integration:

"Their accounts are deactivated, they are signed out from all sessions, and their accounts are removed from channels, but their messages and files remain intact in Slack unless a separate data retention policy dictates otherwise."

Slack retains historical content unless specifically configured for deletion.

(Reference: Slack Administration Study Guide - Deactivation and Deprovisioning via SCIM)

===========

—

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)

===========

—

Slack recommends for security auditing:

"The Audit Logs API can capture file download activities, including which user downloaded a specific file."

Discovery APIs (A) help with content search/export, not action tracking. Audit Logs API is for actions like downloads (B). Option C (export public channel data) and D (workspace data export) won't show specific download activities.

(Reference: Slack Administration Study Guide - Using the Audit Logs API)

===========

—

When designing an Enterprise Grid deployment, Slack recommends a thoughtful, structured approach.

According to Slack’s Enterprise Grid best practices:

"Develop a clear business case outlining why a strategic design is important, addressing key goals such as minimizing noise and maximizing collaboration.

Define success criteria and key design principles early, and work with your Slack account team to evaluate different workspace design models."

The idea is to ensure leadership understands the need for a strategic design and that the team has clear success metrics. C and E describe possible implementation strategies but jump ahead without a strategic foundation. D (surveying users) is helpful later but not the first step.

(Reference: Slack Administration Study Guide - Enterprise Grid Workspace Design Best Practices)

===========

—

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)

In Enterprise Grid, an org-wide channel is intended for communications relevant to all members across all workspaces. Slack documentation states:

"Org-wide channels are automatically shared with every workspace in your organization and should be used for information that applies to everyone, such as company-wide announcements."

Since a cross-functional project would involve specific participants and not the entire organization, a multi-workspace channel is a more appropriate and flexible solution.

(Reference: Slack Administration Study Guide - Enterprise Grid Channels and Communication Best Practices)

===========

—

Slack recommends:

"Use Huddles for lightweight, real-time, informal discussions to troubleshoot quickly without needing to schedule formal meetings."

This directly helps service agents collaborate live without adding overhead.

Options A and C are good for async work but do not replace real-time collaboration. Threads (D) are useful but are slower than live discussions.

(Reference: Slack Administration Study Guide - Using Huddles for Efficient Team Collaboration)

Slack recommends that:

"Workspace Admins should be knowledgeable about Slack best practices, support user adoption, enforce etiquette, and provide feedback on policies."

The candidate in A already demonstrates leadership in Slack usage, policy understanding, and peer support. B focuses on technical integration (more developer-like), C focuses on Slack Connect specifics (not general admin readiness), and D describes a user who needs support rather than offering it.

(Reference: Slack Administration Study Guide - Choosing Workspace Admins)

===========

—

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)

===========

—

Slack recommends using user groups to efficiently notify a specific subset of people:

"User groups allow you to mention multiple people at once by tagging the group’s handle, ensuring the right people are notified without disturbing unrelated members."

Using @channel or @here would notify all 50 members unnecessarily. Sending 10 direct messages individually is inefficient and error-prone.

(Reference: Slack Administration Study Guide - User Groups and Targeted Notifications)

===========

In Slack, Admin roles (Workspace Admin or Org Admin) are required to approve invitations and manage user roles, including inviting guests.

According to Slack’s documentation:

"Admins can invite members and guests, approve new invitations, and manage permissions at the workspace or org level. A Multi-Channel Guest is someone who can access multiple channels that an admin selects."

Since the marketing vendor needs access to "various channels," the correct guest type would be a Multi-Channel Guest, not Single-Channel Guest. Therefore, Tracy should use the Admin role to invite and approve new members and assign the marketing vendor as a Multi-Channel Guest.

(Reference: Slack Administration Study Guide - User Management Roles and Guest Access)

===========

—

According to Slack Enterprise Grid administration best practices:

"Org-wide channels allow messages to be broadcast to every member of an Enterprise Grid organization, across all current and future workspaces."

Creating an org-wide channel ensures that the training communications are visible everywhere, without needing coordination with individual Workspace Admins or external partners. Multi-workspace channels (B) are helpful but only span selected workspaces, not automatic inclusion in all future workspaces.

(Reference: Slack Administration Study Guide - Org-wide Channels)

===========

—

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)

===========

—

Workflow Builder allows launching workflows based on specific triggers. Slack officially states:

"Supported triggers include when a new member joins a channel and at a scheduled date and time."

Keyword usage (A) is not currently a native trigger without a custom app. New channel creation (B) is not a trigger. New member joining a workspace (D) by itself is not a trigger unless tied to joining a specific channel.

(Reference: Slack Administration Study Guide - Workflow Builder Triggers)

===========

—

Mandatory Two Factor Authentication (2FA) adds an extra layer of security to member accounts. When enabled, Slack requires that:

"Members must enter a verification code from an authentication app or text message after submitting their password to successfully sign in."

This means each time members sign into Slack, they must provide both their password and a second factor, typically a code generated by a mobile authentication app or received via SMS. This prevents unauthorized access even if a password is compromised.

The other options (A, B, C) describe different security measures but do not accurately represent the behavior of 2FA as configured in Slack.

(Reference: Slack Administration Study Guide - Security and Compliance - Two Factor Authentication)

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)

===========

—

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)

===========

—

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's External People Management dashboard allows Org Admins to:

"View all external users, the channels they are connected to, and remove them, especially if they have 'Can post & invite' permissions."

Admins cannot view all Connect invitations (C) or directly approve/deny Connect requests (D) from this dashboard — that happens in different settings.

(Reference: Slack Administration Study Guide - Managing External Collaborators)

===========

—

When SSO is made mandatory in Slack:

"Members will receive an email containing a link to connect their Slack account with their identity provider account. They must complete the connection by following the link and authenticating via the SSO provider."

Members are not immediately logged out or forced to reauthenticate before they complete the linking process (which rules out B and C). The correct and supported flow involves an email-based linking process.

(Reference: Slack Administration Study Guide - Managing Single Sign-On (SSO) Settings)

===========

—

When you claim relevant domains for your Enterprise Grid organization:

"Any user with an email address matching a claimed domain who attempts to create a new workspace will be directed to join the Enterprise Grid organization, ensuring that all workspaces fall under centralized policies for security, compliance, and retention."

This process prevents rogue or unmanaged workspaces and ensures consistent governance.

(Reference: Slack Administration Study Guide - Claiming Domains and Managing Grid Compliance)

===========

—

Since Preethi needs access to multiple channels but only for a limited time:

"A Multi-channel Guest is the best choice when someone needs access to more than one channel but does not need full member access across the workspace. You can also set an expiration date for their access."

Single-channel Guest would be too limiting, and full Member access would provide more access than necessary, posing a security risk.

(Reference: Slack Administration Study Guide - Managing Guest Access)

===========

—

Using Workflow Builder is the best way to:

"Automatically send onboarding messages when users join a channel, providing them with key guidelines like how to use Slack appropriately without requiring manual monitoring."

This automates onboarding at scale and reduces Nicole's workload as hiring ramps up.

(Reference: Slack Administration Study Guide - Onboarding Best Practices and Workflow Automation)

===========

—

Slack's official documentation states:

"SCIM provisioning is ideal for automatically managing large user populations, assigning them to workspaces, and ensuring immediate onboarding or deactivation through integration with your Identity Provider (IdP)."

It is perfect for multiple workspaces (A) and large, one-time onboarding events like a company-wide Slack launch (E).

Options B and C relate to Slack Connect and app behavior, not SCIM. Option D refers to "Just-in-Time" provisioning, not SCIM.

(Reference: Slack Administration Study Guide - SCIM Provisioning)

===========

—

Slack ensures that all customer data:

"Is encrypted at rest and in transit, using industry-standard encryption protocols."

Workspace Admins cannot access direct messages unless data exports or eDiscovery tools are properly configured and approved. Slack data is stored on Slack-managed servers (AWS infrastructure) and not on customers’ own servers by default. Access is not restricted solely to the corporate network unless additional security tools (like Slack Enterprise Mobility Management or VPNs) are enforced.

(Reference: Slack Administration Study Guide - Security and Compliance Overview)

===========

—

Slack recommends using self-paced resources and workflows for onboarding:

"Workflow Builder allows admins to create automated onboarding workflows that include links to Help Center articles, internal documentation, and recorded webinars, enabling new users to learn at their own pace."

Hackathons (B) and Slack 101 live trainings (D) are great, but they are scheduled sessions, not self-paced. Custom bots (C) add overhead and are not necessary for scalable self-service onboarding.

(Reference: Slack Administration Study Guide - Onboarding Strategies Using Workflow Builder)

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)

To automatically deactivate users who leave a company, Slack relies on SCIM (System for Cross-domain Identity Management) provisioning. SCIM allows an Identity Provider (IdP) to manage user accounts, including provisioning, deprovisioning, and updating user profiles directly from the IdP.

According to the official Slack documentation for user provisioning:

"When SCIM provisioning is enabled, changes made in your Identity Provider — such as deactivating a user — will be reflected in Slack automatically. Deprovisioning ensures that when someone leaves the company, their Slack account is also deactivated without manual intervention."

None of the other options (A, B, or C) are requirements for automatic deactivation. SCIM deprovisioning is the only supported and correct method for automated account deactivation through IdP integrations.

(Reference: Slack Administration Study Guide - User Management and SCIM Provisioning)

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)

===========

—

Slack’s app management guidelines advise:

"Before approving an app, you should review its compliance with your organization's data security policies and understand which external services and APIs the app communicates with."

Availability in the Slack App Directory (A) doesn’t guarantee security compliance. Whether the app connects with your HR system (D) is helpful but not a core initial security evaluation criterion.

(Reference: Slack Administration Study Guide - App Review and Security Considerations)

===========

—

Slack’s Enterprise Key Management (EKM) provides organizations with the ability to control and revoke access to data encryption keys, ensuring protection for sensitive information such as PII (personally identifiable information).

Slack documentation states:

"Slack EKM allows customers to manage and control access to their data in Slack by using their own encryption keys. It is ideal for industries that frequently handle sensitive data such as PII, PHI, and financial information."

Using unsecured mobile devices (option A) is a mobile device management issue, Azure usage (option C) is not a sole qualifier, and being in the public sector (option D) may suggest high-security needs but does not directly relate to EKM eligibility.

(Reference: Slack Administration Study Guide - Security and Compliance - Enterprise Key Management)

===========

—

For ongoing external data archiving and retrieval:

"Slack recommends using a third-party eDiscovery or archiving app to pull Slack data and store it securely in a separate data warehouse or compliant system."

Corporate exports (Option A) are manual and not continuous, retention policies (Option B) keep data inside Slack, and DLP (Option C) manages risk but not long-term archiving externally.

(Reference: Slack Administration Study Guide - Data Governance and eDiscovery Options)

Slack best practices for managing high-volume help channels recommend:

"Creating regional help channels following a clear, consistent naming convention, such as #help-workplace-region, so requests are easier to route and monitor."

This method ensures that requests are properly triaged without confusing users and keeps the support experience scalable.

(Reference: Slack Administration Study Guide - Best Practices for Managing High-Volume Support Channels)

Slack recommends for external collaborations:

"Slack Connect channels are the preferred method to collaborate securely with external organizations instead of bringing external users into your workspace as full members or guests."

Inviting 15 external users as Multi-Channel Guests (C) is less scalable and harder to manage. Adding them to the IdP (B) is unnecessary and risky for external contractors. Creating a new workspace (D) would complicate governance.

(Reference: Slack Administration Study Guide - Slack Connect Collaboration Best Practices)

According to Slack App Management best practices:

"Turn on app approval to restrict app installation to only those apps that have been reviewed and approved."

"Notifications about app requests should be sent to a specific Slack channel where app managers can easily review and approve or deny requests."

Options A and C suggest manual, ad-hoc processes, which are not scalable or officially recommended for structured app management. Option B incorrectly describes app restrictions not tied to a formal approval process.

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

Slack documentation advises:

"Group DMs cannot be expanded to include or replace members after they are created. If you need to manage membership over time, you should create a private channel."

Converting the group DM into a private channel allows Chandler to maintain privacy, manage membership changes, and centralize discussions securely.

(Reference: Slack Administration Study Guide - Private Channels vs. Group DMs)

===========

—

Slack best practices recommend:

"Pre-approving key apps ensures fast adoption while restricting high-risk apps maintains security compliance."

Admin API (B) is more technical and unnecessary at launch. Individual requests (C) create friction. Pre-approving apps and restricting non-common ones (D) isn't optimal unless based on risk evaluation.

(Reference: Slack Administration Study Guide - App Management Best Practices)

===========

—

Slack advises:

"Using native app approval workflows within the Manage Apps dashboard ensures that app installation requests are logged, require a rationale, and can be tracked by App Managers in a centralized approval workflow."

Workflow Builder (D) is useful but unnecessary when Slack's built-in app approval is available. Options A and C are partial solutions but miss the audit trail and rationale requirement.

(Reference: Slack Administration Study Guide - Managing App Approvals and App Governance)