Projects are a Beta organizational surface for focused initiatives. A project gives an initiative its own identity, progress information, and optional ticket grouping without creating another workspace.
When to create a project
Create a project
Use one when work has its own outcome, priority, owner, or progress view, such as a product launch or content program.
Keep work on the workspace Board
Use the main Board when tickets do not need initiative-level grouping or a separate progress view.
Use one project when the work shares the same goal and board. Split it when the outcomes need separate ownership or progress views.
What belongs in a project
Projects and the workspace
Your workspace remains the home for shared agents, workflows, connections, and knowledge. A ticket can belong to a project when it contributes to that initiative, or remain on the main Board when it does not need project grouping.
Use a project for useful organization, not as a required foundation for every automation.