Salesforce Salesforce-Slack-Administrator Salesforce Certified Slack Administrator Exam Exam Practice Test

Slack’s mobile security features on Enterprise Grid allow:

"Blocking the ability to copy messages and download files on unmanaged devices to protect sensitive data."

IP restrictions (Option B) and VPN enforcement (Option D) are broader network security strategies but not specific mobile device security features. Blocking workspace access completely is not the goal; securing content on devices is.

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

===========

—

Slack’s documentation for the Business+ plan specifies:

"Workspace Owners can use the standard Import/Export Data tool to export data from public channels without needing to contact Slack or request additional permissions."

Discovery APIs (D) are only available on the Enterprise Grid plan. A and B would only apply for more extensive exports (such as private channels, which would require special approval, typically for compliance or legal reasons).

(Reference: Slack Administration Study Guide - Exporting Data from Slack)

According to Slack’s best practices:

"Claim your domains as soon as possible. This process is not retroactive — workspaces created before claiming domains will continue to exist independently unless manually migrated."

Thus, prompt domain claiming ensures better control and prevents users from unintentionally creating ungoverned workspaces.

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

===========

—

Slack defines "By Request" access as:

"A workspace or channel is visible to all users, but users must request to join, and Admins or Owners must approve each request."

This model fits Jorge’s need for visibility plus control over membership approval.

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

In the Slack Business+ plan, to meet compliance requirements where deleted files must remain discoverable, you must set file retention to:

"Keep all files, including deleted files."

This ensures that even after a user deletes a file, it remains accessible for auditing and compliance purposes. Simply keeping files (B) does not guarantee deleted files are retained. Options involving "for a set number of days" (C, E) would risk data loss after the timeframe expires, and D (all file versions) focuses on version history, not deletion recovery.

(Reference: Slack Administration Study Guide - File Retention and Compliance Settings)

===========

—

According to Slack’s official documentation regarding Legal Holds:

"The Legal Holds feature is only available on the Enterprise Grid plan. Legal holds allow Workspace Owners and Org Owners to preserve messages and files of specific users for compliance and legal purposes."

Legal Holds are a critical feature for enterprises with compliance requirements, and they are not available on the Free, Pro, or Business+ plans.

(Reference: Slack Administration Study Guide - Security, Compliance, and Legal Holds)

===========

—

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 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 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 guidance on change management recommends:

"A vision statement defines the purpose of Slack in the organization’s broader workflow. It helps end users align on why Slack is being used and how it supports their day-to-day work."

It focuses on strategic understanding, not tactical elements like channel lists (B), permissions (C), or feature updates (D).

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

===========

—

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)

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)

===========

—

In Slack, only the Primary Owner has the ability to deactivate other Workspace Owners.

Slack documentation states:

"Only the Primary Owner can deactivate or transfer ownership of another Workspace Owner's account."

Thus, Cortez, despite being a Workspace Owner himself, cannot deactivate Camdin’s account.

(Reference: Slack Administration Study Guide - Workspace Roles and Account Deactivation)

===========

—

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

Slack Pro plan documentation states:

"Slack’s Pro plan supports Google Workspace (formerly G Suite) authentication for single sign-on without needing a third-party SAML provider."

Azure SAML, Auth0, and Okta are typically used with the Business+ and Enterprise Grid plans where SAML SSO is needed.

(Reference: Slack Administration Study Guide - Authentication and SSO by Plan)

Slack recommends user groups for onboarding because:

"User groups allow admins to easily manage membership in multiple channels by adding the user group to those channels, ensuring no member is missed and simplifying onboarding processes."

Options A and D misrepresent how access is managed (user groups do not automatically restrict channel access), and C is incorrect because mentions depend on group settings and channel memberships.

(Reference: Slack Administration Study Guide - Managing User Groups for Onboarding)

===========

—

Two critical elements in Change Management are understanding user needs and promoting solutions that fit their workflows.

• Running a campaign promoting Slack's mobile app addresses their need for mobility. Slack documentation notes:

"Promoting the Slack mobile app to teams that are highly mobile ensures they remain connected to important communications and workflows."

• Surveying the Sales team will help prioritize relevant integrations and workflows based on real-world challenges they face:

"Understanding end-user pain points is crucial for designing Slack solutions that users find genuinely helpful."

Simply installing the Salesforce app without understanding their needs may not be effective, and using threats (option B) is contrary to Slack’s recommended adoption strategies.

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

===========

—

On Slack Enterprise Grid:

"Org Owners are responsible for organization-wide security and compliance settings, including configuring and managing Single Sign-On (SSO) for the entire organization."

Workspace Owners manage workspace-level settings such as retention policies (A) or app approvals (D), but they cannot manage enterprise-wide SSO configurations. Resetting passwords individually (B) is not something either can do directly — identity is managed via the IdP in Enterprise Grid.

(Reference: Slack Administration Study Guide - Roles and Permissions in Enterprise Grid)

When restricting channel creation to Workspace Admins, Slack’s best practices recommend:

"Admins should maintain familiarity with naming conventions to process channel requests consistently. Additionally, setting up a clear, efficient channel request process ensures members know how to request new channels and receive prompt responses."

Option B is incorrect — restricting channel creation usually increases the admin workload. Option D is not directly aligned with Slack best practices, as permissions to create channels would still be limited to Admins.

(Reference: Slack Administration Study Guide - Channel Management and Naming Governance)

===========

—

Slack’s best practices for promoting open communication are:

"Keep everything in public channels for transparency and collaboration. Set public channel message retention to 'Keep Everything' and restrict DM retention to minimize private, siloed communication."

Also:

"Allow everyone to create channels to lower barriers to collaboration and prevent bottlenecks."

Restricting channel creation (Option C) would hinder users and reinforce the DM reliance problem.

(Reference: Slack Administration Study Guide - Messaging and Retention Policies)

===========

—

Slack recommends for sensitive HR communication:

"Use a private channel to manage sensitive communications, like hiring and recruiting questions, especially when HR policies and individual discussions are involved."

A public channel (A, D) risks sensitive information exposure. Org-wide channels (B) are less appropriate for targeting a specific audience like hiring managers.

(Reference: Slack Administration Study Guide - Managing Sensitive Information in Channels)

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)

===========

—

To ensure complete preservation of message history with no ability for users to override retention settings:

"Message Retention & Deletion should be set to 'Keep everything' for public channels, private channels, and DMs, and admins should disallow users from overriding workspace-wide retention settings."

Allowing overrides (Option B) would permit users to modify retention, which could lead to gaps in message history.

(Reference: Slack Administration Study Guide - Message Retention and Compliance Settings)

===========

—

To ensure that all users have seamless access to Google Calendar within Slack:

"Enable domain-wide authentication for Google Calendar in Slack. This ensures the app is automatically installed and authorized for all users without requiring manual setup."

Pre-approving (C) still requires individual installation by users. Posting instructions (A) is manual and inconsistent. Using Admin API (D) helps manage app requests but does not guarantee seamless access.

(Reference: Slack Administration Study Guide - Managing Apps and Domain-Wide Authentication)

On the Free plan, to ensure only employees can join automatically and prevent outsiders from signing up:

"Enable sign-up using a specific email domain (such as @company.com) so only people with company email addresses can join the workspace without needing manual invites."

Allowing all members to invite (Option A) could allow external people to join, and IdP enforcement (Option C) typically applies to paid plans, not Free.

(Reference: Slack Administration Study Guide - Workspace Access Settings on Free Plans)

===========

—

Slack best practices for channel naming recommend:

"#team- for department or functional groups, #proj- for project-based collaboration, and #ext- for Slack Connect (external) channels."

#announce (B) is more suitable for announcement-type channels, not team/project work. #help (C) is generally for support channels. #slack (E) is not a standard naming prefix.

(Reference: Slack Administration Study Guide - Channel Naming Conventions Best Practices)

—

According to Slack’s official SCIM documentation:

"Deactivating a user in the identity provider (IdP) automatically deactivates the user’s Slack account through SCIM provisioning."

This ensures the Workspace Admin is promptly deactivated across the Enterprise Grid without needing manual action in Slack itself. Options A, C, and D are manual or inefficient approaches when SCIM is available.

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

===========

—

Slack recommends for Enterprise Grid:

"Use your SIEM (Security Information and Event Management) tool integrated with Slack to review detailed logs of user activity and detect any suspicious behavior."

The SIEM integration provides deeper, real-time, and historical access tracking, compared to basic admin dashboards or member analytics.

(Reference: Slack Administration Study Guide - Monitoring Security Events and Activity Logs)

An Open workspace allows anyone in the organization to join without requiring invitations or approvals, minimizing admin overhead.

According to Slack Enterprise Grid documentation:

"Open workspaces allow any member of the organization to join, making them ideal for widely participated efforts like fundraising, campaigns, or company-wide initiatives."

Invite Only and By Request models would require manual intervention and approval, not ideal when admin resources are limited. Hidden workspaces are for restricted, confidential groups.

(Reference: Slack Administration Study Guide - Workspace Visibility Settings)

Slack best practices for culture change recommend:

"Publishing a Slack Etiquette guide that promotes channel-first communication and encouraging Slack Champions to model this behavior help shift cultural habits effectively."

Simply emailing (C) is passive and less effective. Turning off channel creation (A) stifles collaboration. Default channels (E) help onboarding, but not necessarily behavior change after adoption.

(Reference: Slack Administration Study Guide - Change Management 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 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)

===========

—

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)

===========

—

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's default permissions for Slack Connect channel approvals state:

"Only Org Admins and Org Owners can approve Slack Connect channels by default in an Enterprise Grid organization."

No manual forwarding or private channel workflows are needed if using defaults (B, D). Changing permissions to let Workspace Admins/Owners approve (A) would contradict the requirement.

(Reference: Slack Administration Study Guide - Slack Connect and Admin Permissions)

===========

—

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)

===========

—

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)

===========

—

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's feature availability by plan states:

"SAML-based SSO is supported on Business+ and Enterprise Grid plans."

Pro and Free (B, C) plans do not support SAML SSO. Enterprise Grid only (A) is too restrictive — Business+ also supports it.

(Reference: Slack Administration Study Guide - Authentication and SSO Options)

===========

—

Slack best practices advise creating a new channel:

"When you need a dedicated, transparent space for an ongoing topic, team, or project, such as a new line of business."

For quick or personal conversations (Options A, C, and D), direct messages are more appropriate.

(Reference: Slack Administration Study Guide - Channel vs. Direct Message Best Practices)

Slack recommends:

"Using SCIM provisioning combined with IdP group mapping allows organizations to efficiently manage large groups of users and assign roles based on IdP groups."

This way, you automate role assignment (faculty as Workspace Admins) while onboarding users. Options A and D don’t promote users automatically. Option C is less efficient compared to pre-provisioning via SCIM and group mapping.

(Reference: Slack Administration Study Guide - SCIM Provisioning and IdP Group Mapping)

===========

—

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 recommends Admins:

"Approve and install key apps to ensure security, streamline workflows (such as for incident management), and organize channels to make information discoverable."

Allowing all members to approve apps (Option A) is discouraged because it can pose a security risk.

(Reference: Slack Administration Study Guide - Setting Teams Up for Success with Slack Integrations)

===========

—

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's best practice for controlling fragmentation of discussions is:

"Restrict who can create public and private channels to Workspace Admins and Owners to maintain governance and reduce channel sprawl."

This ensures that projects stay visible in agreed-upon channels and minimizes unnecessary duplication.

(Reference: Slack Administration Study Guide - Channel Management Governance)

Slack strongly advises:

"Design for the minimum number of workspaces needed to meet business requirements. Fewer workspaces reduce context switching, simplify governance, and improve findability."

Option A (loose design) risks chaos. B (strict policy) is important but doesn’t directly solve workspace sprawl. D (more workspaces) worsens fragmentation.

(Reference: Slack Administration Study Guide - Workspace Design Principles for Enterprise Grid)

===========

—

The first step to addressing duplicate channels and improving discoverability is:

"Standardizing channel naming conventions, making it easier for members to find existing channels and understand their purpose."

Slack best practices emphasize that a standardized naming system helps with searchability and organization. Although adding channel topics and purposes (Option C) is also good practice, naming conventions are the first priority.

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

===========

—

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)

===========

—

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 recommends:

"Workspace Admins are ideal for handling workspace-specific tasks such as member management, approval of apps, and settings management for individual business units."

Assigning Org Admins (B) or Org Owners (D) grants broader permissions than necessary and increases risk. Creating a channel for managing requests (C) does not delegate actual admin permissions.

(Reference: Slack Administration Study Guide - Delegating Workspace-Level Administration)

===========

—

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)

===========

—

Slack security best practices recommend:

"Sensitive information should be shared in a private channel where access is restricted to authorized individuals."

Posting in a public channel (D) would expose confidential information. Group DMs (A) are less scalable and harder to manage. A one-off DM to the VP (C) may not involve all relevant stakeholders.

(Reference: Slack Administration Study Guide - Sharing Sensitive Information in Slack)

===========

—

Slack's official analytics guidelines recommend:

"The average number of active days per user is a strong measure of engagement and adoption."

Number of DMs (A) focuses only on private messaging, not overall adoption. Channel/workspace membership (B) doesn't measure activity. New workspace creation (D) is not typically relevant to students and is often disabled.

(Reference: Slack Administration Study Guide - User Activity Analytics)

===========

—

Slack native mobile security features include:

"Admins can block file downloads and copying on mobile and use domain restrictions (domain allow list) to ensure only managed accounts access corporate Slack workspaces."

Remote wipe (C) requires Mobile Device Management (MDM), not native Slack. IdP management (D) is not mobile-specific. Jailbreak detection (E) is not a native Slack feature.

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

===========

—

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

===========

—

In Slack, @channel notifies everyone in a channel, whether or not they're currently active, while @here only notifies active members.

Slack documentation explains:

"Use @channel to notify everyone in a channel of important updates. Use @here to notify only those currently online."

In a case where urgent communication needs to be received either now or seen first thing in the morning, using both ensures coverage without relying only on availability.

(Reference: Slack Administration Study Guide - Using Mentions and Channel Notifications Effectively)

===========

—

According to Slack’s official documentation on IdP group management:

"Mapping IdP groups to Slack allows automatic provisioning and deprovisioning of users to workspaces and user groups. Members added to an IdP group are automatically added to associated Slack user groups and workspaces."

This dramatically reduces manual effort and ensures correct workspace and channel access is kept current.

Slack Connect (C) is external collaboration and not managed directly via IdP groups. D and E are unrelated to IdP functionality.

(Reference: Slack Administration Study Guide - Identity Provider Group Mapping)

===========

—

Slack recommends:

"Private channels are best for sensitive discussions such as hiring, compensation, or any confidential information that should not be visible to all workspace members."

Projects (B), brainstorming (C), and event announcements (D) are usually better suited for public channels to maximize visibility.

(Reference: Slack Administration Study Guide - When to Use Private Channels)

===========

—

Slack’s guidance for handling inactive channels states:

"Archiving a channel preserves its content and history, allowing it to remain searchable without accepting new posts."

Deleting (A) would permanently remove the content. Renaming or limiting posting (C, D) are not standard clean-up procedures for inactive channels.

(Reference: Slack Administration Study Guide - Channel Lifecycle Management)

Slack officially recommends for large-scale channel management:

"Use Slack’s bulk channel management APIs (like conversations.archive and conversations.rename) to automate cleanup activities at scale."

Manually using settings (C) or requesting owners' actions (D) is impractical for 1,000+ channels. Slack’s standard UI tools (A) are efficient but not optimized for this volume compared to API automation.

(Reference: Slack Administration Study Guide - Bulk Channel Lifecycle Management)

===========

—