Actions on view

View context menu

The view context menu provides a set of tools to interact with the view. The view context menu can be accessed by clicking on the ellipsis symbol (...) located next to view in the left sidebar.

Rename view

1. Click on the ellipsis symbol (...) next to view name located in the left sidebar.
2. Click on the Rename option from the view context menu.
3. Enter the desired new view name into the provided field.
4. Use Enter key to finalize the renaming process.

Change view icon

1. Click on the existing view icon to the left of the view name in the left sidebar.
2. Select the desired icon from the list of available options.

Duplicate view

1. Click on the ellipsis symbol (...) next to view name located in the left sidebar.
2. Click on the Duplicate option from the view context menu.
3. Enter the desired new view name into the provided field.
4. Click on the Duplicate View button in the confirmation dialog.

Delete view

1. Click on the ellipsis symbol (...) next to view name located in the left sidebar.
2. Click on the Delete option from the view context menu.
3. Click on the Delete View button in the confirmation dialog.

Lock / Unlock view

Locked views prevent members from modifying view configurations. To lock a view, change the permission type to Locked from the view context menu. To unlock a view, change the permission type back to Collaborative.

You can also add a custom message to inform members why the view is locked. This message is visible to all members when they attempt to unlock the view.

Locked views in sidebar appears with a lock icon next to the view name.

When a locked view has a custom lock message configured, an info icon (ⓘ) appears next to the "This view is locked" banner at the bottom of the toolbar menus (Fields, Filter, Sort, Group By, etc.). Hover the icon to read the creator's message.

What editors can and cannot do on a locked view

Editors on a locked view can still:

• Read the view's saved filters, sorts, group-by, and field configuration (displayed read-only).
• Duplicate the view — the duplicate is created as a new unlocked view they can edit.
• Move the view between existing sidebar sections, or reorder it in the sidebar.

Editors cannot rename, delete, or modify the configuration of a locked view. Attempting to do so from the view context menu shows a "Disabled as View is locked" tooltip. Only Creators and Owners can modify or delete locked views, or unlock them.

Personal Views ☁

Personal Views give exclusive control over view configurations to the owner. Other members (including other editors) retain read-only access to the view and its saved configuration. To make a view personal, change the permission type to Personal from the view context menu. To revert back to Collaborative or Locked, change the permission type accordingly.

Who can claim or reassign a personal view

• Any Editor, Creator, or Owner can convert a collaborative view into a personal view — the user who performs the conversion becomes the view's owner.
• The owner of a personal view can convert it back to Collaborative at any time. Reverting to collaborative clears the ownership assignment, so the view becomes a regular collaborative view again.
• Only Creators and Owners can assign a view as another user's personal view, or transfer ownership of an existing personal view to a different user. Editors can only self-claim.

Assigning a view to another user (Creators & Owners only)

Creators and Owners can assign or change the owner of a Personal View from the left sidebar view context menu.

Personal view in sidebar appears with a user icon next to the view name.

Editor access to other users' personal views

Editors who are not the owner can open a personal view and see its data and saved configuration (filters, sorts, group-by, field visibility) as read-only. Rename, delete, and edit actions on the view are disabled with a tooltip stating that only the view owner can modify or delete the view. Only the owner or a Creator/Owner of the base can make changes.

Add / edit view description

View description can be added by clicking on the Add Description button on the view creation modal or by clicking on the Edit Description button from the view context menu.

Description for a view will be visible as a tooltip when hovering over the info icon next to the view name.

Copy another view's configuration ☁

You can copy view configurations from another view to quickly apply the same settings to your current view. This is useful when you want to replicate filters, sorting, field visibility, and other configurations across multiple views.

Steps to copy view configuration

1. Click on the vertical ellipsis symbol ⋮ in the toolbar.
2. Select "Copy another view's configuration" from the view context menu.
3. In the modal dialog, select the source view from the Select view to copy from dropdown. All the views available in the current table will be listed here.
4. Check the configuration(s) you want to copy:
   • Field visibility - Copy which fields are visible/hidden
   • Field order - Copy the column arrangement
   • Column width - Copy column width settings
   • Row height - Copy row height settings
   • Filter condition - Copy applied filters
   • Group - Copy grouping settings
   • Sort - Copy sorting settings
   • Row coloring - Copy row color settings
5. Click "Copy configuration" to apply the selected settings to your current view.

Selective "Copy from another view" menu option is also available for various toolbar items like Filter, Group and Sort. This opens up the same copy configuration modal with the respective configuration option pre-selected. You can then choose to copy additional configurations as needed.

Note that,

• When copying configurations, the system will only apply settings that are compatible with the current view type. Incompatible settings will be disabled in the copy configuration modal.
• Only views from the same table can be selected as source views for copying configurations.

Views filtered by Current User ☁

NocoDB allows you to filter views based on the currently logged-in user. This is particularly useful for creating personalized views that display records relevant to the user currently logged in. Find more details on how to filter by current user in the Filtering records by current user section.

URL based record filtering

NocoDB enables users to dynamically filter records using query parameters directly in the URL. This is useful when creating sharable views or automating filtered data access in embedded dashboards or internal workflows.

Basic Syntax

Filtering is controlled using the where query parameter in the following format:

?where=(<field>,<operator>,<value>)

Example

https://<your-nocodb-url>/#/workspaceId/baseID/tableID?where=(country,eq,France)
https://<your-nocodb-url>/#/workspaceId/baseID/tableID/viewID?where=(country,eq,France)

This filters records where the field country is equal to France.

Supported Operators

List of supported operators for filtering across various data types are listed below

• Comparison Operators
• Comparison Sub Operators
• Logical Operators

Combining Filters

Multiple conditions can be joined using logical operators:

• ~and → logical AND
• ~or → logical OR

Example

?where=((country,eq,France)~or(country,eq,Germany))

This retrieves records where country is either France or Germany.

?where=((country,eq,France)~and(status,eq,Active))

This retrieves records where both conditions are true.

Conditions can be grouped using nested parentheses to form complex logic:

?where=(((country,eq,France)~or(country,eq,Germany))~and(status,eq,Active))

Filter Precedence: Toolbar vs URL

This means:

• Filters applied manually via the Filter menu are evaluated first.
• Then, the URL query parameter filters (?where=...) are applied on top of the results.

Visual Indicator: As shown in the screenshot below, the toolbar clearly lists both types of filters:

• The user-applied filter: Segment is equal to Government
• The URL-applied filter: Country is equal to France (listed under URL Filters)

Additional Notes

• Field names must be exact (case-sensitive).
• URL values must be URL-encoded if they include spaces or special characters.