Loading tutorials…
Loading tutorials…
Slack Canvas (launched 2023) and Slack Lists (launched 2024) closed two gaps that used to push teams out of Slack: structured docs and project tracking. Used well, they cut your tool count by 1-2 and your context-switching by 30%.
Who this is forMarketing teams already using Slack who currently jump to Notion, Google Docs, or a project tool for every brief, tracker, or doc. Canvas and Lists can absorb some of that work — but not all.
What you'll need
Step 1
Canvas = lightweight in-channel doc. Lists = structured project tracker. Notion/Docs = deep documents with rich linking. Pick by use case, not preference.
Canvas: a doc attached to a channel or a DM. Rich-text, headings, embedded Slack messages, mentions, file embeds. Good for: channel norms, brief templates, meeting notes, decision logs, onboarding docs that live next to the team's conversation.
Lists: a structured table inside Slack. Columns are fields (text, dropdown, person, date, number). Rows are records. Good for: content calendars, campaign trackers, request queues, lightweight project boards.
External docs (Notion, Google Docs, Confluence): deep documents with rich linking, version history, complex formatting. Good for: strategy docs, long-form research, formal SOPs, anything that needs to be referenced from outside Slack.
Rule of thumb: if the doc lives next to a Slack conversation and is referenced primarily by Slack channel members, use Canvas. If it lives across the org and is referenced from many tools, use Notion or Google Docs.
Step 2
Open #general → click the + next to the message box → Canvas → New canvas. Title it "How we work in [Team]" and pin to the channel.
In #general, click the '+' next to the message box → Canvas → New canvas. (Or click the Canvas tab at the top of the channel.)
Title: "How we work in [Marketing/Company].",
Sections: (1) Channel conventions and prefixes, (2) When to DM vs post in channel, (3) Thread etiquette, (4) Workflow Builder shortcuts, (5) Integration channels and what they post, (6) Owner and escalation path.
Use the format options at the top: headings, bullets, callouts, embedded files, @mentions.
Pin the Canvas to #general — click the three-dot menu on the Canvas → "Pin to channel."
Every new hire should be pointed at this Canvas during onboarding. It becomes the single source of truth for "how we Slack here."
Step 3
Each #project-* channel gets a Canvas with the project brief, owner, timeline, and key decisions log.
In each #project-* channel, create a Canvas titled "[Project name] — brief & decisions."
Sections: (1) Project goal in one sentence, (2) Owner and contributors, (3) Timeline (start, milestones, end), (4) Key resources (links to deep docs in Notion or Google Drive), (5) Decisions log (running list with date, decision, rationale).
Pin the Canvas. New members joining the channel can read it before scrolling 2 weeks of channel history.
The decisions log is the highest-value part. Every time the team makes a non-trivial decision in the channel, the owner appends to the decisions log with date + one-line summary.
Step 4
Slack → workspace sidebar → "Later" or "More" → "Lists" → "New List" → "From scratch." Build columns for the content calendar.
In the Slack sidebar, click "More" or scroll to find "Lists." If you do not see it, your workspace might need Lists enabled by an admin (Slack → workspace name → Tools & settings → Manage apps).
Click 'New List' → 'From scratch' (or use a template — Slack ships several marketing templates).
Columns for a content calendar: Title (text), Status (dropdown: Idea / Drafting / Review / Scheduled / Published), Author (person), Publish date (date), Channel (dropdown: Blog / Newsletter / Social / Email), Word count (number), Link (URL).
Add records for current content backlog. Group by Status (toggle in List view).
Connect to a channel: click "Share" on the List → "Share to channel" → #team-content. Now any channel member can update the List inline.
Step 5
Pair this with the request-intake workflow from tutorial 3 — workflow submissions add rows to the List automatically.
Create a new List: 'Marketing requests — Q2 2026.'
Columns: Request title (text), Requestor (person), Request type (dropdown), Deadline (date), Status (dropdown: New / In progress / Blocked / Done), Owner (person), Notes (long text).
Connect to Workflow Builder: in your request-intake workflow (tutorial 3), add a final step "Add row to List" and map the form fields to the List columns.
Now every form submission creates a row. The marketing lead works the List instead of scrolling channel history. Status updates happen inline — no separate project tool needed for lightweight intake.
Step 6
On Slack AI ($10/user/mo), you can ask "summarize this Canvas" or get auto-recaps of List changes. Saves the manual "what changed this week" review.
In any Canvas or List, click the sparkle icon to invoke Slack AI.
For Canvas: 'Summarize this Canvas' or 'What decisions were made this week?' Pulls from the decisions log + the channel context.
For Lists: 'Show me all rows changed this week' or 'Which rows are blocked?' Returns a summary inline.
Especially useful for project channels where the Canvas decisions log is the canonical record. Slack AI can pull weekly summaries that you paste into a team digest.
Step 7
After 30 days, audit which Canvases are working and which are not. Move long-form documents to Notion; keep in-channel context in Canvas.
Open each Canvas and ask: "Is this primarily referenced by people in this Slack channel?" If yes, keep in Canvas. If it is referenced from 5+ tools, move to Notion or Google Docs.
Pattern: short-form, channel-anchored docs stay in Canvas. Long-form, org-wide docs go to Notion. Each tool plays to its strength.
Same for Lists — keep lightweight queues and calendars in Slack. Anything with >100 active records or complex dependencies belongs in a real project tool (Asana, Monday, ClickUp).
Document the rule in your "How we work" Canvas: "Canvas = in-channel docs. Notion = deep docs. Lists = lightweight queues. Asana = complex project work."
Common mistakes
Trying to replace Notion or Confluence with Canvas
What goes wrong: Three months in, you have 80 Canvases scattered across channels, no cross-doc linking, no real wiki structure. People give up and migrate back to Notion. ~20 hours of migration work wasted. Worse: institutional knowledge fragmented across two systems.
How to avoid: Use Canvas for in-channel docs (norms, briefs, decisions logs). Keep Notion or Confluence for deep org-wide knowledge. Hybrid is the right answer.
Using Lists for complex project management
What goes wrong: You move from Asana to Slack Lists. Past 100 active rows, the lack of dependencies, sub-tasks, and views starts to bite. Team rebuilds the missing features as Canvases and DMs. You end up with worse PM than you started with.
How to avoid: Lists for lightweight queues (content calendar, request intake, simple trackers). Keep Asana/Monday/ClickUp for complex project work.
Canvases with no owner
What goes wrong: Norms doc goes stale because nobody owns updating it. Decisions log stops getting updated because the project owner left. Canvas becomes a museum piece — visible but unreliable. ~$200/mo of opportunity cost on a 10-person team from acting on stale docs.
How to avoid: Every Canvas names an owner in the first section: "Owner: [name] — last reviewed [date]." Quarterly review reminder.
Not pinning the Canvas to the channel
What goes wrong: Canvas exists but nobody can find it. New channel members scroll history looking for context. Onboarding time per new channel member: +30 min wasted.
How to avoid: Pin every channel Canvas. Slack pins are persistent and visible in the channel header — first thing new members see.
Building Lists without connecting to workflows
What goes wrong: The List exists but is manually maintained. Half the rows are stale, half are missing. The team stops trusting it within a month. Manual data entry kills any structured-data system.
How to avoid: Connect every List to a Workflow Builder workflow that adds rows automatically. Lists work when they are the output of a workflow, not the input of manual data entry.
Putting sensitive data in Canvas
What goes wrong: Canvas is visible to all channel members. Putting client comp data, financial details, or HR-sensitive content in a public channel Canvas exposes it broadly. Single incident can cost an organization $10K-$50K in mitigation if it's regulated data.
How to avoid: Sensitive data lives in private channels or, better, in Notion/Google Docs with explicit access control. Canvas is for non-sensitive in-channel context.
Recap
Done — what's next
How to set up Slack Workflow Builder for marketing teams
Read the next tutorial
Hand it off
Picking what lives in Slack (Canvas, Lists) vs. external tools (Notion, Google Docs, Asana) is the kind of architecture decision that compounds for years. A growth-ops specialist on EverestX will map your current tool sprawl, pick the right home for each artifact, and migrate the high-value stuff. Typically 12-20 hours at $14-16/hr.
See specialist rates
No, and it does not try to be. Canvas is purpose-built for in-channel context — short, focused, anchored to a conversation. Notion is purpose-built for deep, nested, cross-linked knowledge. Use both.
Yes, Lists is included on Pro ($8.75/user/mo) and above. Free plan does not have Lists. You also need Lists enabled at the workspace level — Slack → Manage apps → Lists.
Yes, you can copy the contents and paste elsewhere, but there's no native 'export to Word/PDF' on the free Pro plan. On Business+ and above, you can export workspace content including Canvases for compliance.
Airtable is far more powerful — multiple views (calendar, kanban, gallery), formulas, automations, linked records. Lists is intentionally simpler. Use Lists for in-Slack lightweight tracking. Use Airtable when you need real database power.
Yes on Pro and above — Canvas → three-dot menu → 'Share externally' generates a public link or invites specific email addresses. Be careful: external sharing exposes Canvas content beyond your workspace.
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
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.