Skip to main content
Beta

How Graph One works

Turn supported relationship records into people, answers and shared work

Start with supported Google or Microsoft accounts and supported LinkedIn or X archive imports. Review how Graph One links identifiers into people, exposes uncertain pairs, finds paths and Search results, then keeps the answer in Tables or Boards.

The result

The team can find a person, inspect why the result or route may be useful, and give the next action an owner without moving the work into a separate copy.

Source data, history, refresh rules, and permissions vary by connection. Network OS and Kernel set who owns the interface; Kernel account, integration, deployment, and support terms need an agreed scope.

One source-to-work sequence

See what changes at each step

Connect a supported source, review identity, find a person or route, and keep the answer in work the team can own. Every view below uses local sample data.

01

Sources

Start with supported source states

Google and Microsoft accounts and supported LinkedIn or X archive imports have different history, refresh and permission rules. The status parts below are the same parts a signed-in team reviews.

Google

Supported account

Microsoft

Supported account

LinkedIn

Supported archive

X

Supported archive

Current source-status parts · Local sample data. History, refresh, available records, and required rights vary by source and account.

02

Identity

Resolve identifiers and keep uncertainty reviewable

Canonical ID can link supported identifiers into one person. When the evidence is uncertain, the team can review the pair instead of treating an automatic match as final.

Loading the identity review proof
03

Paths and Search

Find a route, then ask the right kind of Search question

Inspect direct and indirect relationship context, build an exact query, or review an evaluative result and its reason. Graph One supplies evidence; the team keeps the judgement.

Loading the relationship and Search proof
04

Shared work

Turn the answer into Table or Board work

Keep fields, owner, next step, comments, activity and access beside the linked person or organisation instead of sending a copy to another tool.

Loading the Table, Board, comment and access proof
05

Product boundary

Choose who owns the interface

The result and work model stay the same; the customer choice is where the Graph One interface sits.

Network OS

Use the full Graph One product with your team

Find people, inspect relationship context, and keep the next step in shared Tables or Boards inside Graph One.

See Network OS

Kernel

Put agreed capabilities behind your own interface

Map Graph One's current people, Search, Table, Board and OAuth services to your customer flow, then agree data, integration, deployment and support terms.

Review Kernel

See what your setup would take

Check which sources you can connect, how sharing and protection work, and whether your team needs Network OS or Kernel.