Running several projects at once, every shared view fights itself: one board holding every client's work, one calendar speckled with everything due. The fix isn't a tidier list — it's a view built for one project at a time. This walkthrough tunes two of them, a kanban board and the calendar, so each stops showing you everything and starts answering a single question: what's happening on this project?
If you haven't yet shaped a project's stages and task types, Shape a project's workflow and work it on a board is the companion to this one — that guide defines the workflow; this one aims your views at it.
The goal
Turn "everything, everywhere" into a per-project focus: a board scoped to one project with only the columns and card details it needs, and a calendar showing only that project's chips — each view remembered, so switching projects is switching views.
1. Give each project the statuses and types it needs
Statuses and task types can be project-scoped, not just global. On the task statuses and task types pages you can scope a status or type to specific projects, so a Client review stage or a Design type exists only where it makes sense. This is what lets the rest of this guide be genuinely per-project: a view narrowed to one project can then show just the stages and shapes that belong to it.
Statuses carry flags — finished, backlog, requires action — that views read later, so it's worth setting those as you go (see Custom statuses for what each one does).
2. Build a board scoped to one project
Boards in Ceum are yours and you can keep several — so make one per project rather than sharing a single wall. Create a board from the Kanban boards page, then open its edit page and set three things:
- Project filter — narrow the board to the one project. Now only that project's tasks appear, and the board offers only the statuses and types in scope for it (plus any that apply to all projects).
- Visible columns — a per-board checklist of your enabled statuses. Leave the ones this project moves through and clear the rest, so the board is exactly as wide as the work. Show backlog columns and Show finished columns toggle those special stages independently.
- Card content — switch on just the details that matter here: project breadcrumb, type dot, deadline, description snippet, nested subtasks. A card carrying only what you act on reads faster than one crammed with everything.
The active board sticks per browser, so once you've built a board per project, switching projects is just picking one from the header dropdown.
3. Filter it down further, in the moment
A per-project board is already focused; filters and sorting take it the last step. Narrow to a task type, a tag like urgent, or work due this week — filters combine, so "design tasks in review" is a single view. The board configuration is the permanent shape; the filter is the temporary lens for today's slice.
4. Point the calendar at the same project
The calendar has the same everything-at-once problem, and the same cure. Open Calendar settings and, under Tasks, turn Show all projects off — then a project filter appears where you pick which projects' tasks to include. Choose the one you're focused on and the grid drops every other project's chips; your picks show as removable tags, so widening back out is one click.
A few nearby controls make the view yours:
- Include tasks without a project — keep loose tasks visible, or hide them to see only project work.
- Per-kind toggles and colors — tasks, custom events, and subscription renewals each have their own on/off switch and color, and tasks can be tinted by their task type's color. Turn off what you don't need this week.
Now the same project reads two ways: the board for where each task stands, the calendar for when it's due — both showing only that project, nothing else.
What you end up with
One project, two focused views: a board with just its columns, cards, and tasks, and a calendar with just its chips. Because both remember their settings, keeping a board and a calendar filter per project turns "which of these twelve things is about this client?" into simply opening the view you already built.