Skip to main content

​
Overview

Views allow you to save different configurations of your table - filters, sorting, column visibility, and column order. Create multiple views to show different perspectives on your data to different teams.

Save Configurations

Save filters, sorts, and column settings

Access Control

Control who can see each view

Multiple Perspectives

Create views for different use cases

Team Collaboration

Share views with specific teams or roles

​
Creating a View

1

Configure Table State

Set up your desired filters, sorting, and column visibility
2

Click Add View

Click the + Add View button in the view tab bar
3

Name Your View

Enter a descriptive name for the view
4

Add Description (Optional)

Add a description to help users understand the view’s purpose
5

Set View Access

Choose who can see this view:
  • Specific Users: Individual user access
  • Teams: All members of selected teams
  • Roles: All users with selected roles
6

Create View

Click Create to save the view

​
What Gets Saved in a View

SettingSavedDescription
Column FiltersYesAll active filter conditions
SortingYesColumn sort order and direction
Column VisibilityYesWhich columns are shown/hidden
Column OrderYesThe arrangement of columns
Column PinningYesPinned columns (left/right)
PaginationYesPage size preference
Global FilterYesSearch text (optional)

​
Managing Views

​
Switching Between Views

Click on view tabs at the top of the table to switch between saved views. The active view is highlighted.

​
Editing a View

1

Select View

Click on the view you want to edit
2

Open Settings

Click the settings icon (gear) on the view tab
3

Select Edit

Click Edit View
4

Modify Settings

Update name, description, or access permissions
5

Save Changes

Click Save to apply changes

​
Saving Changes to a View

When you modify filters, sorting, or column settings while in a view:
  1. A “Save Changes” indicator appears
  2. Click Save for Everyone to update the view for all users
  3. Or discard changes by switching to another view
Only users with edit permission on the view can save changes.

​
Duplicating a View

Create a copy of an existing view to start from a similar configuration.
1

Open View Settings

Click the settings icon on the view tab
2

Select Duplicate

Click Duplicate View
3

Configure Copy

  • Update the name
  • Modify description
  • Adjust access permissions
4

Confirm

Click Confirm to create the duplicate

​
Renaming a View

1

Open View Settings

Click the settings icon on the view tab
2

Select Rename

Click Rename View
3

Enter New Name

Type the new view name
4

Save

Click Save or press Enter

​
Deleting a View

1

Open View Settings

Click the settings icon on the view tab
2

Select Delete

Click Delete View
3

Confirm

Confirm the deletion
Deleting a view is permanent. Users who had access to only this view will need access granted to another view.

​
View Permissions

Control who can access each view separately from table permissions.

​
Setting View Access

When creating or editing a view, specify access by:
Access TypeDescription
UsersSpecific individual users
TeamsAll members of selected teams
RolesAll users with selected roles

​
Permission Levels

PermissionDescription
ViewCan see and use the view
EditCan modify view settings and save changes
DeleteCan delete the view

​
Default View

The first view (or “All Records” view) is typically accessible to all users with table access. Custom views can restrict access further.

​
Use Cases

Create views filtered to show only records relevant to each team:
  • Sales Team View: Filter by assigned_team = Sales
  • Support Team View: Filter by assigned_team = Support
Create views for different workflow stages:
  • Pending Review: Filter by status = Pending
  • Approved: Filter by status = Approved
  • Needs Attention: Filter by priority = High AND status != Complete
Create views for time-sensitive data:
  • This Week: Filter by due_date within current week
  • Overdue: Filter by due_date < today AND status != Complete
Create views with different column visibility:
  • Manager View: All columns visible
  • Staff View: Sensitive columns (salary, cost) hidden

​
FAQs

Users with Creator or Editor permissions on the table can create views.
Users with Creator permissions or explicit delete permission on the view can delete it.
Users with Edit permission on the view can modify settings and save changes.
There’s no limit to the number of views you can create per table.
Click the settings icon and select Reset View to clear all filters and sorting while keeping the view configuration.

​
For AI Agents

​
API: Create View

POST /zorp-tables-service/table/:tableType/views
Authorization: Bearer {secretKey}
Content-Type: application/json

{
  "name": "High Priority Items",
  "description": "Shows only high priority records",
  "state": {
    "columnFilters": [
      {
        "id": "priority",
        "value": "High"
      }
    ],
    "sorting": [
      {
        "id": "due_date",
        "desc": false
      }
    ],
    "columnVisibility": {
      "internal_notes": false
    },
    "columnOrdering": ["name", "priority", "status", "due_date"]
  },
  "access": {
    "users": ["user_123"],
    "teams": ["team_456"],
    "roles": ["role_789"]
  }
}

​
API: Get All Views

GET /zorp-tables-service/table/:tableType/views/
Authorization: Bearer {secretKey}
Response: 
{
  "code": "200",
  "data": {
    "views": [
      {
        "_id": "view_123",
        "name": "High Priority Items",
        "description": "Shows only high priority records",
        "isActive": true,
        "body": {
          "colDef": {...},
          "rowDef": [...]
        }
      }
    ]
  }
}

​
API: Get Specific View

GET /zorp-tables-service/table/:tableType/views/:viewId
Authorization: Bearer {secretKey}

​
API: Update View

PATCH /zorp-tables-service/table/:tableType/views/:viewId
Authorization: Bearer {secretKey}
Content-Type: application/json

{
  "name": "Updated View Name",
  "state": {
    "columnFilters": [...]
  }
}

​
API: Save View State

PUT /zorp-tables-service/table/:tableType/views/:viewId
Authorization: Bearer {secretKey}
Content-Type: application/json

{
  "state": {
    "columnFilters": [...],
    "sorting": [...],
    "columnVisibility": {...},
    "columnOrdering": [...]
  }
}

​
View State Structure

interface ViewState {
  columnFilters?: { id: string; value: unknown }[];
  sorting?: { id: string; desc: boolean }[];
  columnFilterFns?: { [id: string]: string };
  pagination?: { pageIndex: number; pageSize: number };
  columnPinning: { left: string[]; right: string[] };
  columnVisibility?: { [id: string]: boolean };
  columnOrdering?: string[];
  globalFilter?: string;
  showGlobalFilter?: boolean;
  showColumnFilters?: boolean;
}

​
UI Elements

ElementLocationPurpose
View TabsBelow toolbarSwitch between views
Add View ButtonView tab barCreate new view
View SettingsView tabEdit/Delete/Duplicate
Save ChangesToolbarSave view modifications

​
Event Tracking

ViewsRSEvents.ADD_NEW_VIEW_BUTTON_CLICKED
ViewsRSEvents.CREATE_NEW_VIEW_BUTTON_CLICKED
ViewsRSEvents.CREATE_VIEW_SUCCESS
ViewsRSEvents.CREATE_VIEW_FAILURE
ViewsRSEvents.DELETE_VIEW_BUTTON_CLICKED
ViewsRSEvents.DELETE_VIEW_SUCCESS
ViewsRSEvents.UPDATE_VIEW_SUCCESS
ViewsRSEvents.DUPLICATE_VIEW_BUTTON_CLICKED
ViewsRSEvents.DUPLICATE_VIEW_SUCCESS
ViewsRSEvents.SWITCHED_TO_DIFFERENT_VIEW
ViewsRSEvents.SAVE_THIS_VIEW_BUTTON_CLICKED
ViewsRSEvents.SAVE_THIS_VIEW_SUCCESS

​
State Persistence

View states are cached in localStorage: 
Key: tableState_${tableType}_${viewId}
This allows quick restoration when switching between views.