Salesforce-Slack-Administrator Salesforce Certified Slack Administrator (Slack-Admn-201) Questions and Answers

According to Slack's official documentation:

"Channel Managers can rename and archive channels, convert public channels to private (but not vice versa), and add/manage other Channel Managers."

They cannot restore deleted channels (B, D) or manage user roles in the org-wide sense (C).

(Reference: Slack Administration Study Guide - Channel Manager Role Capabilities)

===========

—

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)

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)

===========

—

In Slack Enterprise Grid, a Workspace Admin is the correct role for someone managing settings and guest invitations for a specific workspace.

Slack documentation says:

"Workspace Admins can manage workspace-level settings, invite and manage guests, and perform administrative tasks for their designated workspace."

Assigning Frank as a Workspace Admin gives him the necessary permissions to manage the workspace without granting organization-wide control (which is reserved for Org Admins and Primary Org Owners). Options like Member or Multi-Channel Guest do not have the needed permissions.

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

===========

—

When deciding whether to create a new workspace in Enterprise Grid, Slack recommends:

"Start by assessing whether the business unit's data retention, security, and compliance requirements are different enough from existing workspaces to justify workspace separation."

If stricter data retention or compliance needs are present, a separate workspace may be necessary to apply different settings. Collaboration can still happen through multi-workspace channels if needed. Preferences about DMs (B) or apps (D) are secondary considerations.

(Reference: Slack Administration Study Guide - Enterprise Grid Workspace Planning)

===========

—

Slack's official documentation states:

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

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

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

(Reference: Slack Administration Study Guide - SCIM Provisioning)

===========

—

Slack recommends for official, organization-wide communications:

"Create an org-wide channel (such as #announcements) where only admins and owners can post. This ensures important messages are visible to all and remain uncluttered by unrelated posts."

Option B and C involve redundancy and fragmentation. Using @channel in #general (D) risks spamming and frustrating members.

(Reference: Slack Administration Study Guide - Best Practices for Org-Wide Announcements)

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

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

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

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

===========

—

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)

===========

—

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)

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)

===========

—

Slack recommends:

"Use public announce-only channels for company-wide updates. Only designated members can post, while everyone else can view and react without disrupting the information flow."

This keeps updates structured and prevents off-topic discussion, while maximizing visibility to the whole organization.

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

===========

—

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)

===========

—

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 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 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 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 recommends using Slack Connect for secure, flexible external collaboration:

"Slack Connect enables organizations to manage their own members, privacy settings, and security policies while sharing channels with external partners."

Using guest accounts (B, D) would require you to manage all external users yourself, which is burdensome and inflexible. Option C incorrectly implies that Slack Connect automatically sunsets access — expiration must be manually managed.

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

===========

—

Workspace Owners and Admins can:

"Remove any custom emoji via the 'Customize Slack' page, ensuring that inappropriate or unwanted emoji are promptly deleted."

Option A disables all custom emoji creation but doesn't address removing a specific emoji. Option B incorrectly suggests Brian (a non-admin) can delete it. Option D is incorrect — deletion is fully possible for Admins.

(Reference: Slack Administration Study Guide - Managing Custom Emoji and Content Moderation)

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

"If channel content needs to become more sensitive or confidential, converting a public channel to private helps control access to information."

Low membership (B) or duplicate conversations (C) are not valid reasons. Notification preference (A) does not relate to confidentiality.

(Reference: Slack Administration Study Guide - Guidelines for Converting Channels)

===========

—

Slack recommends for Enterprise Grid governance:

"Workspace creation requests should be routed to a private admin team for evaluation, ensuring that new workspaces align with business needs, security policies, and organizational strategy."

Public channels (A) expose sensitive administrative discussions. C and D bypass proper governance and risk fragmented Slack management.

(Reference: Slack Administration Study Guide - Workspace Creation and Governance)

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 recommends for security auditing:

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

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

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

===========

—

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)

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 official plan features state:

"Customizable message and file retention policies are available on Pro, Business+, and Enterprise Grid plans."

Free plan (C) does not support customizable retention. It's limited to 90 days history unless upgraded. Enterprise Grid-only (D) is too restrictive.

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

Slack's best practice for Enterprise Grid states:

"You can use your identity provider (IdP) groups to automatically provision users into the appropriate workspaces, ensuring that workspace membership reflects organizational structure."

Manual additions by HR (A) or managers (C) are error-prone and inefficient. User groups (D) control notification settings inside workspaces, but not workspace membership.

(Reference: Slack Administration Study Guide - Managing Workspace Membership via IdP Groups)

===========

—

According to Slack’s Enterprise Grid admin settings:

"Org Admins and Org Owners can lock the guest invitation setting at the organization level from the Org Admin dashboard to prevent Workspace Admins from controlling it independently."

Option A only applies to workspace-level settings (not sufficient). Option B is unnecessary because Org Admins also have permission. Option C is just communication without any enforcement.

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

===========

—

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

===========

—

Slack best practices state:

"SAML-based SSO and SCIM provisioning (through IdP groups) are available on the Business+ plan. This enables automation of user management and enhances login security."

Google Workspace SSO (A) without SAML lacks the full control needed. 2FA (B) is a good practice but doesn't automate provisioning. Enterprise Grid (C) would be overkill and costly for a small organization.

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

===========

—

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)

===========

—

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

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 Enterprise Grid provides an Org-level Members analytics section where you can view and export detailed information about all users, including guest accounts.

"Org Admins and Org Owners can export member lists from the Org analytics dashboard, including guest account details like type (single-channel or multi-channel), status, and associated workspaces."

Gathering from each workspace (A) is inefficient and manual. Exporting from the Export Data tab (D) relates to message and file exports, not member data. Opening a ticket with Slack (B) is unnecessary for this standard administrative task.

(Reference: Slack Administration Study Guide - Org Analytics and Member Exports)

===========

—

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)

===========

—

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

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

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

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

===========

—

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’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 officially supports configuring Default Channels for workspaces:

"Default channels are channels that new members will automatically join when they first sign in to Slack."

Creating workflows (A) or pinning channels (B) are helpful for awareness but don't enforce automatic joining. Training managers manually (C) is inefficient and prone to errors.

(Reference: Slack Administration Study Guide - Managing Default Channels)

===========

—

Slack's Workflow Builder allows users to create workflows without writing code, and Admins have visibility over workflows to maintain governance.

According to Slack documentation:

"Workspace Owners and Admins can view and manage all published workflows in their workspace." "For Enterprise Grid organizations, Org Owners and Org Admins can see workflows across all workspaces."

Option A is false — creating a workflow is a quick process requiring fewer than five clicks. Option C is inaccurate because regular members can also view workflows they have access to via Workflow Builder, not just Owners or Admins.

(Reference: Slack Administration Study Guide - Workflow Builder and Admin Controls)

===========

—

Slack ensures that all customer data:

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

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

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

===========

—

Slack recommends using Slack Connect for external collaboration across companies.

According to Slack Connect official guidelines:

"Slack Connect lets you securely collaborate with external organizations in channels or direct messages, without needing to add external users as guests in your workspace."

Rather than creating guest accounts (A) or modifying your IdP (C), the correct and scalable method is setting up Slack Connect channels. Option D (setting up a separate Slack workspace) is not necessary and would complicate governance.

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

===========

—

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 guidance emphasizes:

"Default channels help orient new members by exposing them to important organizational channels and reinforcing naming conventions and community norms."

A is inaccurate — default channels are typically public (not required for all communication). B is incorrect because default channels cannot be private. C refers to general Slack usage, but not specifically about default channels.

(Reference: Slack Administration Study Guide - Setting Default Channels for Workspaces)

===========

—

Using Workflow Builder is the best way to:

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

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

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

===========

—

Slack 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 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 Connect allows you to:

"Search for external users by entering their email address in the Slack Connect section of your sidebar to verify if their organization uses Slack."

Inviting first (B) is less efficient. Asking your Workspace Owner (A) is manual. The "People" section (D) only searches internal directory members.

(Reference: Slack Administration Study Guide - Using Slack Connect Discovery)

===========

—

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 user group functionality explains:

"When a user group is @mentioned, all members of the user group are notified, making it easy for others to reach all members at once for questions or updates."

Option A is misleading because visibility of user groups depends on workspace settings. B and C are inaccurate — external users cannot be added, and users cannot add themselves to user groups.

(Reference: Slack Administration Study Guide - Using User Groups)

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)

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)

===========

—

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

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

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

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

===========

—

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

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

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

• Creating a private channel with a personal benefits workflow:

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

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

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

—

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)

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)

===========

—

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