Custom Boards How to build a board for work that has no home in the standard areas, using the four-step wizard.

Operations, Data, Custom Boards. Build a board for a process the platform does not ship with. You need the internal operations capability.

Use one when work is real, recurring, and has no natural home - vendor onboarding, an office move, an audit programme. Do not use one for work that belongs in an existing area; a deal belongs on a pipeline, an issue belongs in Projects.

The Wizard

Four steps.

1. HQ Module. Which area this board belongs to - People, Engineering, Operations, Finance, Marketing, Support or Documents. This decides where it appears and who reaches it.
2. Purpose. What the board is for. Templates are offered per area - recruitment and training for People, bugs and releases for Engineering, projects and vendors for Operations, audits and budgets for Finance, campaigns and content for Marketing, escalations for Support, reviews and approvals for Documents.
3. Configure. Name the board and define its stages - the columns work moves through.
4. Fields. What each card carries, and which fields show on the card face.

Designing The Stages

Stages are the spine. Two rules:

• Name them for the state the work is in, not the action someone takes. "Awaiting vendor" beats "Chase vendor" - it stays true while nobody is doing anything.
• Keep it to five or six. More columns than fit on screen means dragging across a scroll, and people stop moving cards. If you need more granularity, add a field rather than a column.

Card Fields

Only put on the card what someone needs to triage without opening it - usually owner, a date, and one status. Everything else lives inside the record.

Custom fields on a board can be scoped to that view alone, so a board's fields do not appear anywhere else. See Custom Fields.

Views

A board can be worked as a kanban or as a table. Kanban is right when the flow between stages is the point; table is right when you are comparing rows on their values.

Common Questions

Can automations run on a custom board? Board events are part of the event catalogue, so a workflow can trigger on them. Check the exact event in the trigger picker.

Who can see the board? It follows the area you assigned it to in step one. Choose that deliberately - it is the access decision.

Can I change stages after cards exist? Yes, but cards in a stage you remove need somewhere to go. Move them first.

Board or pipeline? A pipeline is for revenue with stages, probability and forecasting. A board is for process without money attached. If you are tracking value and a close date, use a pipeline.