Create your first project

Create a project from the workspace's project controls. Give it a clear name, a short outcome-focused description, and choose the template closest to the work:

• Simple Project for a lightweight list.
• Software Project for triage through shipped work.
• Operations Project for intake, this week, waiting, and complete work.

Templates seed the first project plan and sections. They do not lock the project into a methodology: rename, reorder, add, or archive sections as the team learns what works.

Next, open Context and review the canonical brief. Record purpose, users, outcomes, constraints, non-goals, terminology, priorities, and agent guidance. This gives both people and agents the same durable source of intent.

Add project members from Project Settings → Team. Project access is separate from workspace membership: inviting someone only to a project does not grant workspace-wide Notes, billing, settings, or unrelated project access. Use Viewer for read-only access and Member when the person should change shared project work.

Create the first few tasks, link relevant Context, and add blockers only when one task genuinely prevents another. Use comments for delivery discussion and the Message Board for durable project-wide announcements or decisions.

If an agent will participate, create a least-privilege Agent Connection, grant only this project, and place project-specific operating rules in the brief or repository instructions.