# Channel naming conventions: prefixes and qualifiers

*Slack Consultant Study Guide · Channel Strategy · Last updated October 21, 2026 · https://www.certifyforce.com/study-guide/slack-consultant/channel-strategy/channel-naming-conventions-prefixes-and-qualifiers*

Why a channel naming convention matters, the channel name rules, the prefix-plus-qualifier formula with a dash delimiter, workspace channel prefixes, how to publish the standard, and naming your side of a Slack Connect channel.

- Certification: Salesforce Slack Consultant
- Exam section: Channel Strategy
- Study guide: https://www.certifyforce.com/study-guide/slack-consultant

**Official exam objective:**

> Educate your client on the purpose and importance of a channel naming convention.

## What the exam expects

- Explain to a client what a naming convention achieves (findability, fewer duplicates, an organized sidebar) and what it does not do (privacy, retention, posting control).
- Apply the channel name rules and the recommended dash delimiter to judge a proposed name.
- Build names from a prefix that states purpose and a qualifier that makes the channel distinct, and pick the right prefix for a purpose.
- Recommend one consistent company-wide formula even when it departs from Slack's example prefixes, and say where to publish it.
- Name your organization's side of a Slack Connect channel by your own convention.

Key terms:
- **Naming convention:** the agreed formula every channel name follows.
- **Prefix:** the first part of a name, denoting the channel's purpose (help-, proj-, team-).
- **Qualifier:** the part after the prefix that makes the channel distinct (department, location, client, project, service).
- **Delimiter:** the character between parts of a name; Slack recommends a dash.
- **Channel prefix setting:** a workspace list of prefixes members pick from when creating a channel.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Name length | Up to 80 characters | [Create channels with purpose](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose) |
| Allowed characters | Lowercase letters, numbers, dashes, underscores | [Create channels with purpose](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose) |
| Recommended delimiter | Dash, not underscore | [Create channels with purpose](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose) |
| Formula | Prefix (purpose) + qualifier (distinction) | [Create channels with purpose](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose) |
| External channels | ext- prefix for Slack Connect collaboration | [Create channels with purpose](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose) |
| Where to publish | Pin the standard in #help-slack and main announcement channels | [Create channels with purpose](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose), [How to organize your Slack channels](https://slack.com/resources/using-slack/how-to-organize-your-slack-channels) |
| Default prefixes | #help, #proj, #team; Workspace Owners and Admins add more | [Create channel prefixes](https://slack.com/help/articles/360033618294-Create-channel-prefixes-for-your-workspace) |
| Prefix limits | Free 6; Pro and Business+ 99; 99 per Enterprise org workspace | [Create channel prefixes](https://slack.com/help/articles/360033618294-Create-channel-prefixes-for-your-workspace) |
| Shared channel names | Each side sets its own name | [How to organize your Slack channels](https://slack.com/resources/using-slack/how-to-organize-your-slack-channels) |

## Check yourself

- Why does a channel naming convention matter to end users?
- What do the prefix and the qualifier each contribute to a channel name?
- When is a location-first naming pattern acceptable?
- Why can your organization use its ext- prefix on a channel a partner created?
- How many channel prefixes can a Free workspace have?

## Sources

- [Streamline Slack Channel Creation for Better Collaboration](https://trailhead.salesforce.com/content/learn/modules/slack-channel-strategy-basics/create-channels-with-purpose)
- [Create guidelines for channel names](https://slack.com/help/articles/217626408-Create-guidelines-for-channel-names)
- [How to organize your Slack channels](https://slack.com/resources/using-slack/how-to-organize-your-slack-channels)
- [Create channel prefixes for your workspace](https://slack.com/help/articles/360033618294-Create-channel-prefixes-for-your-workspace)
- [Bring Slack-First Thinking to Your Sales Team](https://trailhead.salesforce.com/content/learn/modules/slack-first-sales/create-a-plan-to-bring-slack-first-thinking-to-your-sales-team)
- [What is a channel?](https://slack.com/help/articles/360017938993)
- [Create a channel](https://slack.com/help/articles/201402297-Create-a-channel)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the Slack Consultant pack (USD $19): https://www.certifyforce.com/practice-exams