> 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/lifecycle-management/access-requests/requestable-catalog-early-access.md).

# Requestable Catalog (Early Access)

{% hint style="info" %}
**Early Access:** Requestable Catalog is an Early Access capability. To have it turned on for your tenant, contact BalkanID Support or your customer success representative.
{% endhint %}

By default, a reviewer raising an access request can browse every connection and resource in your tenant. The **Requestable Catalog** lets an administrator narrow that list, so reviewers, risk managers and even admins only see the access your organization has decided is safe to request on their own.

{% hint style="info" %}
The catalog applies to all users.
{% endhint %}

### Before you begin

* Requestable Catalog must be turned on for your tenant — contact BalkanID Support to request it.
* You need the Administrator role to configure the catalog.

### Configure the catalog

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FSXRXtZJoAEkbMVPKKIoF%2Frc-admin-config.png?alt=media&#x26;token=1247fd49-286d-4c55-9390-413ab76b65b3" alt="The Requestable Catalog section of Access Request Preferences, with Connections and Resources marked as Scoped"><figcaption><p>The Requestable Catalog section of Access Request Preferences</p></figcaption></figure></div>

1. Go to **Access requests** and select the settings (gear) icon to open **Access Request Preferences**.
2. Under **Requestable Catalog**, choose what you want to narrow — **Connections** or **Resources**. Anything already narrowed is marked **Scoped**.
3. Select **Edit** to open the filter builder. It is the same builder used for saved filters elsewhere in BalkanID, so it should already feel familiar.
4. Build the filter by choosing a **Field**, an **Operator**, and one or more **Values**:

   * **Connection** — pick specific connections (roles, policies, groups) by name.
   * **Connection Type**, **Application Integration**, **Application**, or **Insights** — describe a broader rule, such as everything belonging to one application.

   Use **Add condition** to combine conditions, and **NOT** to exclude.
5. Select **Save**, then **Save Preferences**. The change applies right away.

<div data-with-frame="true"><figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FRyJ58b4PqfxCuqfI5n4I%2Frc-filter-builder.png?alt=media&#x26;token=d3a6af15-df8c-4dad-80e2-e009f244f0c2" alt="The filter builder for requestable connections, showing Field, Operator and Values"><figcaption><p>Choosing a field, an operator and values for requestable connections</p></figcaption></figure></div>

Connections and Resources are configured separately. Whatever you leave empty stays fully requestable.

### What users see

Users browsing the grant and revoke pickers see only the access inside the catalog, along with a note explaining that an administrator has narrowed the list. If nothing matches, the picker shows an empty state instead of the full catalog.

#### Does this also apply to Admins?

Yes. While Admins have the permissions to add and update the requestable catalog, while creating an access requests, they are also bound by that catalog, like any other user.

### Removing a scope

Select **Clear** on **Connections** or **Resources** to make everything in that category requestable again.


---

# 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.balkan.id/lifecycle-management/access-requests/requestable-catalog-early-access.md?ask=<question>&goal=<user_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.