> For the complete documentation index, see [llms.txt](https://compassly.gitbook.io/compassly-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://compassly.gitbook.io/compassly-docs/administration/system-settings/connections.md).

# Connections

**Audience:** Super Admin, Admin, Supervisor\
**Page type:** Overview\
**Status:** Draft\
**Owner:** Compassly Documentation Team\
**Last verified:** 2026-04-03

## Purpose

Use **Connections** to control which users, clients, locations, services, and teams are linked to each other in Compassly.

## What connections control

Connections act as the gate to access.

Examples:

* If a **team member** is assigned to a **location**, that team member can access the clients at that location.
* If a **client** is assigned to a **location**, that client is connected to the team members at that location.
* If two **team members** are assigned to the same **team**, they are connected to each other.
* If two users are **not connected**, they should not have access through that connection path.
* A manual **peer connection** can connect people directly even when they do not share the same team or location.

## Before you start

* You must be signed in to Compassly.
* You must be able to open **System settings → Connections**.
* Connections are role-based:
  * **View connection list:** Super Admin, Admin, Supervisor
  * **Assign / unassign / batch assign / batch unassign:** Super Admin, Admin
  * **Assign all new:** Super Admin only
* In many views, the system will prevent an unassign action if it would remove the last required connection for a user.

## How to get there

1. Sign in to Compassly.
2. In the left navigation, select **System settings**.
3. Select **Connections**.

## Connection types

The landing page lets you choose one connection type at a time:

* **Clients to team members**
* **Team members to team members**
* **Locations to users**
* **Services to team members**
* **Teams to team members**

## How the landing page works

On the landing page, you select:

* **Connection type**
* **Access type**
* then click **Apply**

The center switch button in the **Access type** control flips the direction of the connection view.

Examples:

* **Client → team members** can be flipped to **Team member → clients**
* **Team → team members** can be flipped to **Team member → teams**

## Common controls used across connection views

Most connection views use the same front-end controls:

* a main filter for the selected user, client, location, service, or team
* an optional secondary filter such as **Locations** or **Teams**
* a **Search** box
* **Include inactive**
* an **Assign status** dropdown:
  * **Currently assigned**
  * **Currently not assigned**
* row actions
* pagination and page-size controls
* optional batch action buttons

## Important behavior across connection tables

* **Currently assigned** is the default view.
* Search, sorting, and filters stay applied while you use row actions.
* Selected rows stay selected across pagination and sorting.
* Selected rows reset when table filters change.
* The **All** checkbox selects only the current page, not all pages.

## Sections in this guide pack

* [Choose Connection Type and Direction](/compassly-docs/administration/system-settings/connections/choose-connection-type-and-direction.md)
* [Clients to Team Members](/compassly-docs/administration/system-settings/connections/clients-to-team-members.md)
* [Team Members to Team Members](/compassly-docs/administration/system-settings/connections/team-members-to-team-members.md)
* [Locations to Users](/compassly-docs/administration/system-settings/connections/locations-to-users.md)
* [Services to Team Members](/compassly-docs/administration/system-settings/connections/services-to-team-members.md)
* [Teams to Team Members](/compassly-docs/administration/system-settings/connections/teams-to-team-members.md)

## What happens next

Start with **Choose Connection Type and Direction** if you are new to this module. Then open the specific connection-type folder that matches the workflow you need.

## Related guides

* [Choose Connection Type and Direction](/compassly-docs/administration/system-settings/connections/choose-connection-type-and-direction.md)
* [Locations](/compassly-docs/administration/system-settings/locations.md)
* [Roles](/compassly-docs/administration/system-settings/roles.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://compassly.gitbook.io/compassly-docs/administration/system-settings/connections.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
