> ## Documentation Index
> Fetch the complete documentation index at: https://docs.meetsquad.ai/llms.txt
> Use this file to discover all available pages before exploring further.
# Relationships
> How entities connect to each other, which of those links are yours to change, and what removing one actually does.
Squad stores connections between entities as links, never as copies. A signal is not duplicated into
the insight it supports. The insight points at it. That is why you can open a one-pager, follow it
back to the insight, then to the signals, then to the customer sentence that started the whole
thing, and find nothing has been paraphrased on the way.
You read those links on detail pages. Every entity page carries panels listing what it connects to,
and each of those panels is a table you can open, sort, and act on.
## Where relationships show up
**Representative data signals** shows up to three quote cards, with **View all** opening the
full table when there are more. The right column holds **Goals** (the goals this insight
supports) and **Referenced by** (one-pagers and knowledge documents whose body cites it).
**Cluster** names the theme the signal was grouped into, with the member count. **Related data
signals** shows the nearest neighbours. **Insights** lists what the signal helped produce, which
is the panel that tells you whether the evidence went anywhere. **Referenced by** works the same
as on an insight.
The member signals appear as quote cards, and past a handful of members they also render as a
paginated table. **Insights** in the right column lists what Squad synthesised from the group.
**Insights** lists the top five insights attached to the goal, with **Manage** (or **View all
N** past five) opening the complete list in a dialog.
Rows behave the same everywhere. Click one to open it. Right-click for **Open**, **Copy ID**, **Copy
URL**, and **Copy content as JSON**, plus **Remove** on the tables where the link is yours to
change.
## What can link to what
Six kinds of link can be created or removed on demand, whether you do it or Squad does it on your
behalf. Each has a fixed direction.
| Link | Direction |
| --------------------------------------------------------------- | -------------------- |
| A knowledge document informs an insight | Document to insight |
| An insight supports a goal | Insight to goal |
| An insight is related to another insight | Insight to insight |
| An action belongs to an insight | Action to insight |
| A one-pager is derived from an action | One-pager to action |
| A one-pager cites an insight | One-pager to insight |
Anything outside that list is refused. You cannot attach a goal straight to a data signal, and you
cannot link two goals to each other. The pipeline's own connections sit outside this set entirely. A
signal joins a cluster and a cluster produces an insight as the evidence moves, and neither is
something you edit.
## The link you make yourself
Of those six, one is under your control in the app: an insight supporting a goal. You can set it
from either end.
The **Goals** panel on the right of an insight page has **Link goals**, which reads **Manage
links** once at least one goal is attached. The dialog lists your goals with a search box at the
top. Press **Link** on a goal to attach it. An attached goal shows **Linked**, and hovering that
button turns it into **Unlink**. Goals cannot be created here. If the workspace has none, the
dialog says so and points you at the Goals page.
The **Insights** section on a goal page has **Add insight** when nothing is attached, **Manage**
when five or fewer are, and **View all N** beyond that. All three open the same dialog. **Add
insight** inside it opens a search popover, typing filters the list, and insights you have
already attached are left out of the results. Insights are not creatable from here either. Squad
writes them from evidence, so there is nothing sensible to type into existence.
Ask the assistant to link an insight to a goal and it will, using the same rules. See [The chat
assistant](/chat-assistant).
## Removing a link
On the goal page, right-click an insight row and choose **Remove from this Goal**. A confirmation
appears, headed with the reference you are about to detach (**Remove IN-42?**), and it spells out
what will happen: the link goes, the entity stays, and you can re-link it later. In the insight's
goal dialog, hovering a **Linked** button turns it into **Unlink** and one click detaches it with no
confirmation step.
Removing a link destroys nothing. The insight keeps its title, its description, its supporting
signals, and its score. The goal keeps its title, its importance, and every other insight attached
to it. Scores come from evidence alone, so detaching a goal will not move a single number on the
Insights page. What changes is relevance. Squad reads your goals when it ranks actions for an
insight, and an insight attached to nothing gets no help from that. See [Goals](/goals).
Squad decides which goals an insight supports when it first creates the insight. If you remove a
link Squad wrote, it stays removed. Fresh insights arriving later are matched against your goals as
usual.
## What Squad links on its own
Most of the chain is written for you. Signals join clusters as they arrive, clusters produce
insights, and those insights carry a link back to every signal behind them. When a new insight comes
out close to an existing one but distinct, Squad creates it with a "related to" link to its
neighbour instead of merging the two.
Actions are created against the insight they answer. Generate a one-pager from an action and the
document keeps a link to it, plus a citation to the insight it argues from. Reference a `SI-`,
`IN-`, `GL-`, or `OP-` chip anywhere in a document body and the reference becomes a link, which is
what fills the **Referenced by** panel on the entity you mentioned. Delete the mention and the link
goes with it.
See [The evidence pipeline](/pipeline) for the full chain.
## Cookbook
**Find the strategy gap.** On the Insights list, filter **Goals** to 0 and sort by score descending.
Anything scoring well with no goal attached is either an insight nobody has connected or a gap in
what you wrote down as strategy. Attach it from the insight's **Goals** panel, or rewrite the goal
so it says something specific enough to match.
**Prune a goal that has collected the wrong evidence.** Open the goal, choose **Manage**, and read
the attached insights. Remove the ones that do not belong. What remains is the case for the goal,
and it is the list you can walk in a planning meeting.
**Trace a decision back to a quote.** Open the one-pager, follow the insight it cites, open that
insight's supporting signals, and read the original text on any signal detail page. Every hop is a
link, so nothing along the way was rewritten.