> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/getting-started/pylonboarding/issue-views.md).

# Issue Views

<figure><img src="/files/9LG9li3rreMBnY4Mdm7T" alt="" width="563"><figcaption><p>Views in your Pylon Dashboard</p></figcaption></figure>

## Overview

Views in Pylon help you organize and manage customer conversations across Slack, email, in-app chat, and more. With Views, you can:

* Focus on what matters most by filtering Issues and Tickets by status, priority, assignee, or source
* Create team dashboards tailored to specific functions or workflows
* Support triage at scale by visualizing queues clearly
* Personalize your day with saved filters and layouts for your role
* Standardize processes across support and success teams

Whether you’re managing hundreds of issues a day or just want a cleaner workflow, Views help you stay focused.

***

## Setup

{% embed url="<https://demo.arcade.software/wy5t7UJmm0rNz1h8YdrC?embed=&embed_desktop=inline&embed_mobile=tab&show_copy_link=true>" fullWidth="true" %}

***

## Use cases

* Individual Queue
  * A *Kanban* view filtered by `Assignee = Current User` to see all of your issues
* Support Queue
  * A *List* view filtered by `Team = Support`, sorted by *priority* for quick triage.
* Feature Requests
  * A view filtered to `Question Type = Feature Request` to view issues [AI labeled as feature requests](https://docs.usepylon.com/pylon-docs/platform/custom-fields#ai-autofill)

***

## Best practices

* Start simple
  * Begin with a few broad views filtered down by team, account owner, or assignee
* Hide extra views
  * Hide views that you don't use
* Use sharing wisely
  * Keep views private by default, but share important ones to drive alignment across teams.

***


---

# 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.usepylon.com/pylon-docs/getting-started/pylonboarding/issue-views.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.