/help/notifications

Loading…

Help center

All topics & search Table of contents Getting startedWhat GraphVM is, the console and dashboard, search, and building your first graph.Graph editorThe editor views, drawing and wiring nodes, the inspector, graph info pages, and checks.Nodes & catalogBrowsing node types, scopes, the connection taxonomy, and reusable nodes.Running & debuggingRun configuration, breakpoints, run pages, logs and output, and controlling live runs.AI generationDescribing a workflow in prose and refining the graph the builder produces.Credentials & modelsAPI keys for integrations, secret references, and LLM access and budgets.Workspace & adminWorkspace defaults, users and teams, billing, security, your profile, and the audit log.ReferenceKeyboard shortcuts, glossary, and pointers to the API documentation.

Reachable from Help → Help center, or press ⌘K and search.

Help center/Workspace & admin

Notifications

The header bell and the full inbox — where run and workspace events land.

In the app

Notification inbox

The bell in the header shows recent notifications with an unread count; /notifications is the full inbox for reading and clearing them.

Notifications point back at the thing they are about, so a run notification opens that run.
Desktop notifications are opt-in and require the browser's permission prompt to be accepted.

Related

Read run history and tracesRunning & debuggingThe runs list, per-run traces and logs, and the run pages hanging off a graph.
Workspace settings and defaultsWorkspace & adminTenant-wide defaults — theme, default graph scope, experimental nodes, editor grid snap — plus agent health.

More in Workspace & admin · Search all help