> 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/bundles.md).

# Bundles

A **Bundle** is a named, reusable collection of accesses that spans one or more connections across multiple applications. Bundles are created and managed by **BalkanID administrators** to simplify access provisioning for common roles or use cases.

For example, an administrator can create an **Engineering Baseline** Bundle that includes the required access for Okta, Jira, and GitHub. Users can then request the entire Bundle in a single, atomic access request instead of submitting separate requests for each application.

Bundle requests follow the same request, review, and provisioning workflow as standard access requests. Once approved, the requested access is provisioned across all applications included in the Bundle.

#### Bundle Lifecycle

1. **Creation:** An administrator creates a Bundle by giving it a name and selecting the connections it should grant across one or more applications. Bundles that are marked for the catalog become available to users in the service catalog.
2. **Assignment:** An identity owner requests a Bundle from the service catalog, choosing whether to **Assign** (grant) or **Unassign** (revoke) its accesses, and whether access is **Permanent** or **Temporary**. If the Bundle has **Enforce eligibility** turned on, a grant request is only allowed for an employee who matches the Bundle's eligibility rules. The request is then reviewed and approved just like any other access request, including any access request policies that match the Bundle.
3. **Provisioning:** Once approved, access is provisioned across every application in the Bundle. Each application is fulfilled independently and the request tracks a rolled-up status, so a partial failure in one application is surfaced without blocking the others.
4. **Usage:** The identity owner retains the Bundle's accesses across all included applications for the duration of the request.
5. **De-provisioning:** For a Temporary Bundle request, access is automatically revoked across every application when the expiration date is reached. An **Unassign** request revokes the Bundle's accesses immediately upon approval.
6. **Revocation and Updates:** Administrators can edit a Bundle's connections or delete it at any time to reflect changing access requirements.

#### Creating a bundle

Bundles are created and managed by administrators from the **Bundles** section.

1. Navigate to **Configure → Bundles** and click **Create bundle**.<br>

   <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%2FsUFxQPhwjSgniYNgFaCx%2Fimage.png?alt=media&amp;token=b35d6a23-40b2-4058-bc45-d9315e758fb3" alt=""><figcaption></figcaption></figure></div>
2. Fill in the Bundle **name** and **description**, and set the **owner** who is responsible for the Bundle.<br>

   <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%2FJrKHIjp3j5GiQb3EzNU4%2Fimage.png?alt=media&amp;token=d688bd03-970b-462f-a33e-fb1f42f819da" alt=""><figcaption></figcaption></figure></div>
3. Optional: add a **Logo**. The logo is shown on the catalog card instead of the application icons. Paste an https link to an image, or upload a PNG, JPEG, GIF or WebP file up to 2 MB.
4. Optional: set the attributes that describe who the Bundle is for: **Managers**, **Departments**, **Job titles**, **Employment types** and **Teams**. A Bundle can have more than one team, and each team must be an existing employee team. Pick teams from the list. You cannot type a new team. A team already on the Bundle stays until you remove it, even if no employee has it anymore. You can also set a **Birthright** tag. These attributes are used in the catalog filters, in access request policies, and for [eligibility](#bundle-eligibility).
5. Under **Select connections**, add the connections this Bundle should grant. Connections can span multiple applications — this is what makes a Bundle cross-application.<br>

   <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%2FuRDt3kE0vRS7PovWNCHk%2Fimage.png?alt=media&#x26;token=b96f249f-4406-4175-9b21-4b5d2eafc019" alt=""><figcaption></figcaption></figure></div>
6. Turn on **Enable in access request catalog** so the Bundle appears to users in the service catalog. Turn it off to hide the Bundle without deleting it. A Bundle that is hidden from the catalog cannot be requested.
7. Optional: turn on **Enforce eligibility** to limit who can receive the Bundle (see [Bundle eligibility](#bundle-eligibility)), then save. The new Bundle is listed with its logo, or with a stacked icon of the applications it spans.<br>

   <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%2FWx4w2WF1BHPv5dj3iH0e%2Fimage.png?alt=media&amp;token=a5ee28fe-e0c8-4fb0-bab8-397a08071414" alt=""><figcaption></figcaption></figure></div>

#### Bundle eligibility

By default, anyone can request a Bundle. Turn on **Enforce eligibility** to limit who can receive it. When it is on, a grant request is only allowed for employees who match the Bundle's **Departments**, **Job titles**, **Employment types**, **Teams** or **Managers**.

Use **Match mode** to choose how the rules combine:

| Match mode                    | The employee is eligible when                                |
| ----------------------------- | ------------------------------------------------------------ |
| **Any configured attribute**  | They match at least one of the attributes set on the Bundle. |
| **All configured attributes** | They match every attribute set on the Bundle.                |

How matching works:

* Attributes that you leave empty are ignored. If you turn on **Enforce eligibility** but set none of them, nothing is checked and anyone can request the Bundle. The form shows a warning in this case.
* Text values (department, job title, employment type and team) are compared without regard to upper or lower case.
* **Teams:** the employee matches if their team is any of the Bundle's teams.
* **Managers** match direct reports only. An indirect report does not match.
* Eligibility is checked for the employee who will receive the access (the requestee), not for the person who raises the request.
* Eligibility applies to **Assign** requests. **Unassign** requests are never blocked.
* The check runs in the UI and again when the request is created, so it also applies to requests made through the API.

When **Enforce eligibility** is on, the form marks the fields that are used with a **Used for eligibility** tag. In the Bundles list, the eligibility column shows **Enforced (Any)** or **Enforced (All)**.

{% hint style="warning" %}
If a Bundle already has an employment type or a team set, turning on **Enforce eligibility** starts to block employees who do not match. A team that no employee has matches nobody. Review existing Bundles before you turn it on.
{% endhint %}

#### Approval policies for Bundles

Bundle requests go through access request policies, like other access requests. In the policy builder, an access request policy has a **Bundle** condition. Use it to match a request by the Bundle it asks for.

A rule can match the Bundle by ID, name, description, owner, managers, departments, job titles, employment type, team, birthright, application, integration or the connections it contains. For list fields such as departments, a rule like "Department equals Engineering" matches when the Bundle's list includes Engineering.

A rule with a Bundle condition only matches requests that were raised from a Bundle. It does not match normal requests.

Existing policies that match on the requested user or on the access granted also apply to Bundle requests. They are checked once for each connection in the Bundle.

#### Finding Bundle requests

On **Access requests**, filter the list by **Bundle** to see only the requests raised for a given Bundle.


---

# 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/bundles.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.
