Projects
Boards for work that is not a deal: customer projects, internal initiatives, and the feature-request queue.
By Sebastian StreiffertPublished Jan 10, 2026Updated May 4, 20266 min read
What you can do here
Projects is for work that is not a deal and not a single task: onboarding a customer, shipping an internal initiative, or handling the queue of things people keep asking for.
- Run a customer onboarding with visible steps and an owner on each.
- Collect feature requests somewhere other than a chat channel.
- Triage what comes in weekly instead of letting it pile up.
- Show the team what is being worked on now and what is not.
Export to CSV
SSO for Northwind
Fix invoice totals
Import mapping
- 1Columns: Yours to name; the template sets the first ones
- 2Cards: Priority, assignees, deadline, comments
- 3Drag: Move a card and its status follows
The section
| Page | What is on it |
|---|---|
| Overview | Recent projects, and what needs attention: untriaged, blocked, and overdue. |
| My Items | Everything assigned to you, across every project. |
| Inbox | New requests waiting for a decision. |
| Roadmap | Requests sorted into Now, Next, Later, and Shipped. |
| Settings | How projects behave across the workspace. |
Start a project
Create it
Projects → New Project. Name it after the outcome, not the department.Pick a template
| Template | Built for |
|---|---|
| Simple Project | General work on a plain board. Start here if you are unsure. |
| Feature Requests | Ideas, customer requests, and bugs, with scoring and a roadmap. |
| Customer Project | Onboarding, implementation, or delivery for one client. |
Add the first items
| Type | Use it for |
|---|---|
| Task | A piece of work to do. |
| Request | Something asked for, not yet decided. |
| Bug | Something broken. |
| Idea | A suggestion worth keeping. |
| Story | A slice of a deliverable, for teams running sprints. |
| Epic | A container for stories. |
What a card carries
A title, status, priority from none through urgent, an owner, assignees, a due date, and a deadline. Cards show small markers for deadlines, attachments, comments, and story points, so you can read the board without opening every card.
Triage what comes in
The Inbox collects things nobody has decided on yet: new requests, and items created from elsewhere in the CRM. Working it means giving each one a project, a type, and a decision.
The four decisions are Build, Later, Decline, and Duplicate. Anything without a decision stays in the Inbox, which is the point: nothing quietly vanishes into a backlog and nobody has to remember it.
Decide what to build next
Feature-request projects let you score items on impact, effort, and confidence, each from 1 to 5. The scores are there to make the argument explicit, not to make the decision for you.
Roadmap sorts scored items into Now, Next, Later, and Shipped. Only items you have put in a bucket appear, so the roadmap stays a statement of intent rather than a dump of everything open.
Share it, and finish it
Who can see a project
Everyone in the workspace, only you, or a named set of people, teams, and roles, each as a viewer or an editor.
Closing one out
Completing a project records who accepted it, a summary, who is picking up support, handoff notes, and a retrospective. A month later that is the difference between a document someone can read and an archived board nobody understands.
When something looks wrong
| What you see | What to do |
|---|---|
| The Inbox keeps growing | Items stay there until they get a decision. Give each one Build, Later, Decline, or Duplicate. |
| The Roadmap is empty | Only items you have moved into a bucket appear. Score them first, then place them. |
| A colleague cannot see the project | Check its access. Private and restricted projects need them added by name. |
| You cannot add an item in list view | Switch to Kanban to add, then go back to list. |
Quick reference
Was this article helpful?