Salesforce-Slack-Administrator Salesforce Certified Slack Administrator Exam Question and Answers

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)

===========

—

The best practice is to install official, vetted apps for each alerting tool from the Slack App Directory and configure them to post into a centralized channel (such as #alerts-all). According to Slack documentation:

"Integrating alerting tools through approved apps ensures reliable, structured, and centralized notifications. Centralized channels allow all relevant teams to quickly monitor, identify, and respond to incidents."

Building custom apps is unnecessary if existing integrations meet the needs, and reminders or Slackbot triggers do not solve the systemic problem.

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

===========

—

According to Slack App Management best practices:

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

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

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

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

Slack officially recommends for large-scale channel management:

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

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

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

===========

—

Slack recommends:

"When using SCIM provisioning, admins can automate the deactivation of user accounts through the SCIM API, ensuring synchronization with identity provider (IdP) data."

Deactivating manually through the Org Settings (A) is possible but less efficient and scalable. Contacting Slack via /feedback (B) is not appropriate for standard admin tasks. Deactivation is not limited to Primary Org Owners only (D).

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

===========

—

According to Slack Enterprise Grid administration best practices:

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

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

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

===========

—

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

Create confusion and friction in adoption.

Reduce transparency and cross-functional collaboration.

Slack documentation highlights:

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

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

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

===========

—

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)

—

Slack requires:

"Enterprise Grid must use an identity provider (IdP) to manage authentication via SSO before users can sign in. SSO must be configured first for member access."

Options A and B bypass the necessary authentication process and would create user confusion later. Downgrading to Business+ (C) defeats the purpose of deploying Enterprise Grid.

(Reference: Slack Administration Study Guide - Preparing Identity Management for Enterprise Grid)

Slack's best practices for private, sensitive, or surprise planning activities:

"Create a private channel when planning events that should remain confidential to a specific group of people."

This protects the surprise. Public channels (A) expose planning. Group DMs (B) are limited (maximum of 8 people) and informal. A thread in a public space (C) is risky for surprises.

(Reference: Slack Administration Study Guide - Managing Sensitive Conversations)

===========

—

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

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

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

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

===========

Slack Connect discoverability must be enabled by an organization for others to search and find them:

"If an external organization has disabled Slack Connect Discoverability, they will not appear in search results, even if they use Slack."

It is not about whether you already have a Connect channel (A), or necessarily whether they are on a free plan (B — free plans can still accept Connect invites with some limitations). Option C (turning off Slack Connect entirely) would prevent channel creation but is not specifically why search would fail.

(Reference: Slack Administration Study Guide - Slack Connect Discoverability Settings)

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)

===========

—

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

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

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

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

===========

—

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

===========

—

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 best practices for organized workspaces state:

"Establishing and enforcing naming conventions helps members easily identify the purpose of a channel at a glance and maintain workspace organization."

Apps (A) aren't necessary for simple naming. Asking for descriptions (B) is unreliable. Spreadsheets (C) are cumbersome and not visible at channel creation.

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

===========

—

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

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

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

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

===========

—

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

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

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

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

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

Slack's default permissions for Slack Connect channel approvals state:

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

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

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

===========

—

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

"Multi-workspace channels allow you to share a channel between select workspaces within an Enterprise Grid org, enabling collaboration across designated workspaces while keeping others excluded."

Org-wide channels (A) include all members by default. Slack Connect (B) is for external organizations, not internal collaboration. Inviting Internal members as guests (C) is unnecessary and inefficient.

(Reference: Slack Administration Study Guide - Multi-Workspace Channels)

===========

—

Slack's documentation on EMM policies specifies:

"Enterprise Mobility Management (EMM) requirements apply only to full members of your Slack organization. Guest accounts (Single-Channel or Multi-Channel Guests) are not required to use the Slack for EMM app."

Thus, guests are exempt from EMM enforcement. Options B and C incorrectly state guests can be controlled via EMM. D is unrelated.

(Reference: Slack Administration Study Guide - EMM and Guest Account Behavior)

According to Slack’s data retention policies:

"When a message retention policy is applied and messages reach their expiration, Slack permanently deletes the messages from production systems, and recovery is not possible."

Slack’s business continuity plans and MFA security are unrelated to data retrieval for expired content. GDPR (C) impacts retention requirements but the critical reason for non-recovery is Slack’s deletion behavior (D).

(Reference: Slack Administration Study Guide - Message Retention and Data Deletion Policy)

===========

—

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)

===========

—

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

"Keep all files, including deleted files."

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

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

===========

—

The most efficient method to ensure all users are automatically added is:

"Make the workspace a default workspace for the Enterprise Grid organization. This way, all current and future members will automatically be added without manual intervention."

Syncing IdP groups (Option D) could work but requires additional setup complexity and group management.

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

===========

SAML SSO provides:

"Organizations with more control over their authentication policies, including password requirements, session durations, and login behaviors."

"Employees can use their existing login credentials for all applications, including Slack, through SSO integration with the identity provider."

Option B is wrong because SSO depends on having an IdP in the first place. Option C is incorrect because SSO is available only on certain Slack paid plans (not all). Option E refers to Enterprise Key Management (EKM), not SSO.

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

===========

—

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 SCIM provisioning combined with IdP group mapping allows organizations to efficiently manage large groups of users and assign roles based on IdP groups."

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

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

===========

—

Slack recommends for mobile session management:

"Setting a mobile session duration of around two weeks provides a good balance between security and usability, ensuring users aren't prompted to log in too frequently."

Allowing users to set their own session length (A) would reduce security controls. Logging everyone out during any threat (B) is too disruptive for normal operations. Allowing infinite sessions (D) risks serious security exposure.

(Reference: Slack Administration Study Guide - Mobile Security Best Practices)

In Enterprise Grid, if auto-provisioning is enabled via an IdP group, when a member is added to that group, they are automatically provisioned to the specified workspace. According to Slack’s official Enterprise Grid documentation:

"When a member is added to an IdP group that’s mapped to a workspace, they will be automatically provisioned (added) to the workspace, unless the workspace is set as hidden."

Hidden workspaces require an invitation or manual addition and are excluded from automatic group provisioning. Therefore, unless the workspace is hidden, members will automatically join it without needing to take any manual action.

(Reference: Slack Administration Study Guide - Enterprise Grid Configuration and IdP Group Management)

Slack recommends:

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

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

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

===========

—

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 define Slack’s success, it's essential to tie usage to business outcomes and improved productivity — not just technical setup or user counts.

Slack documentation recommends:

"Engage business units to identify opportunities where Slack has improved workflows, collaboration, or response times, and measure these against baseline expectations."

This makes the success conversation focused on value and business impact rather than technical completeness or adoption rates alone.

(Reference: Slack Administration Study Guide - Defining Success and ROI with Slack)

===========

—

When engagement in public channels drops, Slack recommends education and re-engagement campaigns like hosting a “Slack day” to showcase best practices.

Slack documentation highlights:

"Slack Days are opportunities to encourage better usage patterns, provide learning sessions, and reinforce the importance of open communication through public channels."

Option A and D focus on short-term fixes and notifications, not improving behavior sustainably. Option B alone is not a complete strategy.

(Reference: Slack Administration Study Guide - Driving Adoption and Maintaining Engagement)

Slack encourages using threads to keep conversations organized and prevent clutter in busy channels.

Official Slack documentation says:

"Threads help organize conversations around specific messages, allowing multiple discussions to happen simultaneously within a single channel without causing confusion."

While thanking or quick responses (Option B) can also be done in threads, the primary reason for using threads is to manage multiple discussions efficiently.

(Reference: Slack Administration Study Guide - Best Practices for Channel Communication and Threading)

===========

—

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 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 native mobile security features include:

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

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

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

===========

—

Slack domain claiming is:

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

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

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

===========

—

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 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 Workflow Builder guidance states:

"To update an existing workflow, unpublish it, make edits to the steps or messages, and republish it."

Editing JSON manually (B) is unnecessary. Adding a step (C) is a patch, not a real fix. Deleting and rebuilding (D) is inefficient when Slack allows direct editing.

(Reference: Slack Administration Study Guide - Managing Workflows)

===========

—

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 using public channels for community-building and location-specific discussions:

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

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

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

Slack 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 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 security best practices recommend:

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

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

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

===========

—

Slack's official 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'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)

===========

—

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 EKM guidelines specify:

"If sensitive information is exposed improperly (for example, shared in the wrong channel), you can revoke the encryption key, making that content permanently inaccessible."

Guests (A) or contractors in Slack Connect (B) are expected collaboration contexts and do not warrant revoking keys unless data leakage happens.

(Reference: Slack Administration Study Guide - Enterprise Key Management (EKM) Operations)

===========

—

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 strongly advises:

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

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

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

===========

—

The best practice outlined in Slack Enterprise Grid documentation:

"Enable workspace creation requests, so users can request new workspaces that will be routed to Org Admins via an internal channel for review and approval."

This approach scales better for high-volume requests, allowing multiple admins to track and approve them efficiently from a centralized channel, rather than relying on manual direct messages.

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

===========

—

Slack Clips are recommended for asynchronous communication:

"Slack Clips allow users to record video, screen shares, and voice messages directly in Slack, which teammates can view at their convenience."

Starting a Huddle (C) is synchronous and not asynchronous. Recording outside Slack (B) and importing is less efficient. Public channels limited to specific workspaces (D) won’t reach the entire org unless users join manually.

(Reference: Slack Administration Study Guide - Using Clips for Asynchronous Communication)

===========

—

Slack's best practice for maintaining security is:

"Deploy the Slack desktop app to users and allow automatic updates to ensure that users are always running the latest, most secure version."

Disabling updates (Option B) would increase security risks. Browser usage alone (Option A) is insufficient for a full Slack experience, and Option D relies too much on user compliance instead of ensuring deployment at scale.

(Reference: Slack Administration Study Guide - Deployment and Security Best Practices)

===========

—

Slack recommends:

"Before finalizing your Enterprise Grid design, survey teams to understand how they collaborate, where informal knowledge networks exist, and what natural groupings of people and work already exist."

Migrating before design (A) is premature. SSO review (C) is important but unrelated to channel and workspace structure design. Champions networks (D) are helpful for rollout, but not initial design.

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

===========

—

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)