Skip to main content

Exploring your graph

After discovery runs, your organization's systems show up as an interactive knowledge graph: entities as nodes, relationships as edges. This is where you see what SixDegree found.

Prerequisites​

You need a populated graph. Make sure you've:

  • Created an environment
  • Configured at least one integration (GitHub, AWS, and so on)
  • Run discovery at least once

If discovery hasn't run yet, start with your first environment.

Opening the graph​

Navigate to your environment at app.sixdegree.ai. The graph view loads by default on the main dashboard. Entities appear as nodes and relationships as edges, with color encoding the entity type: code, infrastructure, teams, customers, and so on.

  • Zoom: mouse wheel or scroll gesture.
  • Pan: click and drag the background.
  • Inspect: click any node to open its details.
  • Reset: Fit to view re-centers and zooms to show everything.

Filter to cut clutter. Toggle entity types on or off to focus. For example, hide contacts to see only accounts and their subscriptions. Use the search box to jump straight to an entity by name. The graph highlights and centers on the match.

Entity details​

Click a node to open its detail panel:

  • Identity: name, type, the integration that discovered it, and when it was first seen and last updated.
  • Properties: everything specific to that entity: URLs, endpoints, configuration, and metadata from the source system.
  • Relationships: outgoing (this entity → others) and incoming (others → this entity).

Reading the graph​

A few patterns surface quickly once you have real data:

  • Ownership: reps owning accounts, accounts holding subscriptions, teams owning repositories (OWNS, BELONGS_TO).
  • Customer chains: an account joined to its opportunities, subscriptions, support tickets, and the incidents behind them.
  • Dependency networks: tickets escalating into incidents, opportunities depending on usage, services depending on services (DEPENDS_ON).
  • Hubs and orphans: highly connected nodes are often your largest accounts or most critical components. Isolated nodes may be unused resources or contacts with no activity.

Exploring by scenario​

What's tied to an account?​

Search for the account, select it, and follow its outgoing relationships to see its opportunities, subscriptions, contacts, and open support tickets in one view.

What's the risk behind this ticket?​

Select a ticket and read its edges both ways: outgoing shows the incident it escalated into, incoming shows the account and subscription it puts at risk. Follow the chain to gauge the revenue exposure of a single breach.

What's the blast radius of this service?​

Select a service and read its DEPENDS_ON edges both ways: outgoing shows what it relies on, incoming shows what relies on it. Follow the chain to gauge the impact of a change.

What's orphaned?​

Look for isolated nodes with few or no connections. These are often contacts with no recent activity, vendors no team uses, or forgotten resources worth cleaning up or documenting.

Refreshing data​

Discovery runs on each integration's configured schedule, and the graph updates automatically as new entities are found. For an immediate refresh, trigger discovery manually from Environment Settings, where you can also see when each integration last ran.

Troubleshooting​

SymptomWhat to check
No entities visibleDiscovery has completed; filters aren't hiding everything; integrations are configured; credentials are valid.
Graph won't loadRefresh the page, clear your browser cache, filter to reduce the node count, or check the browser console for errors.
Can't find an entityIt exists in the source system; the integration discovers that type; your search term and the type filter aren't excluding it.

Next steps​