> 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/resource-entitlement-discovery.md).

# Resource Entitlement Discovery

## Overview

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

To navigate to the **Resources** page follow the below steps:

1. Select the *Resources* page under the *Entities* section.

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

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

You can use the search box and filters to explore the your organization's resources. The following filter fields are available for this page:

* **Resource** - This field allows you to filter data based on a resource in an application. **For example**, you can choose to filter *arn:aws:apigateway:::/apis/\** Resource *of type apigateway* within AW&#x53;*.*
* **Resource Type** This field filters data based on the type of resources available. **For example**, you can view all resources that belong to a *channel* resource 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 resources have a user with some insights on them. **For example**, to view the resources which have users marked with an *Outlier* insight, you can add *Outlier* as a filter in this field.

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 Resources** <a href="#h_01hwwnrjchzp175sf15d8bxqyj" id="h_01hwwnrjchzp175sf15d8bxqyj"></a>

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

1. The **Identities** tab shows a list of all the identities tied to this resource. You can use the search bar or filters menu to quickly find individual identities tied to this resource.<br>

   <figure><img src="/files/rI8TDFm6s2D15coyeFE4" alt=""><figcaption></figcaption></figure>
2. The **Entitlements** tab shows a list of all the entitlements tied to that resource. You can use the filters menu to quickly sort this list and find individual entitlements.<br>

   <figure><img src="/files/KvwSKAgIHPPS082VsIFX" 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/resource-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.
