Salesforce-Slack-Administrator Questions and Answers

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

===========

—

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’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 best practice states:

"Before creating a new workspace in Enterprise Grid, make sure you have a Workspace Admin available to manage settings, users, and day-to-day operations."

Without a responsible Workspace Admin, new workspaces can become chaotic or mismanaged.

(Reference: Slack Administration Study Guide - Workspace Creation Best Practices)

===========

—

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)

===========

—

Slack Connect rules state:

"Once an external organization joins a Slack Connect channel, they can see all existing channel history unless otherwise configured. Before they accept, Org Owners can revoke the pending invitation to prevent access."

Thus, channel history will be visible, and the requestor should be shown how to revoke the invite.

(Reference: Slack Administration Study Guide - Slack Connect and Channel Invitation Management)

===========

—

In Slack Connect, the same channel can have different names in each participating organization’s workspace:

"Slack Connect channels may appear with different names in each organization. Members need to search by the name it appears in their own workspace."

Therefore, even though you sent the channel name from your side, the user on the partner organization side needs to find it by the name assigned in their workspace. It is not an issue of membership (A), posting permissions (C), or privacy settings (B) in this case.

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

Slack's recommendation for secure external collaboration is:

"Single-Channel Guests are ideal for providing external users with access to only one channel, maintaining strict control over permissions and access."

Multi-Channel Guests (B, C) grant access to multiple channels, which is unnecessary and riskier. Creating a new workspace (A) adds administrative burden and is unnecessary for one project.

(Reference: Slack Administration Study Guide - Managing External Users via Guest Roles)

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)

According to Slack's official documentation on Enterprise Mobility Management (EMM):

"When EMM is required, any users who are not on an approved device and have not completed setup will be immediately signed out of Slack on their mobile devices."

There is no grace period of 24 hours, 72 hours, or one week — once EMM enforcement is enabled, users must be using an approved device immediately or they are signed out.

(Reference: Slack Administration Study Guide - Mobile Security and Enterprise Mobility Management)

===========

—

The best practice for completed projects that may need to be referenced later is:

"Archive the public channel. Archived channels remain searchable and can be browsed for historical reference, but new posts are disabled."

Deleting the channel would risk losing accessibility to discussions, and unnecessary privacy changes would confuse users.

(Reference: Slack Administration Study Guide - Channel Archiving and Searchability)

Slack recommends using the Scheduled Send feature to respect teammates' working hours:

"The Scheduled Send feature allows members to compose a message now and schedule it to be delivered during the recipient’s preferred working hours."

While viewing someone's local time (C) is helpful, Scheduled Send (B) directly solves the problem by deferring the notification appropriately. Setting reminders (D) or Away statuses (A) do not proactively delay messages.

(Reference: Slack Administration Study Guide - Respecting Work-Life Balance in Global Teams)

===========

—

Slack’s compliance and security guidance states:

"A Data Loss Prevention (DLP) integration actively monitors Slack messages and files for sensitive information, and can block, quarantine, or delete data according to your compliance policies."

eDiscovery (A) archives content but doesn’t prevent exposure. Bots (C) are reactive, not proactive. Manual monitoring by admins (D) is inefficient and error-prone.

(Reference: Slack Administration Study Guide - Integrating DLP Solutions with Slack)

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’s Enterprise Grid documentation clearly states:

"Syncing IdP groups with Slack allows you to automatically manage workspace membership, channel membership, and access control based on IdP group assignments."

Key benefits include:

Automatically provisioning and deprovisioning members to specific workspaces (A).

Maintaining mandatory membership in designated channels (B).

Maintaining mandatory membership in designated workspaces (C).

Assigning system roles, approved apps, or admin roles (D, E, F) is not automatically handled through IdP group syncing.

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

Slack recommends for secure, large-scale onboarding:

"Using a SAML-based IdP with SCIM provisioning allows automatic user creation and deactivation based on your identity provider, ensuring security and control."

Email signup (B) and JIT provisioning (C) are less secure. Admin invites (D) are manual and error-prone at this scale.

(Reference: Slack Administration Study Guide - Secure User Provisioning on Business+)

===========

—

Slack compliance best practices state:

"Before configuring Slack for compliance, companies should meet with legal and compliance teams to set internal communication, retention, and monitoring policies tailored to regulatory requirements."

Implementing eDiscovery (D) is important later, but setting policies first ensures the correct technology choices. B and C may not align with regulatory needs without first setting clear policies.

(Reference: Slack Administration Study Guide - Compliance and Legal Alignment)

===========

—

The proper course of action involves:

Deleting the file through an integrated Data Loss Prevention (DLP) solution.

Reviewing access through the Audit Logs API.

Slack documentation confirms:

"A DLP integration allows detection and remediation (e.g., deletion) of sensitive files or messages. The Audit Logs API provides detailed logs of user activity, including file downloads."

Mobile Device Management (MDM) focuses on device security, not file tracking, and EKM controls encryption but doesn't show file download actions.

(Reference: Slack Administration Study Guide - Security and Compliance - Data Loss Prevention and Audit Logs)

===========

—

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)

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)

===========

—

According to Slack's Enterprise Mobility Management (EMM) documentation:

"EMM allows organizations to restrict access to Slack only from approved (managed) mobile devices, enhancing security and ensuring compliance with corporate policies."

Requiring minimum app versions (A), blocking downloads (C), and requiring secondary authentication (D) are native Slack security settings or can be handled with mobile session settings — but device restriction is specifically an EMM capability.

(Reference: Slack Administration Study Guide - Enterprise Mobility Management (EMM) Overview)

===========

—

Slack recommends:

"Setting a clear channel topic and pinned posts help define scope, and creating dedicated channels (like #help-payroll) directs users to the right place without overloading unrelated channels."

Manually redirecting (A, C) or adding payroll staff into a benefits channel (D) doesn’t address root cause or improves structure.

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

The correct scope is admin.conversations:read.

According to Slack's official API documentation:

"The admin.conversations:read scope allows approved apps to call the conversations.list and conversations.info methods for public channels across an Enterprise Grid organization."

channels:read (D) is a user token scope and limited to channels the user is a member of, while admin.conversations:read provides broader access necessary for admins or security teams at the org level. files:read (A) relates to file data, and conversations.connect:read (C) is unrelated.

(Reference: Slack Administration Study Guide - Integration and API Scopes Management)

===========

—

Slack recommends organizing discussions into appropriate channels for clarity and relevance:

"Questions or discussions about specific projects should happen in project-related channels to maintain topic focus and ensure all relevant stakeholders can view and contribute."

#general should be reserved for organization-wide announcements or broad discussions, not for project-specific questions. DMing individuals (A, B) bypasses team collaboration. Deleting the message (C) is unnecessarily punitive.

(Reference: Slack Administration Study Guide - Best Practices for Channel Organization)

—

Slack suggests for onboarding users:

"Provide easy access to self-service resources like the Slack Help Center tutorials and the Slack Resources Library to allow beginners to explore at their own pace."

The Slack Certified Admin program (C) is an advanced certification, not for beginners. Watching the webinar (D) helps admins, not general users. Submitting feedback (E) does not provide learning materials.

(Reference: Slack Administration Study Guide - Supporting New Slack Users)

===========

—

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

"When social channels overwhelm the workspace and impact findability of work-related content, creating a separate workspace for social and community discussions helps maintain focus and discoverability."

Simply deleting channels (B, D) risks damaging community culture. Making channels multi-workspace (A) doesn’t solve workspace clutter — it just duplicates visibility.

(Reference: Slack Administration Study Guide - Workspace Design for Scalability and Discoverability)

===========

—

Slack recommends:

"Channel names should follow consistent naming conventions and use hyphens between words, e.g., help-finance for a help-related finance channel."

Option A incorrectly reverses prefix order. Option B uses incorrect formatting. Option D misuses the prefix format as well.

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

===========

—

Slack adoption best practices emphasize:

"Behavior modeled by leadership has the greatest impact on changing how teams communicate. When executives and leaders use public channels, it sets a strong cultural example."

Mandating behavior (Option B) or limiting private channel creation (Option A) can cause resistance, while education (Option D) is useful but less impactful than leadership modeling.

(Reference: Slack Administration Study Guide - Building a Public-First Culture)

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)

===========

—

Slack recommends measuring transparency by:

"Tracking the percentage of messages sent or viewed in public channels versus private channels and DMs. An increase in public activity correlates to increased organizational transparency."

While engagement and activity metrics (A, C, D) are useful for other goals, measuring the public vs. private messaging ratio directly addresses transparency concerns.

(Reference: Slack Administration Study Guide - Analytics for Measuring Transparency and Collaboration)

===========

—

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)

===========

—

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)

Slack’s internal app management documentation states:

"Adding internal app collaborators allows trusted users to manage an app’s configuration, including OAuth settings, scopes, and other integration behaviors without needing Org Admin privileges."

There is no need to promote SMEs to Org Admins (B) — which would give them excessive permissions across the entire Slack environment. A and C do not enable them to manage the app directly.

(Reference: Slack Administration Study Guide - Managing Internal Apps and App Collaborators)

===========

—

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

===========

—

The best Slack practice for retiring an old channel but keeping its content accessible is:

"Post a message notifying members about the transition, then archive the channel. Archived channels are read-only but searchable."

Archiving preserves the channel’s history while preventing new posts, matching Britt's goals exactly.

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

===========

—

Slack’s documentation on file sharing specifies:

"Enabling public file sharing allows members to create public links for files that can be shared externally outside of Slack."

Public file sharing is about generating external public URLs (A), not internal sharing (B), sharing with guests (C), or Slack Connect-specific behavior (D).

(Reference: Slack Administration Study Guide - File Sharing and Public Link Management)

===========

—

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)

===========

—

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)

===========

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)

To automatically manage user deactivation:

"If your Identity Provider supports SCIM provisioning, and it is correctly configured with Slack, user deactivation in the IdP will trigger automatic deactivation of the user's Slack account."

SCIM ensures seamless deprovisioning. Just-in-Time deactivations (D) are not a Slack feature, and changing the email manually (A) is not secure or scalable.

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

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)

===========

—

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)

===========

—

Slack automation for app approvals suggests:

"Admins can define conditional rules to automatically approve or restrict apps and integrations and notify requesters of the approval status, while creating rules both at the org and workspace level for flexibility."

Listing trusted members (B) does not automate the process. Cost-based approvals (C) are too narrow and risky.

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

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’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 setting a global policy and making specific exceptions where needed:

"Setting a shorter global retention policy and then setting exceptions to keep important messages longer in specific channels gives you flexibility while controlling overall data retention."

Default settings (B) would not provide an organization-wide policy. Allowing members to manage private channel retention (C) can be risky. Setting public retention short and private channels to everything (D) doesn't align with best practices for most businesses.

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

===========

—

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)

===========

—

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)

===========

—

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)

—

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 best practices for app governance recommend:

"The most efficient method is to proactively restrict high-risk apps and automatically allow safe, non-restricted apps, minimizing admin intervention."

Annual whitelisting (B) is infrequent and can quickly become outdated. Asking users to self-rate risk (C) is unreliable. Complex rule chains (D) are difficult to maintain.

(Reference: Slack Administration Study Guide - Streamlining App Management)

===========

—

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 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 recommends for external collaboration:

"Use Slack Connect to collaborate with external partners in shared channels rather than relying on guest accounts, especially for long-term relationships."

Guests (A, C) require manual account management. A new Slack workspace (D) would fragment communication unnecessarily.

(Reference: Slack Administration Study Guide - Using Slack Connect for External Collaboration)

===========

—