How many custom statuses can I create?

There's no hard limit. Most teams have 4-8 statuses covering their entire document lifecycle. Too many can be overwhelming, so we recommend starting simple and adding more as needed.

Can I use emoji in status names?

Yes! Emojis help distinguish statuses at a glance. Put the emoji at the start of the name (e.g., '📝 Draft', '✅ Approved'). They appear in document headers, Kanban cards, and filter dropdowns.

Do statuses integrate with Kanban view?

Directly. Each status becomes a column in Kanban view. The column order matches your status order in settings. Drag documents between columns to change their status.

Can I set a default status for new documents?

Yes. In Status settings, mark one status as the default. All new documents automatically start with this status. Most teams use 'Draft' or 'Idea' as the default.

Can I trigger automations when status changes?

Yes. The visual workflow builder can trigger on status changes. Examples: 'When status changes to Published, send webhook to CMS' or 'When status is Archived for 30 days, notify admin'.

What happens if I delete a status that documents are using?

You'll be prompted to choose a replacement status for those documents. We won't let you leave documents in limbo. All affected documents will be moved to the status you choose.

Workflow Feature

Your workflow,your statuses

Every team works differently. Define custom statuses that match your actual process, from first idea to final publication to archive.

Try it free See all features

Example status workflow

Create statuses that match YOUR workflow. These are just examples.

💡 Idea

Initial concept, not yet started

📝 Draft

Work in progress

👀 In Review

Waiting for feedback

⚖️ Legal Review

With legal team

✅ Approved

Ready for next step

📅 Scheduled

Queued for publishing

🚀 Published

Live and public

📦 Archived

Completed, filed away

Why custom statuses matter

Fixed status options

•'Draft' and 'Final' only. What about Review? Legal?
•Using folders or tags to fake statuses as workarounds
•All statuses look the same in lists, no visual distinction
•Process mismatch: tool doesn't fit how your team works

Custom statuses in WURDX

•Define exactly what you need: Idea, Draft, Legal Review, Approved
•First-class feature: statuses appear everywhere
•Colors & emojis for visual distinction at a glance
•Configure WURDX to work the way you actually work

Every team works differently

WURDX doesn't force a process on you. Here's how different teams set up their status workflows.

📣

Marketing & Content

Idea→Drafting→In Review→Approved→Scheduled→Published

Content moves from idea to published. Webhooks notify Slack and CMS when something hits 'Approved'.

⚖️

Legal & Compliance

Draft→Internal Review→Legal Review→Exec Sign-off→Current→Deprecated

Policies need multiple review gates. Admin-only transitions on 'Current' and 'Deprecated' prevent unauthorized changes.

⚙️

Engineering

RFC Draft→Eng Review→Accepted→In Development→Shipped

RFCs and design docs follow the eng lifecycle. Status changes trigger Linear/Jira webhook updates.

Statuses power everything

Kanban columns

Each status = a column. Drag to change.

Filtering

'Show all In Review' in one click.

Workflow builder

Trigger webhooks on status change.

Frequently asked questions

Kanban View Visual Workflow Builder SOP Documentation Content Teams

Ready to define your workflow?

Start with default statuses, customize when you're ready.

Get started free See pricing