> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/admin/workplace/connections.md).
# Connections
## Overview of the Connections tab in Planning
Gain an overview of all global connections within your division. It enables a detailed view of the relationships between different entities, helping you manage and understand how people and teams are linked across the locations in your division.
**Navigation and Views**
* **Connection Graph:** This provides a visual map of all connections, filterable by location. It simplifies the understanding of complex relationships and dependencies which AIDRA considers when allocating space.
* **List View:** For a more straightforward, detail-focused perspective, this view displays all connections in an actionable format.
## **Key Features of the Connections Tab**
* **Filtering Options:** You can filter both the graph and list views by specific locations to focus on connections relevant to the allocations you're currently monitoring, or unselect a location to see all global locations.
**Connection Management in List View:**
* **Detailed Information:** Each row displays the origin and endpoint entity of a specific connection, its strength.
* **Colour Coding:** Connection strengths are colour-coded—green for positive and red for negative—providing an insight into the nature of each relationship without clicking into it.
* **Ability to Delete:** You can delete any connection directly from the list if it is no longer needed.
---
# 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.gospace.com/admin/workplace/connections.md?ask=&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.
