Use project views

Views show the same project canvases

Project views are different ways to inspect the same project canvases. Switching from Dashboard to List, Calendar, Kanban, or Timeline does not create separate copies of the work. A canvas stays the same canvas; the view changes how you read it, edit it, and spot what needs attention.

Use the view that matches the question you are asking:

For project basics, see Understand projects. For Dashboard details, see Project Dashboard and progress. For canvas-specific organization, see Manage canvases in projects.

Switch views

Open a project, then use the view tabs near the top of the project. Project detail supports these view-mode shortcuts when the project chrome is active:

These are plain-key shortcuts. They do not run when you are typing in an input, using an open menu, or pressing a modified shortcut such as Cmd+L, Ctrl+L, Alt+T, or Shift+C. That keeps browser and app shortcuts available.

Dashboard is a summary view, so it does not show the project search, sort, filter, or canvas-open settings row. Calendar shows search and filters but not sort. List, Kanban, and Timeline use view-specific search, filter, sort, and open-behavior controls when your role allows them.

Project progress

Project progress is based on canvases counted against sections marked as complete. A canvas counts as complete when it sits in a completion section, such as Done, Approved, Published, or another section your team marks as complete.

Progress is not based on the canvas name, project status, due date, or whether every canvas subtask is complete. Canvas subtasks are a separate signal. Dashboard uses them in KPI cards, subtask progress, sorting, and risk signals, but subtasks do not make the whole canvas complete unless the canvas is also in a completion section.

This distinction matters because Dashboard, progress cards, completed and remaining canvas counts, and burndown history all depend on completion sections. If Review is marked complete, every canvas in Review will be counted as complete. If Done is not marked complete, finished canvases in Done will still read as incomplete.

Open a section or Kanban column menu to mark a section as complete or not complete when your role allows section changes. These section completion settings are part of the project workflow, not decoration.

Confirm the setting when:

• you rename sections
• you build a custom workflow
• a new project starts with the final section already marked as complete

Marking completion sections later is still useful. ALLO can immediately count existing canvases in those sections as complete and use available section-movement history to make progress and burndown history meaningful for the project.

Project Dashboard view

Project Dashboard is the project health view. Use it when you need to answer "are we moving?", "what changed?", "what is late?", and "where are the risks?"

Dashboard includes project progress, total canvases, overdue canvases, canvas subtask counts, burndown, section distribution, workload, canvas tag distribution, top risks, and project history. On wider screens, history appears as a side rail. On smaller screens, it appears below the dashboard cards.

Use Dashboard during weekly review, launch readiness checks, client delivery review, and project cleanup. If the progress number looks wrong, check completion sections first. If the burndown chart looks flat or empty, confirm that canvases have moved into sections marked complete and that the project has enough history to chart.

Dashboard summarizes the whole project. Use List, Calendar, Kanban, or Timeline when you need to inspect one filtered owner, tag, section, or date range.

List view

List view is the best place to clean up project data. It groups canvases by section and lets you scan names, assignees, collaborators, due dates, tags, and, on wide screens, created and modified dates.

Use List when you need to add several canvases, fix inconsistent names, compare owners, update dates, apply tags, expand child canvases, or move canvases between sections. Inline canvas creation keeps the new canvas in the section where you add it.

List is also the clearest place to audit completion sections. If the Dashboard progress feels off, switch to List and check which canvases are sitting in sections marked complete.

If manual ordering does not behave as expected, check sort. Active sorting changes the visible order, so clear sort when you want to drag canvases into a manual order. Cross-section moves can still be useful because they change the canvas section, not just row order.

Calendar view

Calendar view shows dated canvases in month, week, or day mode. It is strongest for launches, content schedules, review windows, events, client deadlines, and recurring handoffs.

Canvases without dates may not appear on Calendar. That does not mean they are gone. Switch to List or Kanban, clear filters, and add dates where timing matters. See Use a project calendar.

When your role allows creation, select a date, date range, or time slot to create a canvas inline. Dragging or resizing a calendar item updates the canvas dates when your role allows edits. Use this for real schedule changes, not placeholder dates that make the calendar look busy without helping anyone decide what to do.

Project Calendar is not Workspace Calendar. Use Workspace Calendar when you want source filters, Google Calendar events, OKR Sessions, and dated work from several projects in one place.

Kanban view

Kanban view shows project sections as columns. Use it when the main question is workflow stage: Planning, Design, Review, Approved, Published, or whatever stages your team actually uses.

Move canvases between columns as work changes. This keeps Dashboard progress honest when your completion sections are configured correctly. Kanban is useful in standups and review meetings because bottlenecks are visible without opening every canvas.

Keep section names tied to real decisions. A column named Later can be useful if it has a clear owner and review habit. A column named Misc usually means the project needs cleanup.

Timeline view

Timeline view shows dated canvases across time. It is useful when duration matters more than a single due date: a launch phase, content production window, client review period, or multi-day workshop plan.

Timeline can group lanes by section or assignee. Dragging or resizing a timeline bar updates the canvas date range when your role allows edits. Moving a bar between lanes can update the section or assignee, depending on the grouping mode.

Canvases need an end date to appear on Timeline. If a canvas is missing there, check its dates first, then clear search and filters.

Search, filters, tags, and sort

Search, filters, and sort can make a view show only part of the project. That is useful, but it is also the first thing to check when a canvas seems missing.

Common filters include assignee, tags, due date, section, and search text. A filter for one teammate hides everyone else. A tag filter hides untagged canvases. A date filter hides work outside the range.

Sort options differ by view. List and Kanban focus on canvas fields such as name, assignee, due date, tags, and sometimes audit or canvas-subtask progress fields. Timeline focuses on section and assignee grouping. Calendar is already date-shaped, so it does not use the same sort menu.

For filter behavior, see Use tags and filters. For project canvas tags, see Manage canvas tags.

Canvas hierarchy and sub-canvases

Project views organize project canvases. A canvas can also contain deeper work, child canvases, or canvas subtasks, depending on how the work was created.

Use sub-canvases when a canvas needs a focused child workspace inside the visual canvas itself. For example, a launch planning canvas might contain sub-canvases for pricing research, risk analysis, or campaign review. See Use sub-canvases.

Use canvas subtasks for follow-up items that belong inside one canvas. Treat them as a local signal for that canvas, not as the project completion rule. The project completion rule still comes from sections marked complete.

Examples

For a launch project, use Dashboard for readiness, Kanban for stage review, List for owner and tag cleanup, Calendar for launch-week pressure, and Timeline for work that spans multiple days. Mark Approved, Ready, or Launched as completion sections only if those sections truly mean the canvas is done.

For a content calendar, use Calendar for publish dates, Kanban for editorial stages, List for titles and owners, and Dashboard for overdue canvases and canvas-subtask progress. Use tags for channel, region, content type, or risk.

For a client project, use List for deliverables, Kanban for review state, Timeline for multi-day review windows, and Dashboard before a status meeting. If the client can open the project but not a specific canvas, check canvas sharing separately from project access.

If a view looks empty

Clear filters, search terms, and date ranges. Switch to another view. Check whether the canvas is in a different section, Kanban column, Calendar date, or Timeline range. Then confirm you are in the correct project and workspace.

If Dashboard progress looks wrong, check which sections are marked complete. If Calendar or Timeline looks empty, check project canvas dates. If List or Kanban looks empty, check search, filters, and permissions.

If a canvas is missing across every view, it may have been moved, deleted, archived, or hidden by access. Check Trash, Search across ALLO, and When work looks missing.