The Context Graphs Manager is where Enterprise Context Graph opens: a table of every context graph in your workspace, with a button for starting a new one. From here you open a graph to build it out, or manage an existing graph's sharing, status, and lifecycle.
Overview
A context graph is the unified entity layer your agents reason on — node types (like Account, Contract, or Ticket), the edges connecting them, and the sources feeding real records in. Graphs live inside a project, so the manager opens within your current project. If the module isn't in your sidebar, ask your workspace admin — visibility depends on navigation setup.
Reading the graphs list
Graphs appear as rows in a table — there's no card or grid view. The columns are:
Graph — the graph's name.
Status — Draft or Live.
Version — how many times the graph's contents have changed.
Nodes, Edges, and Sources — counts for each.
Shared with — Everyone, Only me, a group's name, or a combined count of users and groups.
Owner and Last Updated.
Search by name, or sort by the Graph or Last Updated headers; the list loads more rows as you scroll. The toolbar adds a refresh button, Filter and Sort menus, and a columns menu revealing two hidden columns — created time and last-modified-by. There's no ready-made status filter, so build one in Filter if needed. Treat "Everyone" in Shared with cautiously — it also shows while sharing data is still loading. Click a row to open it; rows preload on hover for a fast open. An empty workspace shows "No graphs yet."
Creating a graph
Select Create New Graph. Enter a Graph name and a short Description (it appears on the graph's card), then choose a starting point:
Start blank — an empty canvas where you add node types and edges yourself.
Choose from template — begin from a curated blueprint and customize it.
A template opens a searchable gallery with industry and function filters, and each template lists the node types it creates. Confirming a template, or creating a blank graph, lands you on the new graph's detail page.
Draft and Live status
Every graph starts as Draft. Publishing flips it to Live, and it stays Live — there's no unpublish; publishing again just takes a fresh snapshot. A partial-publish failure returns the graph to Draft automatically.
Publishing and what Version means
The Publish button, in a graph's header, marks it Live and snapshots the schema — node types and edges — stamped with the current version. Records aren't part of the snapshot; they keep flowing in as sources sync, published or not. Publishing a source (which starts its sync) is separate from publishing the graph — do both for a graph that's fully live.
The Version column is a change counter, not a release count: it rises with every added, edited, or removed node, edge, or source. Publishing doesn't increase it — a snapshot just records the version it was taken at.
Edit, share, and delete a graph
Open a row's menu to find Edit, Share, and Delete:
Edit renames the graph and updates its description — it can't touch status, counts, or sharing.
Share opens the same dialog as the graph header: search for people, teams, or application users to add, then assign each a role. Revoke access from their role dropdown.
Delete asks you to confirm, then removes everything — schema, sources and their published snapshots, edges, node types, and records. You need delete access to the graph and every connected source, or it's refused.
Notes
Publish, Share, and Delete stay clickable regardless of permissions — errors appear only if you act without access.
Node record counts refresh roughly every two minutes and can lag briefly; list-level Nodes, Edges, and Sources counts update immediately.
There's no duplicate, archive, or pause action — deleting is the only way to remove a graph.
Most create, edit, and delete actions finish silently — only Publish confirms.