> 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/support-workflows/issues/views.md).

# Views

Customize how you view and act on issues. Pick a default view or save your own, then change the layout, filters, and columns.

## Default views

The Support sidebar starts with views every teammate has:

* **Inbox**: new issues assigned to you or unassigned, plus issues that are On you and assigned to you
* **All issues**: every issue
* **My issues**: issues assigned to you, plus unassigned issues
* **Following**: issues you follow
* **Snoozed**: issues that are snoozed

Below them are **Scheduled**, which lists messages scheduled to send later (see [Message Editor](/pylon-docs/support-workflows/issues/message-editor.md)), and **Drafts**, which lists unsent reply drafts and saved drafts of new issues.

You can change the filters and layout of a default view and click **Save to View** to keep your version. Your changes only apply to you. To go back to the original, open the view's **...** menu and choose **Reset to default**. From the same menu, **Create view from current** turns your changes into a new view, and **Set as Default View** makes it the view you land on.

## Custom views

Click **Create view** to save your current filters and layout as a new view. Under **Who can view?**, choose **Anyone**, **Some members** (specific users and teams), or **Only me**. Use **Who can edit?** to choose who can update the saved view. Editors must also be included in its viewing audience. Views can be starred and organized into folders.

Editors can rename a view, update its icon, change its sharing settings, and delete it. If you can edit a shared view and click **Save to View**, Pylon asks whether to save the changes for everyone or duplicate the view instead.

If you can only view a shared view, you can still change filters and layout temporarily or create a separate view from your changes. You can't overwrite the shared view. Personal changes to built-in views remain separate from shared-view permissions.

## Inbox

The Inbox layout shows a list of issues next to the open issue, so you can work through a queue without leaving the page.

* **Pin issues**: hover over an issue and click **Pin**, or choose **Pin issue to inbox** from an open issue's **...** menu. Pinned issues stay at the top of your Inbox in a collapsible **Pinned** section, and you can drag them to reorder. Pins are personal.
* **Card options**: in the layout menu, choose whether cards show the requester name and issue number, and what message preview to show.

Inbox is a layout, so you can also switch any other view to it.

## Kanban

The Kanban view allows you to see issues laid out in a grid. Pylon's standard Kanban view organizes issues by status.

* Drag an issue between columns to change its status. Select several cards first to drag them together.
* Change the assignee directly from the kanban view by clicking on the assignee avatar
* Greyed out cards indicate issues that have already been viewed by your user
* Cards with a red dot indicate new activity since you last viewed an issue

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FiHDu7N96YtHWi94tPJzv%2FCleanShot%202024-10-06%20at%2021.23.03.png?alt=media&amp;token=6b64fee7-41d3-41f2-b30b-256083ff538d" alt=""><figcaption></figcaption></figure>

## List

The List view allows you to view issues in a list with columns.

* Customize the columns that are visible in the list view
* Change the assignee directly from the list view by clicking on the assignee avatar
* Greyed out rows indicate issues that have already been viewed
* Rows with a red dot indicate new activity since you last view that issue

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2F2BIEwBJouHtklgd0p2pK%2FCleanShot%202024-10-06%20at%2021.20.23.png?alt=media&amp;token=998dc194-c55e-4fe2-b980-df886d1e9805" alt=""><figcaption></figcaption></figure>

## See who's viewing an issue

Kanban cards, Inbox cards, and List rows show avatars of teammates who currently have the issue open. Check them before replying so two people don't answer the same customer.

## Filters

Select filters to apply to narrow down the set of visible issues. Issues can be filtered by a variety of default fields across issues, accounts, or contacts as well as any custom fields you've created. By default, filters are AND'ed together, meaning only issues meeting all specified filters conditions will appear.

Filters can also be combined in advanced ways using Filter Groups. With Filter Groups, different groupings of filter conditions can be combined with AND or OR operators.

To hide the child issues of [issue groups](/pylon-docs/support-workflows/issues/issue-groups.md) from a view, filter on **Parent Issue Group** · **has no value**.

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FMX1eI3qLh5K0TmUhS4bi%2FCleanShot%202024-10-06%20at%2021.10.56.png?alt=media&amp;token=a0429a62-4379-4ed5-ae83-2334363e85f0" alt=""><figcaption></figcaption></figure>

## Layouts

Use the layout menu to change the structure of your view. You can customize:

* Display as: Inbox, Kanban, or List
* Sort by: the order issues appear in within each group
* Columns: For Kanban, the vertical dimension you want issues to be displayed by. For List, the data properties that are visible. (Not used in Inbox.)
* Grouping: For Kanban, a second dimension to visualize issues by. For List, the primary dimension you want to view issues by
* Show unreads only: only display issues with unread activity
* Show requester name, and in Inbox, show issue number
* Preview: choose what message preview appears on cards
* Timestamp: pick what timestamp you want displayed on the cards

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2FZ8OShFdwj0IsybSFkOyr%2FCleanShot%202025-03-07%20at%2019.56.36%402x.png?alt=media&amp;token=fb286fe4-5873-4384-8643-8007fa2f7f51" alt="" width="375"><figcaption></figcaption></figure>

<figure><img src="https://982123570-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9hXBoCTTNw5flARlUVJf%2Fuploads%2F0YDGpzseCfyTj8yCiPid%2FCleanShot%202024-10-06%20at%2021.15.23.png?alt=media&amp;token=6b2826b7-1370-415f-a16b-df94b54cee36" alt=""><figcaption><p>Example of a Kanban layout with Issue Status as the Column and Priority as the Grouping</p></figcaption></figure>

## Export to CSV

To download the issues in a view, click the export button in the view header, then **Export to CSV**. Large exports run in the background. You can leave the page, and the file will appear in your notifications when it's ready. Past files are listed under **Recent exports**.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.usepylon.com/pylon-docs/support-workflows/issues/views.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.