How your board is organized

A project is the boundary for a goal, product, campaign, or client. Its board, files, settings, and connected AI context stay together, preventing work from one project from being mistaken for work in another.

Work units collect tasks into meaningful streams, such as research, production, or distribution for a launch. They make a large project easier to review without changing its task lanes.

A task is an individual job with a title, description, priority, status, and optional acceptance criteria. It can belong to a work unit or sit directly in the project. Its status determines where it appears on the board.

Blank projects resolve to Agiflow's default columns: Planning, Todo, In Progress, Testing, Review, Done, Blocked, and Cancelled.

• Planning: Work is being refined.
• Todo: Work is ready to start.
• In Progress: Work is underway.
• Testing: Work is being validated.
• Review: Work awaits approval.
• Done: Work is complete.
• Blocked: Work needs intervention.
• Cancelled: Work will not continue.

Templates can seed different names and ordering. A marketing project can reflect a publishing flow, while a sales project can reflect a deal pipeline. The project is the source of truth for its available statuses, so do not assume the default list applies everywhere.

You need access to the project in your Agiflow organization. If the project is assigned through a team, your organization membership must include that team.

1. Open the project in Agiflow.
2. Select the Board view if another project view is active.
3. Read the column headings from left to right. They are the statuses available to tasks in this project.
4. Use a work unit filter to focus on one stream. Filtering changes visible tasks, not lane definitions.

The board displays one column for each resolved project status. A blank project still shows default columns when it has no tasks. A template-created project can show custom names and ordering.

Open a task's status control and compare its available names with the visible board columns. They should describe the same project workflow.

This path explains how to read current lanes. It does not mean every member can create or edit status definitions. If a project is missing, confirm the organization and team access. If its names differ from another project, use the lanes shown on the current board.

Templates give a new project a workflow suited to its purpose. They can seed project-specific statuses and starter tasks, which is why projects in the same organization can have different lanes.

For the creation flow, see Start from a project template.

The Artifacts view keeps shared files with the project rather than attaching the same context to every task. A specification or brand guide can support many work units and tasks on the board.

For file procedures, see Manage project files.

Projects live inside an organization, and team assignments determine which projects a member can access. Connected AI tools work within the access approved for their connection, so project scope is both an organizational and safety boundary.

For membership procedures, see Invite your team.