> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/general/crm/crm-common-questions/crm-view-mode-kanban-or-list-or-table.md).

# CRM - Viewing Mode - Kanban | List | Table

In **CRM**, it is possible to choose different **view modes** to track and manage opportunities or leads. Each mode organizes the information in a different way, making analysis and tracking easier according to the user's needs.

{% embed url="<https://youtu.be/x-E7Fe0FUnM>" %}

#### Kanban

The **Kanban** mode presents the opportunities in **columns organized by the stages of the sales funnel**.

Each opportunity appears as a **card**, which can be **dragged between stages** to update the progress of the deal.

This mode is ideal for:

* Quickly viewing the progress of opportunities
* Managing the sales funnel flow
* Moving opportunities between stages in a practical way

#### List

The **List** displays the opportunities in **simple rows**, showing the main information of each record.

This format makes it easier to:

* Quickly view multiple opportunities
* Navigate between records more directly
* Access the details of each opportunity

#### Table

The **Table** presents the data in a format similar to a **spreadsheet**, with **rows and columns**.

In this mode it is possible to:

* View more fields at the same time
* Compare information between opportunities
* Use sorting to organize the data

This format is suitable for more detailed analysis and information organization.

💡 **Tip:** you can switch between view modes as needed, choosing the format that best suits your type of analysis or management of opportunities.


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/topics/general/crm/crm-common-questions/crm-view-mode-kanban-or-list-or-table.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.