> For the complete documentation index, see [llms.txt](https://learn.heeler.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.heeler.com/tenant-admin-guide/connections/trusted-connections.md).

# Trusted Connections

## Approving Outbound Third-Party Connections

**Trusted Connections** are outbound connections from your environment to external services that you've explicitly approved as safe. This complements Vendor Connections — Vendor Connections is *what's there*, Trusted Connections is *what you've signed off on*.

### Where to find it

Administration → **Connections** → **Trusted Connections** in the left sidebar.

URL: `https://app.heeler.com/administration/connections/trusted_connections`

### Quick start

1. Click **Add Trusted Connection** in the top-right.
2. Identify the third-party connection you want to mark trusted (typically by selecting from observed vendor connections or providing connection details directly).
3. Once added, future findings related to that connection are de-prioritized or suppressed depending on your policy.

### Reference

#### Table columns

| Column                     | Description                                     |
| -------------------------- | ----------------------------------------------- |
| **Connection Information** | The third-party identifier and a description.   |
| **Connection Type**        | Type (AWS Account, etc.).                       |
| **Resource Count**         | Resources touched by this trusted relationship. |

#### Actions

* **Add Trusted Connection** — explicitly approve a connection.
* Clicking a row opens detail; from there you can revoke trust.

### Related documentation

* Vendor Connections — the discovered-vendor inventory this approval list maps onto


---

# 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:

```
GET https://learn.heeler.com/tenant-admin-guide/connections/trusted-connections.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.