Start with one project.
Build from there.

1. Create your account and workspace.

Sign in with an email link or an available provider, then review the terms. Choose a starter project, give it a name, and create it. A workspace is created alongside your first project, and you can rename it later. Your account includes one free workspace; another workspace starts on a paid plan, or upgrade your first one and then add another free workspace.

2. Give one project some context.

Open your first project. Add a goal, relevant constraints, decisions already made, and a next action. A short, useful brief is enough to begin. Use Projects to create additional projects as your work grows.

For example: ‘Prepare the product launch. Keep the first release focused on the homepage and getting-started guide. Next: review the draft copy.’

3. Add the next few tasks.

Break the work into concrete tasks and attach them to the project. Update their statuses as work progresses and use list or board views to see what needs attention.

Add recurring tasks only where there is a repeatable need. Choose the timezone and schedule deliberately; reminders are delivered to the schedule owner’s verified email.

4. Keep useful context nearby.

Use project and task comments for updates, decisions, and history. Comments keep their original text and attribution; add a correction when something changes.

In Resources, write a library note for an editable brief, plan, or reference. Upload original documents, spreadsheets, images, and exports from a project or task, or save an HTTPS link to an existing source.

For supported file operations, authorize Google Drive separately in Sources & accounts. You do not need an integration simply to start organizing work.

5. Invite people. Then choose whether to add an agent.

Owners and admins can invite collaborators in Settings → People & roles. Invitations are tied to the recipient’s email; the recipient needs a verified account to accept.

To connect an agent, start in a compatible client’s MCP settings and follow the authorization flow. Begin with the smallest set of permissions that supports the work.