Skip to content

Graph Detail

The graph detail page is the main interface for working with a single graph (formerly called a repo). It lives at /orgs/<org>/graphs/<name>. It combines a header with key metadata, a tab bar for navigating different views of the data, and permission-aware controls for editing.

The top of the page displays:

  • Graph name in large text.
  • Visibility badge — a globe icon for public graphs or a lock icon for private ones.
  • MCP badge — a clickable badge displaying the graph’s Model Context Protocol (MCP) endpoint path. Click it to copy the full MCP URL to your clipboard.
  • Rename button — a pencil icon button (Edit graph details) that opens the Update graph dialog to rename the graph (display name and slug). It is shown only on desktop, and only to users with repo:configure permission (admins and above).

The graph description appears in the Description section of the sidebar on wide screens; on narrower screens that section stacks below the main tab area. Users with repo:configure permission can edit it on desktop with the pencil (Edit about) button next to that heading.

Below the header, tabs organize the graph’s content:

  1. About (default) — README, data dictionary, and sidebar info.
  2. Things — Thing browsing and search. See Things and Wrefs for the data model behind this tab.
  3. Assertions — Assertion browsing with filters and BDU meters. Signed-in viewers may also see source reputation recorded in Veritas for the graph. See Assertions for the underlying data model.
  4. Actions — Webhook subscription management. Only visible to users with repo:configure permission.
  5. Components — Installed components and their configuration. Not available on mobile; opening a ?tab=components link on a mobile device shows the About tab instead.

Non-default tabs are reflected in the URL as a query parameter (for example, ?tab=actions), so you can bookmark or share a direct link to any tab. The default About tab omits the parameter.

Selecting a different graph tab creates a browser-history entry, so Back and Forward retrace the tabs you visited. Drilling into namespace folders on the Things tab also participates in browser history.

Within the Actions tab, you can also deep-link directly to a specific subscription’s detail view by adding a sub=<subscription-name> parameter — for example, ?tab=actions&sub=my-subscription. As with the tab parameter, you can bookmark or share this URL to return directly to that subscription.

You can also deep-link directly to a specific action run by adding a run=<run-id> parameter — for example, ?tab=actions&run=<run-id>. Notification buttons (call-to-action buttons in notification messages) use this format to navigate you straight to the relevant run, and the Actions tab resolves the parameter back to that selected run. You can bookmark or share this URL to return directly to it.

Graph actions are gated by role-based permissions. For background on how authentication works, see Authentication. The table below maps each permission string to the minimum role required:

PermissionMinimum roleGrants
repo:configureAdminManage subscriptions, credentials, rename graph, edit description
things:writeEditorCreate and revise things (including the README)
  • Read access — All tabs except Actions are visible to anyone who can view the graph. Browsing data does not require write access; use wh thing history for per-thing version trails.
  • Actions tab — requires repo:configure (admins and above). Users without this permission do not see the tab.
  • Write access — Different actions require different permission levels:
    • Edit README — requires things:write (editors and above), because the README is stored as a thing and goes through the write path.
    • Rename graph / edit description — requires repo:configure (admins and above). Both controls appear only on desktop.

To view graph metadata from the terminal, use wh graph view. For a full list of CLI commands, see the CLI reference.