Saved views

Это содержимое пока не доступно на вашем языке.

A view is an admin-curated saved filter on the Cars page. Each view bundles:

A row filter (status, location, currency, date range, group).
A set of visible columns and their order.
Cost-redaction flags — what cost fields to blank for the people bound to this view.
Per-role bindings — which roles see the view in their tab strip.

Every company has a default “All cars” view (slug all, system-default, can’t be deleted). Owners and Admins always see every view.

Why views matter

Sales reps shouldn’t see cost. Yard managers shouldn’t see customer pricing. With views you can:

Create a “Showroom A” view bound to the Sales role with hideTotalCost = true + showOfferingPrice = true.
Create a “Korea Yard” view bound to the Korea Manager role with location filter = Korea + cost columns visible.

The rep sees only their view’s cars with cost blanked; the manager sees their yard’s cars with full pricing. Owners and Admins see both views in their tab strip.

Creating a view

On /cars, click + New view at the right of the tab strip.
Name it. Slug auto-generates from the name; editable.
Set the row filter (status, location, etc.).
Configure visible columns + drag-and-drop reorder.
Set cost-redaction flags.
Bind roles. Each binding has a single Visible toggle and an Offering price toggle (controls who can edit internalOfferingPrice on rows in this view).
Save.

Offering price (internal)

Distinct from listingPrice (the public marketplace price). It’s the price your sales rep should quote to a buyer. Editable inline in the cars table for users whose bound view has canEditOfferingPrice = true.

URL behavior

Each view has its own URL: /cars/all, /cars/showroom-a, /cars/korea-yard. Linking to a specific view scopes the visible cars accordingly. Users without a binding to that view see “all cars” instead.