# Views

> Views are the screens where your team works with records. Learn the view types, how to create a view, and how filters and permissions apply.

A view is a working screen over one table. It is where people find, read, and edit records: a list to scan, a board to drag cards across, a calendar to plan the week, or a map of sites.

Every view reads its table through an [access filter](/docs/base-views). The access filter decides which rows and columns are available at all. The view then adds its own settings on top: a filter, a sort, which columns are visible, and in which order. A view can only narrow what the access filter allows. It can never show rows or columns the access filter withholds.

## View types

| Type | Use it for | What it needs |
| --- | --- | --- |
| [Table View](/docs/views/table) | Scanning, filtering, grouping, and editing many records | Nothing extra |
| [Kanban View](/docs/views/kanban) | Moving records through stages | A Status, Single Select, or Text column |
| [Calendar View](/docs/views/calendar) | Scheduling and planning | A Date column for the start |
| [Map View](/docs/views/map) | Records that have a place | A Location column |
| [Entry View](/docs/views/record-page) | Showing one record on its own | A record to show |

Table, kanban, calendar, and map views can all open a record. When someone clicks a row, a card, an event, or a pin, the [record page](/docs/views/record-page) opens with the record's form, its history, comments, files, and related lists. You set up that record page on the view.

## Create a view

1. In the sidebar, hover over the folder where the view should live and click **+**.
2. Choose **New view**.
3. Enter a **Name** and, if you like, a **Description**.
4. Pick a **View Type**. Kanban and calendar views ask for a few extra fields. See [Kanban view](/docs/views/kanban) and [Calendar view](/docs/views/calendar).
5. Under **Parent Data View**, pick the access filter this view reads from. Or turn on **Resolve parent base view dynamically via group routing** and pick the table, so each person gets the access filter assigned to their group.
6. Set who can use the view. See [Permissions on a view](#permissions-on-a-view).
7. Click **Create**.

> **Note:** The view type can't be changed after the view is created. To show the same records another way, create a second view on the same table.

## Change a view

Click **Settings** in the view's toolbar to open the **View Settings** panel. It lists every setting of the view, with its current value on the right.

| Setting | What it does |
| --- | --- |
| **Layout** | Shows the view type. |
| **Customize layout** | Sets up the [record page](/docs/views/record-page) that opens from this view. |
| **Property visibility** | Shows or hides columns in this view. |
| **Filter**, **Sort** | Choose which records appear and in which order. |
| **Group** | Groups rows in a [table view](/docs/views/table). |
| **Card Layout** | Chooses what a [kanban](/docs/views/kanban) card shows. |
| **Copy link to view** | Copies a direct link you can share with teammates. |
| **Source** | Opens the table the view reads from. |
| **Record name** | Picks the column used as each record's title. |
| **Edit properties** | Adds or edits columns on the table. |
| **Business Rules** | Opens the [business rules](/docs/business-rules) for the table. |
| **Workflows** | Opens your [workflows](/docs/workflows). |
| **Import Data**, **Export Data** | Bring records in from a file, or download them. |
| **General** | Name, description, and type-specific settings, such as the calendar fields. |
| **Permissions** | Who can create, read, update, and delete through this view. |
| **Change History** | Every change made to the view's setup, and who made it. |

### Save filters, sorts, and grouping

When you change the filter, sort, or grouping from the toolbar, the change applies only to you at first. To keep it:

- **Save for everyone** stores the new filters, sorts, and grouping on the view for everyone who uses it.
- **Save as new view** keeps this view as it was and puts your changes into a new view.

## Permissions on a view

Each view has its own permission list. Open **Settings**, then **Permissions**.

- **Inherit from parent** uses the permissions of the folder the view sits in. You can add extra entries on top.
- **Custom permissions** uses only the entries you list on the view.

Each entry grants access to the whole organization, a group, a single person, or holders of a permission, with a choice of Create, Read, Update, and Delete. Presets such as **Full Access**, **Can Edit (no delete)**, and **Read Only** fill in common combinations. The person who created the view always has full access to it.

Organization permissions decide who may create or delete views at all. See [Access](/docs/access) for the full picture.

> **Note:** Per-view permissions are available on Pro and above. On other plans, views are visible to all organization members.

## Plan a good view

A good view supports one job: "the board the dispatcher drags", "this week's deliveries", "open invoices by customer". When you set one up, decide:

- Which type fits the job.
- Which access filter it reads from, or whether each group should get its own.
- Which filter, sort, and columns people need to see first.
- What the record page should show when someone opens a record. A list with no useful record page is an unfinished screen.

  - [Table view](/docs/views/table): Scan, filter, group, and edit many records.
  - [Kanban view](/docs/views/kanban): Move records through stages on a board.
  - [Calendar view](/docs/views/calendar): Plan work by day, week, or resource.
  - [Map view](/docs/views/map): See records as pins on a map.
  - [Record page](/docs/views/record-page): Design what people see when they open a record.

---

Source: https://community.sapugo.app/docs/views