Use a consistent naming pattern for Slack channels so people can quickly understand what a channel is for, find the right place to post, and search for older conversations later.
Note: Channel prefixes are recommended, but they are not required. Users can still type any valid channel name they want.
Why Channel Naming Matters
Slack works best when channel names are predictable. A consistent naming pattern makes channels easier to identify, easier to manage, and easier to search.
Slack channel names always begin with a hashtag, and spaces are automatically replaced with hyphens. For example, a channel created with the words project launch appears as #project-launch.
Using standard prefixes also helps users understand the purpose of a channel before they join it. In most cases, the prefix should come first in the channel name.
Recommended Naming Prefixes
Common Internal Prefixes
- #help- for incoming requests and questions for a department
- #team- for ongoing operational communication within a department
- #proj- for time-bound projects, initiatives, or campaigns
- #topic- for general discussion or knowledge sharing
- #announce- for broad announcements and push-based updates
- #event- for internal events or sponsored public events
- #social- for non-work or community channels
Special-Purpose Prefixes
- #ext- or #shared- for channels that include external organizations
- #feed- or #alert- for automated information sources
- #erg- or #sig- for employee resource groups or special interest groups
Location and Region Prefixes
- #office-london- for office-based channels
- #office-nyc-midtown- for office-based channels
- #office-nyc-brooklyn- for office-based channels
- #mkt-apac- for geographic region channels
- #mkt-canada- for geographic region channels
- #mkt-norcal- for geographic region channels
Important: Keep the rest of the channel name short and specific. A good channel name should describe the audience, purpose, or topic without extra words.
Choosing the Right Channel Visibility
Internal Channels
For most internal use cases, the default should be a public channel. Public channels support organizational knowledge by making conversations searchable and available to everyone in the workspace.
Use a private channel when the content needs restricted access, such as hiring discussions, promotion planning, one-to-one check-ins, or projects that require approval to join.
In some cases, sensitive work may be better suited to a separate workspace instead of a private channel.
External Channels
For Slack Connect channels, the default should be private. External conversations are usually relevant to a smaller group and often involve privacy or confidentiality concerns.
Use a public external channel only when the relationship is relevant to most of the organization, when the channel is meant to broadcast information from the external organization, or when the goal is to support networking across organizations.
Note: In a Slack Enterprise Grid environment, shared channels support collaboration between workspaces, while Slack Connect channels are used for collaboration with external organizations.
Default Channel Recommendations
Every Slack workspace includes two default channels. Add a clear topic and description to each one so users understand how to use them.
#general
Consider renaming #general to something more specific, such as #announce-[workspace-name]. This channel is a good place for workspace-wide news, announcements, and other broad updates.
Limit posting as needed and add a welcome message for new users.
#random
Consider renaming #random to something like #social-random-[workspace]. Use it for informal conversation, and add a pinned message or canvas with posting rules if needed.
Help Channels
- #help-slack-community for general how-to questions and advice
- #help-slack-admin for admin-specific requests that should not be posted by general members
Naming Examples
- #proj-new-student-orientation
- #team-oit-support
- #announce-unlv-all
- #topic-ai-tools
- #shared-cyber-evpp-discuss
- #ext-rebel-slalom-project
- #office-nyc-midtown-it
- #mkt-apac-campaigns
Best Practices
- Use one clear purpose per channel.
- Keep names short, specific, and easy to search.
- Use public channels when possible for internal work.
- Use private channels only when the content needs restricted access.
- Use Slack Connect channels only when the channel needs external collaboration.
- Add a channel description and topic to provide extra context.
Need Additional Help?
If you need help choosing a channel name or deciding whether a channel should be public, private, shared, or external, contact the IT Help Desk or submit a ticket through the IT Support Portal.