Organize canvases and sections

Project List is the main place to organize canvases inside a project. It groups canvases into sections, shows project fields such as owner, collaborators, due date, tags, and activity dates, and lets you reshape the project without opening every canvas.

Use it when you need to create several canvases, rename or reorder sections, move canvases between sections, nest a canvas under another canvas, or decide which sections count as completed work.

Work with sections

Sections are project groups such as Planning, Design, Review, Approved, and Published. They keep canvases scannable and define the workflow used by List and other project views.

From a section menu, rename the section, add a section above it, collapse or expand sections, mark the section complete or not complete, move it to another project, copy it to another project, or delete it when your role allows those actions.

You can drag a section header to reorder sections. Project List uses the header position for section reordering, so aim for another section header rather than blank space in the section body.

An empty section is still useful. You can create canvases in it, drag canvases into it, or mark it complete before canvases arrive.

Create canvases in sections

Use the add row or add action in a section to create a canvas in the project. Name the canvas for the work it represents, then add owner, collaborators, due date, and tags where they help the team act.

If you paste several lines into the add row, ALLO can create one canvas for each non-empty line. For example, pasting:

Launch brief
Homepage copy review
Press quote approvals
Release checklist

creates separate project canvases in that section.

Choose the section intentionally. If the section is marked complete, a new top-level canvas in that section counts as completed for Project progress and Dashboard burndown as soon as progress updates.

Drag canvases in Project List

Project List supports several drop targets when the current view and permissions allow dragging.

Dragging a canvas under one of its own descendants is blocked because that would create a loop in the sub-canvas tree.

When an active sort is controlling the visible order, Project List can block same-section manual reorder and parent drops. Cross-section moves can still work because they update the canvas section without promising a manual row order.

For the broader sub-canvas model, see Use sub-canvases.

Mark sections complete for progress

Project progress is based on sections marked complete. Every top-level project canvas in a complete section counts as completed. Top-level canvases outside complete sections count toward the project total but not completed progress.

Dashboard burndown uses the same completion source, so section settings affect both the project progress number and Dashboard progress charts.

More than one section can be marked complete. For example, a project can count both Approved and Published as completed work while leaving Draft, Review, and Blocked incomplete.

You can set this later. If a project already has months of canvases in Approved, marking Approved complete immediately makes that existing section history useful: when Project progress refreshes, top-level canvases already in the section count as completed. You do not need to recreate canvases or move them through the section again.

Canvas subtasks and sub-canvases do not define Project progress. They help organize work inside or under a canvas, but the project completion model counts top-level project canvases by section.

If progress looks wrong, check which sections are marked complete, whether the canvases are top-level project canvases in those sections, and whether the Dashboard or project view has refreshed after recent changes.

Move or copy canvases to another project

Use a canvas menu to move or copy a canvas to another project. Moving changes where the canvas lives. Copying creates a separate canvas in the destination.

Choosing a project as the destination makes the canvas top-level in that project. Choosing a canvas as the destination makes it a sub-canvas under that canvas when that option is available.

Moving can change project-based access. If someone could open the canvas through the old project, they may need access to the new project or a direct canvas share after the move.

Copying is useful for templates, recurring workflows, and project-specific versions. Rename the copy if the old name is too tied to the source project. If you are copying because the original went missing, check Search and All canvases first.

See Manage canvases in projects.

Move or copy whole sections

Use the section menu to move or copy a whole section to another project. Moving transfers the section to the destination project. Copying creates a separate section and canvases in the destination.

Section move is useful when a workflow slice belongs in another project. Section copy is useful when another project needs the same setup, such as a client onboarding section or recurring launch review section.

Private or restricted destination projects can require an access confirmation. Confirm the destination before moving a section that contains shared or sensitive canvases.

Examples

For a launch project, start with Planning, Design, Review, Approved, and Published. Mark Approved and Published complete if those are the stages that should count toward progress and burndown.

For a client project, keep external review canvases in their own section. Copy that section to a new project when a similar client workflow starts, then rename canvases that contain client-specific context.

For a large research project, use top-level canvases for workstreams and sub-canvases for interviews, notes, or analysis slices. Keep progress based on the top-level workstreams so the project does not become noisy.

Recovery paths

If a canvas is missing from the section you expected, clear filters and check whether it moved under another canvas. Expand parent rows in Project List, then search the project and All canvases.

If a section move or copy did not land where expected, check the destination project and your access to it. A private project or narrower role can hide the result from people who expected to see it.

If a drag does nothing, check whether the view is sorted, whether the drop target is valid, and whether your role allows editing that project. For missing project actions, use Troubleshoot project and canvas access.