Skip to main content
Marketing content rarely ships without at least three sets of eyes on it — founder, marketer, SEO, legal. Without structure, that turns into email chains and “final_v3_ACTUAL.docx”. The Content module gives you proper review, comments, versioning, and approvals in one place.
Path: Marketing > Content

​
Why Use Content Reviews

Keeps versions straight

Every save is a version you can compare or restore

Ends the email chain

Comments live on the content, threaded and resolvable

​
Pipeline Stages

Every piece of content moves through four stages:
  1. Draft — owner writes and edits freely, no reviewers notified
  2. In Review — reviewers assigned, comments and approvals collected
  3. Approved — all required reviewers approved, ready to publish
  4. Published — live on your site
You can customize the stages per workspace, but the default covers most teams.

​
Creating Content

1

Open Content

Go to Marketing > Content.
2

Click + New

Pick a type — blog post, landing page copy, email, case study, social post. Each type has its own template and metadata fields.
3

Fill in the essentials

Title, slug (if applicable), target audience, target keyword (for SEO content), author. These populate the final published version and inform any SEO checks.
4

Write the draft

Rich text editor with markdown shortcuts, images, embeds, AI writing assistance. Save frequently — every save creates a version you can roll back to.

​
Requesting a Review

1

Click Request Review

Top-right of the document. The stage changes from Draft to In Review.
2

Assign reviewers

Pick team members. Mark any as Required — the piece can’t move to Approved until required reviewers sign off.
3

Add a note (optional)

Context for reviewers: “SEO review only please” or “Legal: check the claims in paragraph 3”.
4

Send

Reviewers receive notification (email + in-app). They can open the doc with a single click.

​
Leaving Feedback

Reviewers work inline, not in a separate doc.
1

Highlight the text

Select any word, phrase, or paragraph.
2

Click Comment

A comment thread pins to that text. Type your note.
3

Optionally @mention

@Abe notifies that specific person. Useful for questions: “@Abe is the pricing on this correct?”
4

Resolve when addressed

Once the author makes the change, either the author or the reviewer can mark the thread Resolved. Resolved threads collapse but remain visible for audit.

​
Approvals

1

Review all comments

Reviewers click through each pinned comment, reading context and making sure nothing was missed.
2

Approve or Request Changes

Top-right buttons. Request Changes sends it back to the author with a required note.
3

All required approvals complete

Status automatically moves to Approved. The author gets notified.

​
Publishing

From Approved, click Publish. The content pushes to your site. Blog posts appear at /blog/<slug>, landing pages deploy as configured. If you need to update published content, edit it and re-publish — versioning tracks the published history separately from the draft history.

​
Version History

Every save is a version. To review or restore:
  1. Click the Version icon (clock) in the document header
  2. Browse versions with timestamp, author, and change summary
  3. Compare any two versions side-by-side
  4. Restore any prior version as the current draft
Very old versions (beyond 12 months) may be archived to cold storage. Contact support to retrieve archived versions — usually available within 24 hours.

​
Images, Files, and Tags

  • Images — drag-drop into the editor, stored in your project’s asset library, auto-optimized for web
  • File attachments — PDFs, videos, decks. Referenced in the doc or kept as metadata.
  • Tags — organize by category, campaign, channel. Filter the dashboard by any tag.

​
Roles

Each piece of content has defined roles:
  • Owner — writes, edits, manages the review
  • Editor — can modify draft but not publish
  • Reviewer — comments and approves, can’t modify
  • Observer — read-only access
Set roles per document, or use workspace defaults (e.g., “everyone in the Marketing group is Editor on all content”).

​
Useful Dashboard Filters

  • My drafts — everything you own that’s still in Draft
  • Awaiting my review — requests sent to you
  • Recently published — last 30 days of live content, for stakeholder updates
  • Overdue — in-review pieces that have been sitting too long
Standardize your review process and write it down. “SEO reviews all posts, legal reviews any health/finance claims, founder reviews anything about pricing or positioning.” Put it in a team doc so expectations are clear.

​
Verify It Worked

Create a test doc. Request review on a teammate. Have them leave one comment, resolve it, and approve. Confirm status moves to Approved. Publish and check the content is live.

​
Troubleshooting

Check that reviewers have verified email addresses in their workspace profile. Also confirm workspace notification settings aren’t suppressing content review emails at the user level.
Browser tab may have lost connection. Refresh the page — unsaved comments appear in a recovery draft in the bottom-right. Recover and resubmit.
Versions older than 12 months may be archived. Check the Archived versions link in the version panel, or contact support to retrieve a specific timestamp.
You have to be in the reviewer list set by the person who requested the review. If you’re not, ask them to add you via Edit review in the document sidebar.
Your site may be caching aggressively. Check the Deploy Site guide — you may need to trigger a redeploy to bust the cache for the updated page.

​
What’s Next?

Post a Blog

Walk through publishing a blog post end-to-end

Brand Guide

Lock in consistent voice, tone, and style