Back to Kanban Tasks

Kanban Tasks setup guide

How to set up Kanban Tasks without turning it into a project

This guide is written for normal business users, not project-management power users. If you live in Gmail and want a calmer way to keep work moving, this will get you set up without jargon, without guesswork, and without assuming you already know how Kanban works.

Start here

You do not need a perfect setup to get useful value out of Kanban Tasks. These reminders will help you start cleanly and keep day one simple.

Open Kanban Tasks wherever it feels most natural to you. Many people use it in Gmail, and many others prefer the standalone app.

Start with one real workflow you already manage every week, not a grand system for every project and every team.

Keep your first board simple. You can rename lists, add more detail, and fine-tune the setup once the board is already useful.

If you plan to share the board, keep your teammates' email addresses ready so you can invite them once the board is in place.

Step 1

Start in the simplest way possible

The easiest way to begin is in the version you already have open. Some people prefer Gmail because work starts there, and others prefer the standalone app because it gives them more room to work.

1.1

Open Kanban Tasks where you already work

If you are in Gmail, open Tooling Studio from the Google Workspace sidebar. If you are using the standalone app, open Kanban Tasks there instead. The goal is simply to start in the place that already feels normal to you.

1.2

Sign in with Google

Sign in with your Google account and let the workspace load. If something does not appear right away, refresh once or reopen the app. Most first-run hiccups are small and easy to fix.

1.3

Let the product teach you the shape of the workspace

You do not need to understand everything on day one. What matters first is knowing that the sidebar is your home base, boards live there, and clicking a task opens the full details on that task.

You are not choosing between two different products here. Gmail and the standalone app lead you into the same workspace, so use the one that feels easiest to return to.

Step 2

Understand the three building blocks

Kanban Tasks stays easy to use because the structure is simple. You only need to learn three terms.

A board is the overall workspace for a project, team process, or area of responsibility.

A list is a stage inside that board, such as To do, Doing, Waiting, or Done.

A task is the card that holds the actual work item.

If you are brand new, do not over-design your board. A small board with a few clear lists beats a clever setup you never maintain.

Step 3

Create your first board the way real teams actually use it

Most people make Kanban harder than it needs to be. Your first board should be tied to one real stream of work, not your whole business.

3.1

Pick one outcome, not ten

Good first boards are things like Client onboarding, Weekly operations, Marketing requests, Hiring pipeline, or Product backlog. Bad first boards try to capture every task in the company at once.

3.2

Start with four or five lists

A strong default is Inbox, Next up, In progress, Waiting, and Done. You can always rename them later once your team starts using the board for real.

3.3

Add a few real tasks immediately

Do not leave the board empty. Add the work you already know is happening this week so the board becomes useful right away.

Step 4

Open one task and add the details people actually need

The task card is where scattered context becomes shared clarity. Clicking a card opens the detailed view.

4.1

Write the task so someone else could understand it

Use a clear task title. Then add the short description, not a giant essay. The goal is to make the next action obvious.

4.2

Use due dates and assignees when ownership matters

Due dates help work show up in the right focus views. Assignees make it clear who is expected to move the task next, especially on shared boards.

4.3

Keep supporting detail inside the task

Kanban Tasks supports checklists, comments, attachments, tags, rich descriptions, and an activity log. That means the conversation and the work can stay together instead of being split across email, chat, and memory.

A useful rule: if someone would ask about the task later, put the answer on the task now.

Step 5

Turn emails into tasks instead of letting them become mental debt

This is one of the reasons people choose Kanban Tasks over a separate project tool. Work often starts in Gmail, so capturing it there matters.

5.1

Use an email when follow-up matters more than the message itself

When an email represents an action, create a task from it or drag it into the right board or list. That keeps the work visible instead of burying it in your inbox.

5.2

Use the task as the shared follow-up space

The task keeps the email subject and a link back to the original message. From there, your team can comment, assign, and plan the work around it.

5.3

Know the privacy rule

The email link is tied to the person who created the task from the email. Teammates can work on the task, but they do not automatically get access to your mailbox.

Step 6

Set up your team before you need it in a rush

Kanban Tasks works well for solo use, but shared boards are where the product becomes much more valuable for many teams.

6.1

Create a team when the work is no longer just yours

If a board needs shared visibility, create a team and keep that work in the team space instead of in a personal board. That gives everyone one live place to work from.

6.2

Invite people from Manage Team & Seats

In team settings, invite teammates by email. When you invite them, you can choose their role and choose which product and boards they should be able to access.

6.3

Use the roles on purpose

Members should be the default for day-to-day collaborators. Admins are for people who need to manage users, product access, team settings, and billing.

6.4

Share only the boards that need to be shared

Not every board needs every person. Keep shared work visible, but keep the setup clean enough that people can immediately tell which boards matter to them.

Once a board is shared, real-time updates matter. If one person moves a task, everyone else sees the board change without waiting for a refresh.

Step 7

Use the built-in focus views so you do not have to open every board

A lot of people miss this at first. Kanban Tasks is not just separate boards. It also gives you views that cut across boards.

7.1

Get Work Done

Use this when you want a day-and-week view. It collects due-date-driven tasks from across your boards so you can see what needs attention now.

7.2

Assigned

Use this when you want to see what is clearly yours. It is the fastest way to answer, What am I responsible for right now?

7.3

Mentioned

Use this when your team collaborates heavily in comments and descriptions. It brings you back into the tasks where someone directly pulled you in.

Step 8

Turn on deadline visibility once the basic workflow is working

Do not start with every setting. First get people using the board. Then layer in due dates and calendar visibility.

8.1

Add due dates to the tasks that genuinely need them

Not every task needs a deadline. Use due dates for the work that is time-sensitive, scheduled, or likely to slip if nobody sees it.

8.2

Enable calendar sync if your team lives by the calendar

Tooling Studio can sync due dates into Google Calendar. In the app, this lives under Settings and Integrations. If you enable it, you may be signed out once so you can reconnect with the extra permission.

8.3

Use search when the board gets busy

Search is there to take you straight to the right task instead of making you hunt through lists and boards. Once your setup grows, that becomes one of the most useful habits in the product.

Step 9

A good first-week setup for a solo user or small team

If you want one practical way to roll this out, use this sequence.

Create one board for real work you already have this week.

Add four or five simple lists rather than a fully custom workflow.

Move three to five live tasks onto the board immediately.

Turn at least one real email into a task so the Gmail workflow becomes obvious.

Add due dates only where timing really matters.

If the work is shared, invite teammates and assign owners before the board gets crowded.

The goal of week one is not perfection. It is to make the board useful enough that people come back to it tomorrow.

If something feels off during setup

Start smaller. One board, a few live tasks, and only the details your team genuinely needs. If something still does not load correctly or your team setup feels confusing, reach out early instead of letting a half-working setup sit there unused. [email protected] .