> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/getting-started/entitlement-discovery/connection-entitlement-discovery.md).

# Connection Entitlement Discovery

## Overview

In this article we will give an overview of the **Connections** page and how to utilize it for entitlement discovery. The **Connections** page provides a list of different connections available within an application. These connections are extracted from an application during the application integration stage.

To navigate to the **Connections** page, elect the *Connections* page from the Entities group.

You can view all the connections with respect to the application that belong to your organization from here.

<figure><img src="/files/oagVewNbBuEFgeTVYzdM" alt=""><figcaption></figcaption></figure>

#### You can use the search box and filters to explore the your organization's connections. The following filter fields are available for this page: <a href="#h_01hprdm3hcta51pytrt469m514" id="h_01hprdm3hcta51pytrt469m514"></a>

* **Connection** - This field allows you to filter data based on a connection in an application. **For example**, you can choose to filter *admin* connection in a *group* connection type within *Confluence.*
* **Connection Type** - This field filters data based on the type of connections available. **For example**, you can view all connections that belong to a *group* connection type.
* **Application** - This field filters based on the specific Application Integration that you would like to explore. **For example**, you want to view *Azure(Test Environment)* data, you can add it as a filter in this field.
* **Insight** - Filtering with insights allows you to see which connections have a user with some insights on them. **For example**, to view the connections which have users marked with an *Outlier* insight, you can add *Outlier* as a filter in this field.&#x20;

Using multiple filter fields together will help you navigate through the data swiftly and will make your time spent on discovering entitlements a lot more productive! Refer to [working with filters](/getting-started/entitlement-discovery/working-with-filters.md) to learn more about filters.

## **Viewing Individual Connections** <a href="#h_01hssy6xprg6fhjj71v6wbwccv" id="h_01hssy6xprg6fhjj71v6wbwccv"></a>

Selecting a connection from the list will pull up more detailed information about the identities and entitlements associated with the connection. There are two tabs in this view:

&#x20;

1\. The **Identities** tab shows a list of all the identities tied to this connection. You can use the search bar or filters menu to quickly find individual identities tied to this connection.&#x20;

<figure><img src="/files/mNZ4oDGudcedGeN3d3m8" alt=""><figcaption></figcaption></figure>

2\. The **Entitlements** tab shows a list of all the entitlements tied to that connection. You can use the filters menu to quickly sort this list and find individual entitlements.

<figure><img src="/files/7sJZIPrFykzvQl5QxKSr" alt=""><figcaption></figcaption></figure>

## **Connection Graph View** <a href="#h_01hssy72z1rdc4xz0h9zdbe36g" id="h_01hssy72z1rdc4xz0h9zdbe36g"></a>

The **Connection Graph View** on the top right corner of the image above, will  allow the user to visualize the connection entity relationships in a manner that helps understand lineage and dependancies. In the example screenshots below, you are able to understand how connections -> application -> identities -> resources/permissions types are related.

<figure><img src="/files/ae81Z3uOpKcO1cH3ImZa" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/yB0fyN3fJtbaiFbe6Xve" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/erjA5olHg27LaCbo5ESa" alt=""><figcaption></figcaption></figure>


---

# 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://docs.balkan.id/getting-started/entitlement-discovery/connection-entitlement-discovery.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.