Explore Channel Types
Learning Objectives
After completing this unit, you’ll be able to:
- Explain the different channel types.
- Describe essential channel settings.
There are several types of channels, each with different features to support work in Slack. When creating a channel, consider its purpose, members, and intended audience to choose the right channel type.
Distinguish Between Public and Private Channels
The first distinction to make between channels is whether they are public or private. This determines general visibility and access to the channel.
Identify Public Channels
Any member in a workspace, except for single-channel guests, can view, join, or search a public channel. When creating a new channel, it’s public by default. Public channels are recommended unless there's any information shared that’s intended for a private audience. Anything posted or shared, including files, can be searched for, viewed, and accessed in a public channel. Most importantly, public channels promote transparency, trust, and inclusivity at an organization. Public channels are indicated with a #.
Determine Private Channels
A user must be invited to a private channel by an existing member of that channel. All messages and files shared within that channel can only be searched for, viewed, or accessed by members of that channel.
Private channels are recommended for when information is going to be shared that should not be available to all users, like hiring or budgeting. Private channels are indicated with a padlock symbol.
Additionally, there are other solutions available for setting up channels.
Explore Slack Connect Channels
Slack Connect channels allow you to communicate with users outside your organization, such as vendors and customers, via channels and direct messages (DMs). Slack Connect channels can include users from different organizations, however, invitations need to be sent and approved by each organization’s admin.
Slack Connect is a great option if all organizations are already on Slack. If your client is working with external parties who don't use Slack, that’s OK! Slack Enterprise Grid customers can create sponsored connections where new users don't need to start a Slack free trial and can stay connected in this channel long-term. These can be both public or private.
Find more inspiration for using Slack Connect in the resources below. And if you want to level up your Slack Connect expertise, check out the Slack Connect badge.
Understand Channels Across Workspaces
Channel management also varies based on the workspace and organization configuration. Consider how your client wants to share information across the entire enterprise.
Multi-Workspace Channels
Multi-workspace channels span across multiple workspaces. These channels are a great way to break down communication barriers when your client has multiple workspaces. This way users and teams from different workspaces can come together and collaborate on a project. Also, users from different workspaces get shared updates and announcements in a single channel. In the grid design image, #proj-released, #service-support, and the other channels in yellow are examples of multi-workspace channels shared across several workspaces. Multi-workspace channels can be either public or private.
Org-Wide Channels
Org-wide channels are present in every workspace in the grid, no matter how many workspaces there are. These channels are important for sharing information and collaboration across all workspaces and grid members. An example of this channel might be #announcements-global, where all users can access the channel and view the information shared no matter what workspace they're in.
Org-wide public channels are accessible to every single user in the Enterprise Grid, so you should be thoughtful about recommending certain settings for these org-wide channels. Let’s review the channel settings available.
Configure Channel Settings and Permissions
With each channel configuration, there are a few different settings and permissions needed to best manage member access.
Setting |
Description |
|---|---|
Default |
Org-wide channels can be set as default for the entire organization. This means that all new members are automatically added to these channels when they are added to the grid. |
Required or Optional |
You can set a default channel as required, meaning members can’t leave it, or as optional, allowing them to leave at any time. For example, an #announcements-global channel should be required to keep all employees informed of company news, while a #help-hr channel can be optional for more specific support. |
Posting Permissions |
To keep org-wide channels focused, consider restricting posting permissions to Org Admins or specific individuals. This helps prevent clutter and ensures announcements stay on topic. The same permission controls can be applied to other channels as needed, allowing for customized management across the organization. |
Threading Permissions |
You can restrict posting in announcement channels to keep discussions focused while still allowing members to ask questions through threaded replies. This helps maintain the channel’s purpose while encouraging engagement. |
In this Posting permissions example, Org Admins only is selected, threads and @ mentions are enabled. That means only Org Admins can post, but everyone can reply and @ mention the channel to further the conversation.
We recommend customers start with at least two default channels. Include #announcements-global for companywide updates and #help-slack for slack-related questions and support.
An organization can have up to 25 org-wide default channels and additional default channels for certain workspaces and user groups. Being thoughtful about default channels can improve the onboarding experience and help users feel more connected to other teams.
Now that you know about the different channel types, it’s time to learn how to name them and create new ones with a clear purpose to keep your Slack workspace organized.