---
title: "Relation graphs"
url: https://developers.dagio.ai/graphs/
---

# Relation graphs

   
                        
                                                                    
              
                
          
   

## A graph is a projection

A graph view presents objects as nodes and relations as edges. Use it to explore clients, quotes and associated work. It does not replace the canonical graph or access checks.

| Parameter   | Expected values                         | Description                   |
| ----------- | --------------------------------------- | ----------------------------- |
| Sources     | Declared Query and scope                | Objects permitted in the view |
| Relations   | Admitted types and directions           | Visible connections           |
| Labels      | Declared properties                     | Recognizable text             |
| Layout      | Contract algorithm and options          | Node arrangement              |
| Interaction | Selection, opening and admitted Actions | Explore and act in context    |

## Example

Place North Studio at the center, surrounded by quotes and preparation work. Selecting Q-1042 presents its identity; opening its record uses the same navigation as a table. Removing a relation can only be saved through an authorized business operation.

## Manage scope

Readable graphs require bounds and filters. Loaded object counts, relation direction and navigation controls must be explicit. A node absent from this projection does not establish that the object is absent from the system.

If opening a record fails, its retry opens that same record; reorganizing the graph only changes its layout. A changed work context or a removed or revised record withdraws the old retry. Reopen the current record from its current view; retry never grants access.

Graph controls and feedback follow the interface language. Switching language keeps the current filter, selection and view; it does not reorganize the graph or run a search. Record titles, relation types and layout names authored in the Model keep their original text.

Surface uses the graph component’s native capabilities; [presentation contracts](https://developers.dagio.ai/reference/workspace-graph-presentation/) define admitted variants. [Canvas](https://developers.dagio.ai/canvas/) serves a different purpose: composing free visual content.

## Explore with the assistant

To find information across authorized applications or Spaces, ask for a search and then explore incoming or outgoing links. Results preserve each object’s identity, Fields and exact destination. Full content loads when needed in its owning context.

Continue result pages to expand the exploration. A loaded page represents part of the accessible graph; it does not establish that other information is absent. The owning Space’s instructions and access rights still apply.

<!-- surface-examples:start -->

## Applied examples : Explore the client and its relations

Two visual arrangements present the same linked objects without changing their data.

### Configuration

Fragment placed in `graphPresentations[].profiles[].layout`. [Properties and accepted values](https://developers.dagio.ai/reference/workspace-graph-layout/).

```json
{
  "algorithm": "layered",
  "nodeSpacing": 48,
  "componentSpacing": 64,
  "layerSpacing": 80,
  "direction": "RIGHT",
  "seed": 1
}
```

### Variation and connection

Fragment placed in `graphPresentations[].profiles[].layout`. [Properties and accepted values](https://developers.dagio.ai/reference/workspace-graph-layout/).

```json
{
  "algorithm": "mrtree",
  "nodeSpacing": 56,
  "direction": "DOWN",
  "aspectRatio": 1.5
}
```

### UI layout example

The illustrative layout below places this configuration in the Clients/Quotes app. Insert each fragment at the stated location, with Field, Query and Action references matching the Model declarations.

1. North Studio
2. Quote S-1042
3. Preparation
4. Sources

<!-- surface-examples:end -->