# Views

### Customizing Columns

Click the **Gear icon** (⚙) in the top right of any supported tab to open the column settings modal. From here you can:

* **Toggle columns on or off** — Show or hide available columns. The columns available will vary by tab.
* **Reorder columns** — Drag columns to rearrange the order they appear in the table.
* **Pin columns** — Pin a column to keep it visible as you scroll horizontally. Useful for anchoring key identifiers while reviewing other fields.

Click **Save** to apply your changes.

---

### Filters

Click **Add filter** to narrow what's displayed. Filters vary by tab.

Filters can be combined for targeted review. A few examples:

* Filter Transactions by **entity = Personal** to review personal transactions for reclassification
* Filter Transactions by **Reconciliation = Not Reconciled** to surface outstanding items
* Filter Bill Pay by **status** to see only **unpaid bills**
* Filter Chart of Accounts by **Account Source = Custom** to isolate custom accounts

---

### Saving Views

Once you've configured your columns and filters, you can save the layout as a named view:

1. Set up your preferred columns, order, and filters.
2. Click **Save View**.
3. Name the view and set it as your default landing view if desired.

Saved views are accessible from a dropdown, so you can quickly switch between different layouts depending on the task.

To edit an existing view, select it, adjust columns or filters via the **Gear icon** (⚙), and click **Save changes**.

---

## 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.kick.co/accountants/collaboration/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.
