Your organization is on the Slack Enterprise Grid plan. What are three benefits of syncing identity provider (IdP) groups? (Select the THREE best answers.)
A. Automatically adds or removes members of an Id group to workspaces within your org.
B. Makes membership for certain channels required to ensure that all members of an laP group remain members of a channel.
C. Makes membership for certain workspaces required to ensure that all members of an IdP group remain members of a workspace.
D. Automatically assigns system roles.
E. Automatically assigns approved apps to certain groups within your org.
F. Automatically assigns admin roles.
Explanation:
A. Automatically adds or removes members of an IdP group to workspaces within your org. This is a fundamental benefit. When you sync IdP groups, Slack can automatically provision and deprovision users from workspaces based on their group membership in your identity provider. This vastly simplifies user management, especially for large organizations with frequent hires, role changes, and departures.
C. Makes membership for certain workspaces required to ensure that all members of an IdP group remain members of a workspace. This allows for strong control over access to critical workspaces. If a specific department (represented by an IdP group) must be in a certain workspace for their work, syncing ensures they are always there. If they are removed from the IdP group, they are also removed from the required workspace.
D. Automatically assigns system roles. This is another powerful automation benefit. Instead of manually assigning Slack system roles (like Channels Admin, Users Admin, etc.) to individual users, you can assign these roles to IdP groups. As users join or leave those IdP groups, their Slack system roles are automatically updated, streamlining administrative delegation.
Let's look at why the other options are not correct:
B. Makes membership for certain channels required to ensure that all members of an IdP group remain members of a channel. While you can connect IdP groups to channels to automatically add members, Slack states that members of an IdP-synced channel can leave those channels at any time. Therefore, it doesn't require them to remain members in the same way it can for workspaces.
E. Automatically assigns approved apps to certain groups within your org. IdP group syncing primarily manages user and role provisioning, not the automatic assignment or installation of approved apps to specific groups. App management often has its own set of controls within Slack's App Administration settings.
F. Automatically assigns admin roles. This is too broad. While it does automatically assign system roles (as in option D), "admin roles" could imply broader administrative permissions not directly managed by IdP group syncing for all scenarios. Option D is more precise regarding the specific types of roles automatically assigned.
Reference:
Slack's official documentation on "Connect identity provider groups to your Enterprise organization" explicitly details these capabilities. You'll find information on how IdP groups streamline:
Workspace Membership: Auto-joining and leaving workspaces, including making workspace membership required.
Channel Membership: Auto-joining channels (though with the caveat that users can leave).
System Role Assignment: Assigning specific Slack system roles to IdP groups.
You previously built a workflow using Workflow Builder that shares onboarding information with new project team members when they join the project channel. Recently, the project took a major pivot and the scope, timeline and team are all going through many changes. Much of the information In your onboarding workflow is now out-of-date. How do you ensure new team members receive the right information?
A. Unpublish your workflow, modify the workflow steps and republish your workflow.
B. Download the workflow file, edit the JSON file and import the updated workflow file.
C. add a new step to your workflow' calling out what has changed since the previous iteration.
D. Delete your workflow and create a new workflow with the updated project information.
Explanation:
In Slack Workflow Builder, the best practice for updating an existing workflow is to:
1. Unpublish the current version (to prevent outdated information from being triggered).
2. Edit the workflow steps (update content, change messages, forms, etc.).
3. Republish it once the updates are complete.
This approach maintains the existing workflow logic and history while ensuring accurate and current information is shared moving forward.
❌ Why not the others?
B. Download and edit JSON manually:
Workflow export/import (via JSON) is available but not the intended or easiest method for small updates. It's error-prone and overcomplicated for this use case.
C. Add a step noting what changed:
That doesn’t address the core issue: the outdated content still exists. Adding a note won't replace incorrect or irrelevant information.
D. Delete and recreate:
Unnecessary extra work and removes existing logic, triggers, and history. Editing the workflow is faster and cleaner.
🔗 Official Reference:
Slack Help – Edit a Workflow
Slack – Workflow Builder Documentation
You re a Workspace Owner and you just launched Slack across your entire organization. You look at the percentage of messages viewed in public channels versus in private channels and direct messages (DMs), and notice that most communication is happening in DMs. Which two actions should you take to promote the usage of channels? (Select the TWO best answers.)
A. Turn off the ability for users to create channels, so they can collaborate only in the exist.ng channels.
B. Publish a Slack Etiquette guide that includes a rule of defaulting to using channels.
C. Send a company-wide email asking members to use Slack channels for collaboration.
D. Ask your Slack Champions to model the behavior, and encourage others to post in channel.
E. Create the default channels, so that employees have more options in the channels they can use for collaboration.
Explanation:
When most communication is happening in DMs rather than public channels, it limits transparency, knowledge sharing, and cross-team collaboration. In Slack best practices, the goal is to encourage employees to work in public channels unless there’s a clear reason for privacy.
✅ B. Publish a Slack Etiquette guide that includes a rule of defaulting to using channels – This is a key enablement step. Providing a written guide helps set organization-wide expectations and gives employees clarity on why and how to use channels over DMs. It also formalizes the behavior you want to see.
✅ D. Ask your Slack Champions to model the behavior, and encourage others to post in channel – Champions (power users or early adopters) can lead by example. When influential members of the workspace consistently post in channels and remind others to do the same, it normalizes that behavior.
❌ Why not the others:
A – Turning off channel creation can actually reduce collaboration opportunities. It doesn’t address the cultural issue of people defaulting to DMs.
C – A one-time company-wide email is not enough to change habits; it’s passive and has no reinforcement mechanism.
E – Adding more default channels may cause clutter and confusion without guiding employees on how to use them effectively. The problem isn’t the number of channels—it’s the behavior.
Reference:
✔ Slack’s official guidance on encouraging channel use: Slack – Encourage your team to work in channels
✔ Slack Admin Guide: "Lead by example, establish channel norms, and make guidelines visible"
You're a Slack admin reviewing an approval request for an app to be used in your organization You notice that a particular app requires permission to "Send messages as @bot." Which box scope will need to be assigned to the app to grant the requested permission? (Select the best answer.)
A. chat:write
B. admin apps-write
C. admin.conversations:read
D. chathistory
Explanation:
Correct Answer: A. chat:write
The permission to "Send messages as @bot" allows an app to post messages in Slack channels or conversations on behalf of a bot user. According to Slack’s API documentation, this capability is governed by the chat:write permission scope. This scope enables an app to post messages in approved channels and conversations where the bot is a member. It is the most relevant scope for sending messages as a bot, as it directly controls the ability to write messages in Slack.
❌ Option B: admin.apps:write is incorrect because this scope relates to managing app installations and configurations, not sending messages. It’s used for administrative actions like approving or restricting apps.
❌ Option C: admin.conversations:read is incorrect as it allows reading conversation details, such as channel metadata, but does not permit sending messages.
❌ Option D: chat:history is incorrect because this scope (likely referring to channels:history or similar) allows viewing message history in channels, not posting new messages.
Reference:
Slack API documentation on permission scopes: https://api.slack.com/scopes/chat:write
Anna, a Workspace Owner, has decided to restrict channel creation in her workspace to Workspace Admins only. This will allow her and the other Workspace Admins to enforce channel naming conventions. What are two best practices Workspace Admins should follow in this scenario? (Choose two.)
A. Keep up to date on all channel naming conventions to accurately process requests.
B. Prepare for a decrease in workload since channel requests will need to be processed less frequently.
C. Create a process for channel requests.
D. Appoint other members of their workspace to help with the workload.
Explanation:
1. Option A (Correct): ✅
Since channel creation is restricted to Workspace Admins, they must be fully aware of the naming conventions to ensure consistency and compliance when approving or creating channels.
ℹ️ Reference: Slack’s Admin Best Practices recommends admins maintain clear guidelines for channel naming.
2. Option C (Correct): ✅
A formalized process (e.g., a request form, approval workflow, or dedicated #channel-requests channel) ensures efficiency and transparency when users need new channels.
ℹ️ Reference: Slack’s Channel Management Guide suggests structured processes for managed channel creation.
❌ Why the Other Options Are Incorrect:
Option B (Incorrect): Restricting channel creation often increases admin workload due to manual review of requests, not decreases it.
Option D (Incorrect): Only Workspace Owners/Admins can create channels in this scenario—appointing non-admins wouldn’t help unless they’re granted admin rights (which isn’t a best practice for workload delegation).
A company has recently implemented Slack, and many teams have started to use it instead of email. Admins want to help members be more productive in Slack without overwhelming them with too much training. Which of the below would be the most effective way to increase members’ productivity in Slack?
A. Show employees how they can request new apps to be installed in Slack.
B. Train everyone on how to create Slack integrations.
C. Allow employees to install social apps, like Giphy, that will help attract new Slack members.
D. Connect tools they are already using, like Google Calendar or Box, to Slack.
Explanation:
When a company adopts Slack, the fastest way to increase productivity without overwhelming users with training is to integrate Slack with the tools they already use daily. By connecting apps like Google Calendar, Box, Zoom, or Jira to Slack, employees can receive notifications, take actions, and access content directly in Slack. This creates immediate value by reducing context-switching and email reliance, while also helping members naturally learn how to leverage Slack for work.
✅ D. Connect tools they are already using – This is the most impactful productivity booster because it lets employees keep using familiar workflows but in a centralized Slack workspace. It also demonstrates Slack’s capability as a work hub.
❌ Why not the others:
A – Teaching employees how to request new apps is helpful for governance, but it doesn’t directly improve day-to-day productivity.
B – Training everyone on creating integrations is overly technical and unnecessary for most users; it’s more suited for developers or admins.
C – Social apps like Giphy may improve engagement or culture, but they don’t directly drive productivity.
ℹ️ Reference:
Slack Help: Connect your tools with Slack
Slack Admin Guide: "Integrate the tools your team already uses to make work more efficient in Slack"
You're a Workspace Admin for your organization's Slack's Business+ instance. You need to report on the number of both daily and weekly active users within your workspace in the last 30 days. Where can you find this information? (Select the best answer.)
A. Org analytics dashboard
B. Workspace analytics dashboard
C. Analytics members dashboard
E. Message activity analytics
Explanation:
As a Workspace Admin for a Slack Business+ instance, you can find the number of daily and weekly active users within your workspace in the last 30 days on the Workspace analytics dashboard. According to Slack’s documentation, the Workspace analytics dashboard provides detailed metrics about workspace activity, including Daily Active Users (DAU) and Weekly Active Users (WAU), which measure the number of members who actively use Slack (e.g., sending messages, reading messages, or performing other actions) daily or weekly. To access this:
1. From your desktop, click your workspace name in the top-left corner.
2. Select Tools & settings from the menu, then click Workspace analytics.
3. Navigate to the Members tab to view detailed metrics, including DAU and WAU, for the last 30 days. You can adjust the date range by clicking the “Last 30 days” dropdown in the top-right corner.
Option A: Org analytics dashboard is incorrect because this dashboard is available only for Enterprise Grid plans, not Business+ plans. It provides organization-level insights across multiple workspaces, which is not applicable here.
Option C: Analytics members dashboard is incorrect because there is no specific “Analytics members dashboard” in Slack. The Members tab within the Workspace analytics dashboard is where member-related metrics like DAU and WAU are found.
Option E: Message activity analytics is incorrect because message activity analytics focus on interactions with specific messages (e.g., views or reactions) and do not provide aggregate DAU or WAU metrics.
ℹ️ Reference:
🧩 Slack documentation on viewing the analytics dashboard
🧩 Slack analytics guide on available metrics
The security team at your organization wants to monitor different public channels that are created in your Slack Enterprise Grid instance. The team requested access to the conversations.list and conversations. info API methods to get the required data about the channels. As a Slack admin, you need to assign the required scopes to their Slack app for the security team to be able to invoke the APIs. Which scope should you assign to allow the security team to retrieve a list of all public channels only and retrieve information about a public channel? (Select the best answer.)
A. files:read
B. admin.conversations:read
C. conversations.connect:read
D. channels:read
Explanation:
The channels:read scope allows a Slack app to:
✔ Retrieve a list of all public channels (using conversations.list).
✔ Fetch details about a specific public channel (using conversations.info).
This matches the security team's requirement to monitor public channels only.
❌ Why Other Options Are Incorrect:
A. files:read: Grants access to file metadata/content, not channel data. Irrelevant here.
B. admin.conversations:read: Used for Enterprise Grid admins to access all channels (including private and shared), not just public ones. Overkill for this use case.
C. conversations.connect:read: Designed for Connect apps (external org collaborations), not internal public channel monitoring.
Reference:
Slack API Scopes Documentation confirms channels:read is the correct scope for public channel access.
conversations.list and conversations.info methods require this scope for public channels (API method docs).
You're a Workspace Owner at a small business that used Slack's Free plan in their first year. However, its business is growing fast enough to justify upgrading to a paid plan.
The requirements:
• Users want to be able to access their old messages and integrate Slack with
their calendars.
• You want to use Okta to provision users in order to provide additional security
and simplicity to the employee onboarding process.
• Field representatives need to be able to access Slack securely on their company-owned mobile devices.
Based on the requirements, what should you recommend?
(Select the best answer.)
A. Stay with the Slack Free plan for another year.
B. Move to the Slack Pro plan.
C. Move to the Slack Business+ plan.
D. Move to the Slack Enterprise Grid plan.
Explanation:
Let’s match each requirement with the Slack plan features.
1. Access to old messages – The Free plan limits message history (currently 90 days for free workspaces). Paid plans like Pro and Business+ offer full message history.
2. Integrate Slack with calendars – App integrations (like Google Calendar or Outlook Calendar) are supported on paid plans, so both Pro and Business+ qualify here.
3. Okta for user provisioning – SCIM-based provisioning and SSO with identity providers (like Okta) are not available on the Pro plan. They’re available starting from Business+.
4. Secure mobile access for field representatives – Features like Enterprise Mobility Management (EMM) to control company-owned mobile device access start with Business+.
The Enterprise Grid plan would also meet these requirements, but it’s designed for very large organizations with multiple interconnected workspaces and complex compliance needs—overkill for a growing small business. Business+ is the first plan tier that meets all listed needs without unnecessary complexity or cost.
Why not the others:
A – The Free plan fails all requirements except basic Slack usage; no old message history or advanced integrations.
B – The Pro plan meets some needs but lacks SCIM provisioning and EMM support.
D – Enterprise Grid meets the needs but is not cost-efficient for a small business without multi-workspace or heavy compliance demands.
Reference:
✔ Slack Plans & Pricing: Slack feature comparison
✔ Slack Business+ plan features: Slack Business+ Overview
As a Workspace Admin, you've been tasked with launching Stack at your company. You need to provide resources for beginners to learn more about Slack on their own What are the two best ways you can help your coworkers access relevant Slack learning materials? (Choose 2 answers)
A. Ask members to review the 'Slack tutorials' section of the Help Center.
B. Guide members to the Slack resources library on slack.com.
C. Ask members to complete the Slack certified Admin program.
D. Invite members to watch the on-demand How to launch Slack at your organization' webinar.
E. Use the /feedback command or email feedback@slack.com to submit a support request to Slack.
Explanation:
✅ Correct Answers: A. Ask members to review the 'Slack tutorials' section of the Help Center and B. Guide members to the Slack resources library on slack.com
Providing employees with self-service learning resources is one of the most effective ways to help them get comfortable with Slack without overwhelming them with direct training sessions. Both the Slack Help Center’s tutorials and the Slack Resources Library offer clear, structured, and accessible materials for beginners.
📖 A. Ask members to review the 'Slack tutorials' section of the Help Center ✅
The Slack Help Center offers a dedicated “Slack tutorials” section with short, step-by-step guides on using core Slack features, from sending messages to organizing channels. This resource is beginner-friendly and allows users to learn at their own pace, making it a perfect first stop for self-guided onboarding. Directing employees here ensures they have trusted, official instructions.
📚 B. Guide members to the Slack resources library on slack.com ✅
The Slack Resources Library, available on Slack’s main website, contains articles, tips, videos, and customer stories that explain not just how Slack works but also best practices for using it effectively in various work scenarios. This resource is great for users who want to go beyond basic features and explore workflows and productivity tips.
🎓 C. Ask members to complete the Slack Certified Admin program
The Slack Certified Admin program is an advanced certification course intended for workspace administrators, not general employees. It covers deep configuration and governance topics rather than basic user training, making it inappropriate for beginners.
🎥 D. Invite members to watch the on-demand 'How to launch Slack at your organization' webinar
While this on-demand webinar is valuable for admins and project leads responsible for rollout strategy, it’s not designed as a general beginner’s guide for everyday Slack users. Most employees won’t need this level of detail about the implementation process.
📩 E. Use the /feedback command or email feedback@slack.com to submit a support request to Slack
This option is for providing product feedback or reporting issues to Slack’s support team. It does not serve as a learning resource and won’t help beginners get up to speed with Slack features or workflows.
📚 Reference:
Slack Tutorials – Help Center
Slack Resources Library
You're a prospective customer looking to purchase Slack for your organization of approximately 50 employees. You need to ensure that the plan supports SAML single sign-on (SSO) for authentication. Which plan(s) fit the requirement?
A. Enterprise Grid only
B. Pro, business+ and Enterprise Grid
C. Free, Pro, Business+ and Enterprise Grid
D. Business+ and Enterprise Grid
Explanation:
SAML-based single sign-on (SSO) is a security feature that allows users to access Slack using their existing credentials through an identity provider (IdP) such as Okta, Microsoft Entra ID, or Google Workspace. According to Slack’s official documentation and Salesforce Trailhead, SAML SSO is supported only on the Business+ and Enterprise Grid plans, making these plans suitable for an organization of approximately 50 employees requiring this feature. Below is a detailed breakdown of each option:
Option A: Enterprise Grid only
This option is incorrect because it excludes the Business+ plan, which also supports SAML SSO. The Enterprise Grid plan is designed for larger organizations or those needing advanced features like organization-wide administration, multiple workspace management, and enhanced security controls (including SAML SSO). While it meets the requirement, it’s not the only plan that does, as Business+ also offers SAML SSO for smaller organizations like one with 50 employees. Choosing Enterprise Grid alone might be overkill for a 50-employee organization, as it’s typically tailored for enterprise-scale needs with higher costs.
➜ Why it’s incorrect: It omits the Business+ plan, which also supports SAML SSO and is more suitable for a smaller organization.
Option B: Pro, Business+, and Enterprise Grid
This option is incorrect because the Pro plan does not support SAML SSO. The Pro plan allows authentication via Google Auth (OAuth 2.0), which syncs email addresses and display names but does not support the full SAML 2.0 standard required for advanced SSO configurations with IdPs like Okta or Microsoft Entra ID. In contrast, both Business+ and Enterprise Grid support SAML SSO, making this option partially correct but inaccurate due to the inclusion of the Pro plan.
➜ Why it’s incorrect: The Pro plan only supports Google Auth, not SAML SSO, which is a key requirement.
Option C: Free, Pro, Business+, and Enterprise Grid
This option is incorrect because neither the Free nor the Pro plan supports SAML SSO. The Free plan relies on Slack’s built-in authentication (email and password) and does not offer any SSO options. The Pro plan, as mentioned, supports Google Auth but not SAML SSO. Including these plans alongside Business+ and Enterprise Grid makes this option too broad and inaccurate.
➜ Why it’s incorrect: The Free and Pro plans do not support SAML SSO, which is essential for the organization’s needs.
✅ Option D: Business+ and Enterprise Grid (Correct Answer)
This option is correct because both the Business+ and Enterprise Grid plans support SAML-based SSO, meeting the requirement for secure authentication via an IdP. The Business+ plan is well-suited for an organization of 50 employees, offering SAML SSO, advanced admin controls, and 24/7 support, making it a cost-effective choice for small to medium-sized teams. The Enterprise Grid plan also supports SAML SSO and adds features like organization-wide analytics, SCIM provisioning, and support for multiple workspaces, but it may be more than necessary for a 50-employee organization due to its higher cost and enterprise focus. Since the question asks for plans that fit the SAML SSO requirement, both Business+ and Enterprise Grid are valid.
➜ Why it’s correct: Both plans support SAML SSO, and Business+ is likely the most practical choice for an organization of 50 employees.
Additional Considerations:
✔ For an organization of 50 employees, the Business+ plan is typically recommended due to its balance of features and cost. It supports SAML SSO, allowing integration with popular IdPs like Okta, Google SAML, or Microsoft Entra ID, and includes other features like custom retention policies and unlimited message history.
✔ The Enterprise Grid plan, while also supporting SAML SSO, is better suited for larger organizations or those needing advanced governance and scalability across multiple workspaces.
✔ To configure SAML SSO, a Workspace Owner (for Business+) or Org Owner (for Enterprise Grid) must set up the connection in Slack’s SSO & authentication settings, providing the SAML 2.0 Endpoint URL, Identity Provider Issuer URL, and x.509 certificate from the IdP.
References:
➜ Salesforce Trailhead: Implement the Right Authentication Process
➜ Slack Help Center: Set up SAML single sign-on for Slack
➜ Slack Help Center: Manage single sign-on settings
You're a Workplace Admin for a major retail chain in Europe on the Slack Pro plan. An
executive user at your company recently discovered that Slack message retention for your
organization was set at one year.
The executive asked you to find out how to access their channel history from more than 18
months ago using any means necessary.
Will it be possible for you to recover the data?
(Select the best answer.)
A. Yes, because Slack's disaster recovery policy and business continuity plan provide backups that organizations on the Slack Pro plan can access upon request from Org Admins.
B. Yes, because Slack employs multi-factor authentication for all administrative access to systems. Slack can access channel history upon request from Org Admins.
C. No, because this company is in a territory affected by GDPR. Slack Is legally not allowed to provide this data after the retention date has passed.
D. No, because customer data is removed immediately upon expiration of message retention. Slack and deletes all information from production systems at that time.
Explanation:
Correct Answer: D. No, because customer data is removed immediately upon expiration of message retention. Slack deletes all information from production systems at that time.
➜ Slack’s message retention policy is strict—once the retention period (in this case, one year) expires, the data is permanently deleted from Slack’s production systems. This applies to all plans, including Slack Pro. Slack does not retain backups of expired messages for customers, even upon request.
Why the Other Options Are Incorrect:
A. Incorrect: Slack does not provide disaster recovery backups for expired messages. Their data retention policy states that once retention expires, data is irrecoverable.
B. Incorrect: Multi-factor authentication (MFA) is a security feature, not a data recovery method. Slack cannot retrieve deleted messages after retention expires.
C. Incorrect (Misleading): While GDPR imposes strict data handling rules, Slack’s inability to recover messages is not due to GDPR compliance—it’s because Slack permanently deletes expired data. Even in non-GDPR regions, this data would still be unrecoverable.
Key Takeaway:
✔ Pro Plan retention is fixed (customizable only on Enterprise Grid).
✔ No backups exist for expired messages—once deleted, they’re gone forever.
✔ If the executive needs longer retention, upgrading to Enterprise Grid (with custom retention policies) is the only solution.
Reference:
Customize data retention in Slack
Slack Pro vs. Enterprise Features
| Page 5 out of 17 Pages |
| Previous |