> For the complete documentation index, see [llms.txt](https://docs.scaleconnect.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleconnect.com.au/api/knowledge-graph.md).

# Knowledge graph

Traverse a fictional broker workspace and understand its records and relationships.

Explore a fictional broker workspace using the same graph canvas, record icons and controls as ScaleConnect. Start with **Gravity**, then try **Clusters**, **Minimap**, **Left to right**, or **Radial** from the view menu inside the frame.

{% hint style="info" %}
**Interactive example.** These records are fictional. The example needs no sign-in and makes no workspace API calls. To explore your own records, use Knowledge Base in your signed-in ScaleConnect workspace when the feature is enabled.
{% endhint %}

{% @scale-knowledge-graph/workspace-explorer %}

## Try a traversal

1. Select **Amelia Thompson** on the graph, or use **Browse records** in the toolbar.
2. Follow **has strategy → Current position**, then **includes property → 14 Willow Street**, then **has loan → Home loan · variable**.
3. Use **Previous record** in the details pane to retrace your steps.
4. Choose **Focus connections** to isolate a record's context, and **Show workspace** to return.
5. Search **ANZ**, **Amelia**, or **meeting**. Use **Reset graph** to clear the search and selection.

Search in this example matches the phrase you enter against fictional labels, record types, descriptions and properties. The graph shows matches with their connected context. The [workspace search guide](https://docs.scaleconnect.com.au/scaleconnect-docs/workspace/knowledge-base/search) explains the signed-in product's saved-content search and its limits.

## Choose a view

| View          | Use it to                                                                              |
| ------------- | -------------------------------------------------------------------------------------- |
| Gravity       | Explore connections arranged by a shared force layout. Drag a record to reposition it. |
| Clusters      | See client groups inside their mesh outlines.                                          |
| Minimap       | See the workspace as a compact map.                                                    |
| Left to right | Follow directed connections across record types.                                       |
| Radial        | See connections arranged by distance from the focus.                                   |

Zoom, fit and the overview minimap stay inside the frame. Click the overview to move around the graph, or focus it and press **Enter** to fit. **Browse records** provides a keyboard-accessible list on desktop and mobile.

## Read the tree

This text tree summarises the example's hierarchy. A graph can contain cross-links and multiple parents; changing the layout does not add, remove or reverse relationships.

```
Workspace
├── Team
│   ├── Broker
│   └── Client
│       ├── Strategy
│       │   ├── Property
│       │   │   └── Loan
│       │   └── Entity
│       ├── Document
│       ├── Meeting
│       │   └── Transcript
│       └── Memory
├── Task ── for client ──→ Client
│        └─ assigned to → Agent
└── Agent
```

A name mentioned in a document or transcript can match a keyword search; the mention alone does not prove a saved relationship.

## Understand records and relationships

| Component    | Meaning                                                                             |
| ------------ | ----------------------------------------------------------------------------------- |
| Record       | One workspace item, such as a client, strategy, property, task or document.         |
| Record type  | The kind of item represented by the node, using its familiar product icon.          |
| Relationship | A directed connection with a named meaning, such as `HAS_STRATEGY` or `FOR_CLIENT`. |
| Selection    | The current record and the connections available to follow in its details pane.     |
| Layout       | A different arrangement of the same records and relationships.                      |

For example, a loan has an incoming relationship from its property:

```json
{
  "record": {
    "id": "example:loan",
    "kind": "loan",
    "label": "Home loan · variable"
  },
  "relationships": [
    {
      "source": "example:property",
      "type": "HAS_LOAN",
      "target": "example:loan"
    }
  ]
}
```

This small JSON illustration explains the relationship. Its identifiers and shape are not request parameters or a guaranteed API response schema.

## Explore your workspace

The product guides live in **Docs → Workspace → Knowledge Base**:

* [Explore your workspace knowledge graph](https://docs.scaleconnect.com.au/scaleconnect-docs/workspace/knowledge-base)
* [Choose a graph view](https://docs.scaleconnect.com.au/scaleconnect-docs/workspace/knowledge-base/views)
* [Search saved workspace content](https://docs.scaleconnect.com.au/scaleconnect-docs/workspace/knowledge-base/search)
* [Create tasks and understand live updates](https://docs.scaleconnect.com.au/scaleconnect-docs/workspace/knowledge-base/updates)
* [Troubleshoot missing graph records](https://docs.scaleconnect.com.au/scaleconnect-docs/workspace/knowledge-base/troubleshooting)

## About the embed

This interactive block runs inside GitBook with bundled fictional data. Gravity is the starting view on desktop and mobile. Search, layout, record details and navigation controls are contained in one rounded frame.

The example does not provide access to a customer's own Knowledge Graph API. A live integration would need an authenticated connection that enforces the customer's workspace permissions and an explicitly supported API contract.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.scaleconnect.com.au/api/knowledge-graph.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.