> 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/setting-up-your-tenant/application-integrations/fulfillment-options.md).

# Fulfillment Options

BalkanID supports multiple fulfillment options, allowing seamless configuration for how **identities, connections, and resources** are provisioned or deprovisioned across all connected applications.

This comprehensive approach offers both a **streamlined setup process** and the **versatility** to integrate with your existing infrastructure. You can configure fulfillment via your **Identity Provider (IdP)**, directly manage provisioning, connect via a **SCIM server**, create tickets for management through your **Ticketing and Work Management solutions**, or even trigger custom actions by calling **playbooks**.

**Note:** To enable Fulfillment Options for your account, please [contact Customer Support](mailto:support@balkan.id).

The options are:

| **Fulfillment Option** | **Description**                                                                                                                                                                                                                                                       |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Direct Provisioning    | The user account will be provisioned in / deprovisioned from the app itself.                                                                                                                                                                                          |
| Ticket Creation        | The system will create a ticket to the ticketing system for manual provisioning / deprovisioning.                                                                                                                                                                     |
| SCIM                   | The account provisioning / deprovisioning will happen via SCIM (Needs [SCIM configuration](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations.md#h_01hpzxnnktnf241s28vqsn3vy3) to be done first). |
| Playbook               | The playbook server will be called post actions (Needs [Playbook configuration](https://docs.balkan.id/playbooks/playbooks.md) to be done first).                                                                                                                     |

The current set of applications supported are:

| **Fulfillment Option** | **Description**                                                                                                                                                 |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Direct Provisioning    | AWS, AzureAD, Google, Okta, and other apps on demand                                                                                                            |
| Ticket Creation        | Refer to [support ticketing systems](https://docs.balkan.id/getting-started/system-notifications-and-automatic-ticket-creation/supported-ticketing-systems.md). |
| SCIM                   | All applications                                                                                                                                                |
| Playbook               | All applications                                                                                                                                                |

#### To configure fulfillment options within your tenant: <a href="#h_01hr43v8yte2q8z6gxgwnm345q" id="h_01hr43v8yte2q8z6gxgwnm345q"></a>

1. Go to the *Configure* > *Integrations > Add Integration* **OR** *Select the three dots on an application -> Edit* (If you want to edit an already configured application)

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FXRvzAfUdpqlc7iQZT5Na%2Fimage.png?alt=media&amp;token=43dd9897-4221-45f6-b341-f15fd50fa14a" alt=""><figcaption></figcaption></figure>

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2Fh0CLBhN0TwFBpBPgTnRc%2Fimage.png?alt=media&amp;token=fe962a17-e4b8-4779-b5a6-18682ddc62af" alt="" width="375"><figcaption></figcaption></figure>
2. If adding a new integration, [configure the application integration](https://docs.balkan.id/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations.md) and click *Next.*
3. Under the *Optional Configuration* settings, Select the fulfillment options as required.

   <figure><img src="https://2975852473-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbVGYwk8aSk5yI1GDPEW9%2Fuploads%2FWwMwzBtDCwYSplMbZBtP%2Fimage.png?alt=media&amp;token=0d22f002-4d7b-4d31-84c0-31b50ca63edd" alt="" width="563"><figcaption></figcaption></figure>
4. Click on Save to apply this to that integration.

Voilà, all set! Your newly set fulfillment options will be taken into account if any event takes place on the event in the system.


---

# 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/getting-started/setting-up-your-tenant/application-integrations/fulfillment-options.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.
