> For the complete documentation index, see [llms.txt](https://docs.ebrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebrain.ai/tasks/views-and-collaboration.md).

# Views and collaboration

Every project in **Tasks** holds the same set of tasks, but you can look at them three different ways and switch whenever it suits the job at hand. Changes you and your teammates make show up live, so the board always reflects what is really happening.

This page covers the three views, how to organize what you see, and the ways you work together. To create projects and tasks or learn about roles, see [Projects and tasks](/tasks/overview.md).

## The three views

A small **view switcher** sits at the left of the toolbar with three icons: **Board**, **List**, and **Gantt**. Click any one to switch instantly.

| View      | Best for                                                                                                  |
| --------- | --------------------------------------------------------------------------------------------------------- |
| **Board** | Moving work through stages and seeing at a glance what is in progress. A kanban grid of cards in columns. |
| **List**  | Scanning, editing, and bulk-changing many tasks fast. A dense table with inline editing.                  |
| **Gantt** | Planning and spotting overlaps. A timeline that shows tasks with dates as bars you can drag.              |

### Board view (kanban)

Tasks appear as cards in columns. By default the columns are your project's statuses (**To Do, In Progress, Review, Done**).

* **Drag a card** to another column to change its value, or drag within a column to reorder. What the move changes depends on the current **Group by**: by **Status** it moves the task (dropping into a Done-type column marks it complete automatically; moving it back out un-completes it); by **Priority**, **Assignee**, or **Label** it changes that field instead.
* **Quick add**: each column has an inline **New Task** field. Type a title, press Enter, and the task is created in that column.
* **Manage columns** (only when grouped by Status): use the dashed **Add column** tile to create a column with a name, a category (**To do / In progress / Review / Done / Cancelled**), and a colour. Each column's "…" menu lets you rename or delete it. You cannot delete the last remaining column, and if a column still holds tasks you must first choose another column to move them to.

### List view

A table with columns for selection, **Status**, **Title**, **Assignee**, **Due Date**, **Priority**, **Labels**, and a "…" actions menu.

* **Edit inline**: change status and priority from dropdowns, set a due date from the calendar popover, add or remove assignees and labels right in the row, and **double-click a title to rename it** (Enter saves, Escape cancels).
* **Delete** a task from its "…" menu.
* **Bulk actions**: tick several rows (or select all) and a floating bar shows "{n} selected" so you can change status or priority for every selected task at once.
* **Subtasks** appear nested with expand and collapse chevrons; a collapsed parent shows a done/total badge.

### Gantt view (timeline)

A timeline with a task sidebar on the left and bars on the right.

* **Zoom** with **Week**, **Month**, or **Quarter**, and use the **Today** button to jump to the current date.
* **Only tasks with a start date and/or a due date appear here.** If none have dates yet, you will see a prompt to add start or due dates.
* **Drag bars to schedule**: drag the middle of a bar to move the start and due dates together, or drag the left or right edge to change just one of them.

{% hint style="info" %}
In Gantt view, the search, filter, group-by, and sort controls are hidden, and subtasks always show as if expanded.
{% endhint %}

## Organizing what you see

In **Board** and **List**, the toolbar gives you a few ways to focus:

* **Search** — free-text box that matches task titles and descriptions.
* **Filter** — a popover (with a badge showing how many filters are active) to filter by **Status**, **Priority**, **Labels**, and an **Overdue** toggle. Use **Apply** to set them and **Clear** to reset.
* **Group by** — **Status**, **Assignee**, **Priority**, **Label**, or **No grouping**.
* **Sort by** — **Manual** (your drag order), **Title**, **Priority**, **Due date**, **Created**, or **Updated**.
* **Subtask display** — **Collapsed** (default, hidden under parents), **Expanded** (nested under parents), or **Separate** (their own cards or rows, handy for filtering subtasks).

### Your setup is remembered

{% hint style="success" %}
Your choice of view, plus grouping, sorting, collapsed groups, and subtask display, is remembered per project. When you reopen a project, it looks exactly as you left it, and each project can have its own setup.
{% endhint %}

## Working together

### Comments

Open any task and go to the **Comments** tab. Write in the box and click send or press **Cmd/Ctrl+Enter**. Comments support markdown and threaded replies, and each shows the author, a timestamp, and an "edited" marker when changed. You need to be a member of the project to comment.

### Activity log

The **Activity** tab on a task is an automatic history of what happened to it, such as when it was created and when its status or assignee changed. It is a read-only audit trail, so there is nothing to fill in.

### Time estimates

The task detail sidebar has an **Hours** field. This is a planned-time **estimate** for the task, so you can capture how long you expect work to take. It is not a running log of time spent.

### Live real-time sync

The board is live. While a project is open, it keeps a real-time connection so that when a teammate, or Tim, creates, updates, moves, assigns, comments on, or deletes a task, your view updates automatically with no manual reload. The connection reconnects on its own if your network drops and closes when you leave the project. This is what lets several people work the same board at once and see each other's changes appear.

{% hint style="info" %}
You can also ask **Tim** to create, update, assign, and comment on tasks from chat or WhatsApp, and those changes show up live on the board just like manual edits. Because changes that send or create things are confirmed first, see [Approval flows explained](/chatting-with-tim/approval-flows.md). Tim respects the same project permissions you have.
{% endhint %}

### Permissions in collaboration

What you can do on a shared board depends on your project role. **Viewers** have read-only access and cannot create, move, edit, or delete tasks, while Owners, Admins, and Members can make changes. See [Projects and tasks](/tasks/overview.md) for the full breakdown of roles and member management.

<table data-view="cards"><thead><tr><th>Topic</th><th data-card-target data-type="content-ref">Link</th></tr></thead><tbody><tr><td>Create projects, tasks, and manage roles</td><td><a href="/pages/QHjGRyyr3mGbgO5HBTLx">/pages/QHjGRyyr3mGbgO5HBTLx</a></td></tr><tr><td>Let Tim manage tasks for you</td><td><a href="/pages/omYTaN5jK46mNbpfwSqk">/pages/omYTaN5jK46mNbpfwSqk</a></td></tr><tr><td>How Tim confirms changes before applying them</td><td><a href="/pages/U5I52kkdwBkHiYY8zxEH">/pages/U5I52kkdwBkHiYY8zxEH</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ebrain.ai/tasks/views-and-collaboration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
