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

# Views

**Views** help organize and present data in a way that is relevant to the user's needs. By selecting a particular view, you can quickly filter and display records that match the criteria set by that view. This makes it easier to focus on relevant information without being overwhelmed by unnecessary data. All views are customizable to fit entity processes and functionality.

#### Types of View

| View Type        | Description                                                                                                                                                                                                                               |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| System View      | a system view refers to a predefined and configurable way of displaying records from a specific entity. System views allow users to filter, sort, and organize records based on criteria that are relevant to their tasks and objectives. |
| Lookup View      | A lookup view refers to a specific type of view that allows users to search and select records from a related entity while working with a record in another entity.                                                                       |
| Document View    | a document view refers to a user interface component or feature that allows users to manage and interact with documents associated with records within the system.                                                                        |
| Search View      | a search view refers to a user interface component that allows users to perform searches and retrieve specific records based on search criteria.                                                                                          |
| Quick Grid View  | a Quick Grid View refers to a user interface component that allows users to display and interact with a list of records in a compact, tabular format within a form or page.                                                               |
| Portal List View | a portal list view refers to a user interface component within a customer or external-facing portal that displays a list of records from Ezra360 entities.                                                                                |
| Calendar View    | a calendar view is a visual representation of records that have date or time-related attributes.                                                                                                                                          |

The following image below shows an example of a <mark style="color:orange;">**view**</mark>. Views are pre-defined filters that allows users to see specific subsets of data based on their desired criteria or outputs. The views help organize and present data in a way that is relevant to the user’s needs. It is a listing of data within a n entity.\
On <mark style="color:orange;">**#1**</mark> shows where you can filter the view, to show the list of data you want to view.\ <mark style="color:orange;">**#2**</mark> is the search bar where you search for the list of data you want to view.\ <mark style="color:orange;">**#3**</mark> Shows an index find where you can filter the list of data by alphabet. When you click alphabet it will show data that starts with that specific alphabet.

<figure><img src="/files/TFQTtED3qTbg4VYYl16A" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>

* **Quick Find:** Finding a specific record by using search bar.
* **Filters:** Filter data to display only what you’re interested in.
* **Column headings and sorting:** In a grid, column headings display the names of columns that were defined in the layout. For example, in the above images when you click subject, you will sort the listing data alphabetically (Ascending or descending)
* The **Select All** check box appears next to the first column heading. When you select the check box, all the rows on the current page in the grid are selected, you can perform actions collectively for all records.
* **Index:** You can select a character in the index to filter records in the grid or list that start with that character. For example, to display records that start with the letter *P*, select *P* on the index, and records that start with *P* are displayed<br>

The image below shows a view with Select options. The pointer at <mark style="color:orange;">**#4**</mark> shows the listing of views.

<figure><img src="/files/p1umLOlp00dIdLG3vHxf" alt=""><figcaption><p><mark style="color:red;">Click image to view full screen</mark></p></figcaption></figure>


---

# 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.ezra360.com/overview/components-overview/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.