> For the complete documentation index, see [llms.txt](https://docs.rox.com/development/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rox.com/development/product/organization-level-configurations/editing-user-account-views.md).

# Editing User Account Views

Your account list is one of the most important places you'll work in Rox — and everyone works a little differently. **Account Views** (the tabs above your list) let you save your own personal layouts, so the data you care about is always one click away.

This guide walks you through creating, editing, and managing your views.

> **Good to know:** Views are personal to you. Anything you change only affects your experience — your teammates' views stay exactly as they have them.

***

### What's in a View?

Each view remembers:

* **Columns shown** and the order they appear in
* **Pinned columns** (locked to the left or right as you scroll)
* **Column widths**
* **Sorting** (e.g. sorted by Last Activity, newest first)
* **Filters** (e.g. only accounts in your territory)

Switching between views instantly swaps the layout — there's nothing to "apply" or save manually.

<figure><img src="/files/cPDJ9rsYBTBykePRsNZo" alt=""><figcaption></figcaption></figure>

### Creating a New View

1. Open the account list you want to customize.
2. In the tabs bar, click **+ (New View)**.
3. Give your view a clear name (e.g. *"My Pipeline – West"*) and an optional description.

Your new view appears as a tab and becomes active right away.

<figure><img src="/files/19UaXE6w3A3mTdlHATrK" alt=""><figcaption></figcaption></figure>

***

### Customizing a View

With a view active, just shape the list the way you want — your changes save automatically to that view.

| To do this           | Do this                                         |
| -------------------- | ----------------------------------------------- |
| Reorder columns      | Drag a column header left or right              |
| Hide or show columns | Open the column picker and toggle visibility    |
| Pin a column         | Click the header → **Pin left** / **Pin right** |
| Resize a column      | Drag the edge of the column header              |
| Sort                 | Click a column header and sort (A-Z or Z-A)     |
| Filter               | Use the filter controls on each column          |

<figure><img src="/files/J7bhQRQ9cVepBTjo9tEo" alt=""><figcaption></figcaption></figure>

***

### Renaming or Editing a View

1. Click the view's tab (or open its menu).
2. Select **Rename**.
3. Update the name or description.
4. Click **on the** ✔ **icon**.

***

### Deleting a View

1. Click on the ⌵ menu (present next to the name of the view) and choose **Delete**.
2. Your next-oldest view automatically becomes your new default.

> **Note:** You'll always have at least one view — the last remaining view can't be deleted.

<figure><img src="/files/RRaeFmVa2XSDMmV573CQ" alt=""><figcaption></figcaption></figure>

***

***

### Need Help?

If a view isn't behaving the way you expect, reach out to your Rox admin or contact support — we're happy to help.


---

# 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.rox.com/development/product/organization-level-configurations/editing-user-account-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.
