Bookmarks

Save and restore graph views in your browser

Bookmarks save a named view of one graph. Use them when you want to return to a useful filter and group configuration without rebuilding it.

What a bookmark saves

A bookmark contains:

  • the bookmark name and optional description
  • the active filter stack
  • the expanded and collapsed group state

It does not save selected nodes or the camera position.

Create or update a bookmark

Press Ctrl+B (Windows/Linux) or Cmd+B (Mac), or use Bookmark View in the viewer toolbar.

The bookmark dialog can create a bookmark or replace an existing bookmark with the current filters and group state. A name is required. The dialog shows how many filters and group states the snapshot contains.

Apply a bookmark

The Bookmarks panel lists the bookmarks for the current graph. Each entry shows its filter count, group-state count, and description when present.

Applying a bookmark replaces the current filters and group state. Schematify asks for confirmation first when either is already active.

Manage bookmarks

From the Bookmarks panel, you can:

  • rename a bookmark and edit its description
  • update it with the current graph state
  • apply it
  • delete it after confirmation

Deleting a bookmark cannot be undone.

Browser-local storage

Schematify stores bookmarks in your browser’s local storage under the graph ID. As a result:

  • each graph has its own bookmarks
  • bookmarks persist across sessions in the same browser profile
  • bookmarks do not sync to another browser, device, or team member
  • clearing site data removes them

Schematify does not currently provide a bookmark export or sharing workflow.

Bookmarks and smart filters

A bookmark preserves both node filters and query-based smart filters. Smart filters run their query again when the graph document changes or a resolved channel value changes. Queries can target realtime data explicitly with channels.<key>; free text still excludes channel values.

If a saved historical query is no longer valid, Schematify keeps the filter visible with an error and selects no nodes rather than changing the query.

What’s next