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

# Access requests

BalkanID supports access request management for multiple integrations. For a list of supported integrations, please check the integrations list. Our integrations broadly fall into IDP applications (Okta, Azure AD, etc to name a few), Cloud Service Providers (AWS, GCP, Azure, etc to name a few), Commercial SaaS applications (Salesforce, Github, Netsuite, etc to name a few). Typically, an unsupported integration can be supported immediately upon request within a few days.\
\
**Note** - For guidance on enabling provisioning and de-provisioning options, please refer to this article: [Fulfillment Options](/getting-started/setting-up-your-tenant/application-integrations/fulfillment-options.md)

Access requests are broadly categorized into the following types

* [New user access request](/lifecycle-management/access-requests/new-user-access-request.md)
* [New service account access request](/lifecycle-management/access-requests/new-service-account-access-request.md)
* [New identity access request](/lifecycle-management/access-requests/new-identity-access-request.md)
* [New connection access request](/lifecycle-management/access-requests/new-connection-access-request.md)
* [New resource access request](/lifecycle-management/access-requests/new-resource-access-request.md)
* [New SCIM access request](/lifecycle-management/access-requests/new-scim-access-request.md)

Administrators can pre-scope which connections and resources reviewers are able to request — see [Requestable Catalog (Early Access)](/lifecycle-management/access-requests/requestable-catalog-early-access.md).

{% embed url="<https://vimeo.com/1185989225>" %}


---

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