Projects and Tasks: when to use each

It's the most common question when starting out. The short rule: if it's a single action, it's a task; if it's a set of actions with a goal and a closing date, it's a project.

When a standalone task?

For one-off work that resolves on its own and isn't part of something bigger: "reply to the client", "upload the October report", "review the ad spend". It lives in the workspace or the account, and needs no further structure. See Create and organize tasks.

When a project?

When the work is a multi-stage engagement: a website redesign, a campaign launch, a long onboarding. There you want a top-down view —progress, owner, end date, phases— and inside it, the concrete tasks. The project gives you that view; the tasks, the execution. See Manage your projects: views, fields and tasks.

How do they connect?

A project contains tasks: you create them inside and they're real tasks from the Tasks module, so they also appear in your task lists and filters (you can filter by project). The project's progress reflects how those tasks are going. You don't duplicate anything: it's the same work, seen from two heights.

A key point for agencies: visibility

Each project has a Visibility that controls who sees it, and this matters a lot when you work for clients with access to the platform:

• Agency only — only your agency's members see it, not the client. Use it for internal work: margins, strategy notes, work you don't want to show yet.
• Public — also visible to that account's client.
• Custom — visible only to the people you choose.