> ## Documentation Index
> Fetch the complete documentation index at: https://www.docusnap.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Relationships

> What a relationship is, where it comes from, and where it shows up in Docusnap365.

A relationship connects an asset to another asset or to an entry from
another module — a risk, a control, a document. Every detail page carries
its own *Relations* tab for this.

## Origin of relationships

Relationships sit in two separate zones, depending on how they came about:

| Zone | Origin |
| - | - |
| *Defined Relations* | created by hand |
| *Detected Relations* | determined automatically, for example from a scan |

Only relationships you created yourself can be edited or deleted —
relationships detected from a scan are information only.

<Note>
  If a relationship belongs to a type that has been disabled in the data
  model, or if the permission for the target is missing, the row stays visible
  but cannot be opened — the detail page is unreachable. This applies to
  defined and detected relationships alike.
</Note>

## Relation type and direction

A relation type carries two labels, one per direction — "Assigned to" from
the source's point of view can read "Assigned by" on the other end. An
arrow shows the direction; a bidirectional relation type shows a double arrow.

For some combinations of source and target type, Docusnap365 determines the
relation type automatically — you then only choose the target, Docusnap365
sets the type. Which relation types exist is listed under
[Relation types](/docs/en/assets/relation-types).

## Critical

A relationship can be flagged *Critical*. The flag is information only — it
attaches to the relationship itself and has no effect on any evaluation
outside the relationship list.

## Relation objects

A relationship can carry further entries of its own — *relation objects*. Example:
a relationship "Assigned to" carries, as a relation object, the item
through which the assignment was made. Each relation object gets its own
relation type, its own *Critical* flag, and its own description.

## Where relationships show up

Besides the *Relations* tab itself, the *Relation Map* shows an
asset's relationships as a diagram — see
[Create and edit relationships](/docs/en/assets/relations-edit). ISMS and ITAM
show selected relationships in their own tabs as well, for example
Risk › Assets or Control › Objectives.

## Related

[Create and edit relationships](/docs/en/assets/relations-edit) and
[Relation types](/docs/en/assets/relation-types).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.