Loading tutorials…
Loading tutorials…
A new Slack workspace looks free and easy. Six months in, you have 180 channels, DM-based decisions no one can search, and a $50/user bill no one approved. Here is how to start it the way marketing-ops teams that have done it three times before would.
Who this is forMarketing leaders and founders standing up Slack for a 5-50 person marketing team (or a team that will be that size in 12 months). If you already have a chaotic workspace, this also doubles as the rebuild blueprint.
What you'll need
Step 1
The plan choice locks in message history, integrations, and Slack AI access. Pro is the floor for any team that uses Slack as a system of record.
Open slack.com/pricing. The four real choices: Free (90 days of history, 10 integrations), Pro ($8.75/user/mo — unlimited history + unlimited integrations + Workflow Builder), Business+ ($15/user/mo — SSO, compliance exports, Slack AI add-on), and Enterprise Grid (custom, multi-workspace org).
For a marketing team that wants Slack as the searchable record of decisions and assets, Pro is the floor. The 90-day cap on Free will silently delete every onboarding doc, brief, and decision rationale older than three months.
Slack AI (channel recaps, search summaries, thread summaries) is an add-on at $10/user/mo on top of any plan. It is genuinely useful at 15+ people. Below that, you can skip until you feel the search pain.
Set up billing on annual if you have the cash flow — it is ~15% cheaper and you avoid the per-invite surprise on monthly billing.
Step 2
Open Slack → workspace name dropdown → Settings & administration → Workspace settings. Set name, default channels, and join restrictions before inviting anyone.
In slack.com, click "Create a workspace" → enter your company name → pick the email domain that should auto-join (e.g., @yourcompany.com).
Once in, click your workspace name (top left) → Settings & administration → Workspace settings.
Set the workspace name to match your company brand exactly. This appears in every notification and shared link.
Under "Permissions" → "Invitations," restrict who can invite Guests and Multi-Channel Guests. Default everyone-can-invite is fine for small teams; restrict to admins once you cross 15 people.
Under "Permissions" → "Channel management," restrict channel creation to Workspace Admins for the first 90 days. This is the single most effective governance lever. Loosen later if it slows the team down.
Under "Authentication," enable 2FA enforcement for all members. Marketing workspaces have CRM tokens, ad-account access, and client data flowing through them — 2FA is not optional.
Step 3
Decide on a naming convention and a category structure. The pattern that survives team growth: prefix-based categories (#team-, #project-, #client-, #ops-).
Pick a prefix system. The pattern that works at scale: #team-* (functional teams), #project-* (named projects with end dates), #client-* (external client channels), #ops-* (recurring ops — reporting, standups, alerts), #social-* (off-topic, watercooler), #help-* (cross-team support).
Document the convention in a Canvas attached to #general (more on Canvas in step 5).
Create the starter set: #general (everyone), #announcements (broadcast-only, admin-posts), #random (off-topic), #team-marketing, #ops-standups, #ops-reporting, #help-marketing.
For each starter channel, set a purpose AND a topic. Purpose answers "what is this channel for?" Topic answers "what is happening here right now?" Most teams skip Purpose and it costs them six months later when new hires cannot tell channels apart.
Star the 3-5 channels that everyone should always see. New members will mirror what they see starred.
Step 4
Invite admins and leads first (ring 1), let them validate the architecture, then invite the rest (ring 2). External guests come last (ring 3).
Ring 1 — workspace admins (1-3 people). Click your workspace name → Invite people to [workspace]. Invite as "Workspace Admins." These people can change settings; everyone else cannot.
Ring 2 — the rest of the internal team. Invite as "Members" (regular). Provide a short Loom or written onboarding doc (we will build this as a Canvas in step 5) explaining channel conventions before they join.
Ring 3 — external guests. These are Multi-Channel Guests ($8.75/user/mo on Pro, counted toward your billable seats) or Single-Channel Guests (free on Pro — limited to one channel, perfect for client-* channels).
For client channels specifically, use Single-Channel Guest for the client and add internal team as regular members. This keeps client billing free and isolates them to that one channel.
Step 5
A Canvas is a Slack-native doc. Create one explaining the channel convention, naming rules, and "how we work in Slack" — pin it to #general.
In #general, click the "+" button next to the message box → Canvas → New canvas (or click the Canvas tab at the top of the channel).
Title it "How we use Slack at [Company]."
Sections to include: (1) Channel conventions and prefixes, (2) When to DM vs post in a channel (default to channel), (3) Threads — when to start one and when not to, (4) Status / Do Not Disturb norms, (5) Tagging — when to @here vs @channel vs @person, (6) Emoji reactions as ack (the :eyes: / :white_check_mark: pattern).
Pin the Canvas to #general — click the three-dot menu on the Canvas → "Pin to channel."
Every new hire onboarding doc should link to this Canvas. It becomes the single source of truth for "how we Slack here."
Step 6
Open Slack → workspace name → Settings & administration → Workspace settings → Notifications. Set sane defaults so new members do not get a notification firehose.
Under Workspace settings → "Default notification preferences," set "Notify me about" to "Direct messages, mentions & keywords" (not "All new messages").
Set a workspace-wide Do Not Disturb schedule (e.g., 7pm-8am local time). Members can override individually but defaults matter for the people who never touch settings.
Configure "Use different settings on your mobile devices" — usually mobile should be "Mentions & DMs only" to prevent badge fatigue.
For each Channel Admin, set channel-level notification defaults: #announcements = "Every new message," #social-random = "Nothing," #ops-* = "Mentions only."
Step 7
Tight governance for the first 30 days, then review. Open up channel creation, prune unused channels, gather feedback.
On day 30, run a workspace audit. Slack → workspace name → Tools → Analytics → Workspace activity.
Look at: most-active channels (good — these are real), least-active channels (archive any with <3 messages over 14 days), most-DMd people (consider: is there a missing channel here?).
Open up channel creation to all Members once you are confident the convention has stuck. Workspace settings → Permissions → Channel management → "Everyone can create channels."
Schedule a quarterly archive sweep — any channel inactive for 60 days gets archived. Archive ≠ delete; the history is preserved and searchable.
Common mistakes
Starting on Free plan with the intent to upgrade later
What goes wrong: Every message older than 90 days is hidden. Onboarding docs, decision rationale, agency briefs — all invisible after 3 months. You upgrade in month 4 and the history reappears, but the team has already moved important context elsewhere. ~30% knowledge searchability lost.
How to avoid: Start on Pro. $8.75/user/mo for a 10-person team is $87.50/mo — less than the cost of one repeated conversation that should have been searchable.
Letting anyone create channels from day one
What goes wrong: By month 6 you have 200 channels. ~120 are dead. On Pro at $8.75/user/mo for a 25-person team, that's ~$2,625/year for a workspace where nobody can find anything. Channel sprawl directly correlates with DM-based decision-making, which kills searchability.
How to avoid: Restrict channel creation to admins for the first 90 days. Document the prefix convention. Loosen only after the team has internalized the pattern.
No naming convention
What goes wrong: Channels named "marketing", "marketing-team", "marketing-stuff", "mkt-team", "the-marketing-channel" all exist simultaneously. New hires guess wrong, post in the dead one, get ignored. Onboarding time stretches by 2-3 weeks per hire.
How to avoid: Lock a prefix-based convention before anyone joins: #team-*, #project-*, #client-*, #ops-*, #help-*. Document it in a Canvas. Pin to #general.
Channel sprawl with no archive policy
What goes wrong: 200 channels with no archive policy on Pro ($8.75/user/mo for ~25 users) = ~$2,625/yr of governance debt where search returns 40 irrelevant results per query. Slack AI cannot summarize dead channels — it just makes the noise worse.
How to avoid: Quarterly archive sweep. Any channel with <3 messages over 14 days gets archived. Archive preserves history; it just hides the channel from the sidebar.
Treating DMs as the default communication mode
What goes wrong: Important decisions made in DMs are invisible to the rest of the team. Slack AI cannot search DMs you are not in. New hires arrive blind. Decisions get re-litigated. DM-heavy culture loses ~30% of organizational knowledge searchability.
How to avoid: Default to channels. The Canvas norm doc should say it explicitly: "If two people are discussing work, it belongs in a channel, not a DM." Use DMs for personal coordination only.
Skipping 2FA enforcement
What goes wrong: Marketing Slack workspaces have CRM tokens, ad-account access, GA4 links, and client data flowing through them. One compromised account is a full data leak. Average cost of a Slack-originated breach is in the tens of thousands at minimum.
How to avoid: Workspace settings → Authentication → require 2FA for all members. Set a 14-day deadline; Slack will lock out non-compliant members automatically.
Recap
Done — what's next
How to set up Slack channel conventions that survive team growth
Read the next tutorial
Hand it off
Workspace setup is the easy part. Keeping the convention alive as the team grows from 10 to 50 is the work — and most founders do not have time for it. A growth-ops specialist on EverestX will set this up, write the Canvas norms, run the first 90 days of governance, and hand it back when the team owns it. From $14-16/hr — typically a 20-30 hour project, then 2-4 hrs/month of light maintenance.
See specialist rates
Free is fine for a 2-3 person team that uses Slack as a real-time chat tool only. The moment Slack becomes the place where decisions, briefs, and context live, the 90-day history cap on Free silently deletes your institutional knowledge. Pay $8.75/user/mo and keep your history.
One workspace for a team under 100 people. Multiple workspaces only when you need hard data isolation (e.g., regulated industry, M&A in flight). If you are tempted to split workspaces because of channel clutter, the answer is channel governance, not a second workspace.
Use Single-Channel Guests on Pro — they are free and limited to one channel each. Create a #client-acme channel with the agency as a Single-Channel Guest and your internal team as regular members. Do not invite agencies as full Members; you pay per seat and lose data isolation.
Slack Connect lets you create a shared channel between two separate Slack workspaces (e.g., you and a partner agency that also uses Slack). Both organizations pay; the channel lives in both workspaces simultaneously. Use it when the external party has their own active Slack — otherwise use Single-Channel Guests.
Business+ ($15/user/mo) makes sense when you need SAML SSO, compliance exports, or guaranteed uptime SLA — usually around 50+ people. Enterprise Grid is for multi-workspace orgs (separate workspaces per business unit, shared identity layer) — usually 500+ people. Stay on Pro until the upgrade pays for itself in real features used.
Rule of thumb: a healthy workspace has 2-4 channels per active member. A 25-person team is healthy at 50-100 active channels. Past 200 channels for 25 people, search degrades and people start using DMs instead — at which point you have lost the system-of-record benefit of Slack.
Slack
Most Slack workspaces die not from low adoption but from too much adoption with no rules. This walks through the channel-architecture decisions that survive the jump from 10 to 50 people.
Slack
Slack Workflow Builder is the no-code automation tool that's been in Slack since 2019, and most marketing teams have never opened it. Done well, it replaces a quarter of your meetings and most of your DMs to recurring people.
Slack
You have 240 channels. Half are dead, half have unclear names, and search returns 30 irrelevant results per query. Here is the cleanup sequence that does not break the team.