YipiiYipii Mobility Docs
Features

Saved Views

Pin your filter, sort, and search combinations on every list page so your team starts each day on the right view.

Saved Views

Saved views capture the filter, sort, and search state on a list page so you can recall it in one click later. Once you've set up a useful filter combo — "open critical issues this week", "fuel logs over €100 last month", "drivers with expiring licenses" — save it as a view and pin it for everyone in your team.

Saved views are available on every major list page in Yipii Mobility, including:

Assets · Work Orders · Inspections · Issues · Tasks · Drivers · Vendors · Parts · Expenses · Documents · Licenses · Recalls · Service Schedules · Service Tasks · Service Kits · Site Locations · Diagnostics · Purchase Orders · Warranties · Fuel Logs

Why Saved Views

Without saved views, every team member rebuilds the same filter combinations every morning. With them:

  • Daily triage starts on the same view your team agreed on yesterday
  • New hires see the right slice on day one — no "how did you set that up?" tutorial
  • Cross-team workflows stay aligned ("look at the Critical Open view")
  • Reports built from a list export start from the same baseline data

Where Views Live

Saved views are scoped per user × tenant × entity. Your "open critical issues" view on the issues page is yours alone — your colleague has their own list, even on the same page. Sharing views across users is on the roadmap; for now everyone sets up their own.

Anatomy of a View

Each view captures three things:

  • Filters — every active column filter on the page (status, priority, type, category, etc.)
  • Sort — current sort column and direction
  • Search — current free-text search query

Pagination, page size, and column visibility are not captured — those are session-scoped.

Saving a View

The saved-view selector lives in the toolbar of every list page (right side, before the export button).

To save the current state:

  1. Set up the filters, sort, and search the way you want
  2. Open the saved-views dropdown in the toolbar
  3. Click Save current view
  4. Give it a name — short, action-oriented ("This Week's Critical", "Overdue Inspections")
  5. Optional: tick Set as default to make this the view the page opens with on next visit

The view is saved to your account and immediately available from the dropdown.

Applying a View

Open the dropdown, click the view name, and the page snaps to that filter set. Anything you had configured before is replaced by the saved state.

The active view's name shows in the toolbar so you can tell at a glance whether you're looking at a saved view or an ad-hoc set of filters.

Default Views

Mark any view as the default for an entity to have the page open with that view applied automatically on first load. Useful for:

  • Hiding cancelled / closed records by default
  • Pre-filtering to only your assigned items
  • Always sorting by due date instead of the column default

You can have one default per entity. Setting a new default unsets the previous one.

Default vs active

The default is what the page opens with. The active view is whatever's applied right now — which may be the default or any other view you switched to. Refresh the page to snap back to the default.

Renaming, Updating, Deleting

From the saved-views dropdown:

  • Rename — click the pencil icon next to a view name
  • Update — recall the view, adjust filters, then click "Update (view name)" to overwrite the saved state
  • Delete — click the trash icon next to a view name; confirm the irreversible delete

Permissions

Every authenticated user can manage their own saved views. There's nothing to configure at the role level — saved views are personal preferences, not org-wide policy.

RoleSaved Views Access
Any role with list-page accessFull CRUD on their own saved views

Best Practices

  • Name views by intent, not by filter spec. "This Week's Critical" beats "status=open AND priority=critical AND created_at>=2026-04-21".
  • Keep the default lean. Make the default view the one you'll glance at most often; save more specific cuts as named non-default views.
  • Curate, don't hoard. A dropdown of 30 views is harder to use than 5 well-named ones. Prune views you haven't used in a while.
  • Use them with exports. Save a view, set it active, then click Export — the CSV reflects the filtered set, not the whole table.
  • Pair with bulk actions. A saved view + bulk select + bulk action is the fastest path through repetitive triage.

FAQ

Are saved views shared with my team? Not yet — they're per-user. Org-shared views are on the roadmap.

Can I save a view without column filters, just a sort? Yes. A view captures whichever of filters / sort / search are currently set. An empty filter set with just a sort order is a valid view.

What happens if I delete a column or feature that one of my views filters on? The view becomes a no-op for that filter — it's safely ignored. The view itself still applies any remaining filters and the saved sort.

Why doesn't my view persist column visibility / page size? By design — those are session-scoped UI preferences, not data filters. We may extend views to capture them in a later release.

Can I export a view as a URL to share with a teammate? Not yet. For now, agree on a view name and have your colleague save the same combo on their account.

  • Every list page in the dashboard supports saved views — pick a feature in the sidebar and look for the saved-views selector in the toolbar.

Need Help?

Contact your organization administrator or the Yipii support team for assistance with saved views, export workflows, or recommendations on view structures for your team's daily triage.

On this page