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

# Welcome

Welcome to the BalkanID documentation page. Here, you will find detailed information about BalkanID's capabilities, as well as release notes on the latest platform features.

### What is BalkanID? <a href="#what-is-balkanid" id="what-is-balkanid"></a>

BalkanID is an identity governance platform that provides the following capabilities:

1. Preemptive discovery, analysis and remediation of identity-related risks.
2. Correlation and visualization of IdP, SaaS, IaaS and on-prem application identities and related entitlements.
3. User access review (UAR) workflow and campaign management.
4. Application entitlement lifecycle management.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Getting started</strong></td><td>Getting Started with BalkanID</td><td></td><td></td><td><a href="/getting-started/user-onboarding.md">Getting Started</a></td></tr><tr><td><strong>User access reviews</strong></td><td>Ensure the right people have right access by periodically reviewing and certifying user permissions across all systems.</td><td></td><td></td><td><a href="/user-access-reviews/access-review-management.md">Access review management</a></td></tr><tr><td><strong>Lifecycle management</strong></td><td>Automate user access from onboarding to offboarding, ensuring consistent permissions and timely de-provisioning</td><td></td><td></td><td><a href="/lifecycle-management/access-requests.md">Access requests</a></td></tr><tr><td><strong>IAM Risk Analyzer</strong></td><td>Discover, prioritize and remediate identity and access related risks using findings</td><td></td><td></td><td><a href="/iam-risk-analyzer/risk-analysis-dashboard.md">IAM RISK ANALYZER</a></td></tr><tr><td><strong>Playbooks and webhooks</strong></td><td>Enhancing workflow automation with playbooks and webhooks</td><td></td><td></td><td><a href="/playbooks/playbooks.md">Playbooks</a></td></tr><tr><td><strong>BalkanID Copilot</strong></td><td>Interact with BalkanID IGA using natural language interface</td><td></td><td></td><td><a href="/balkanid-copilot/balkanid-copilot.md">BalkanID Copilot</a></td></tr><tr><td><strong>Updates</strong></td><td>BalkanID release notes and system updates/enhancements</td><td></td><td></td><td><a href="/updates/release-notes.md">Release Notes</a></td></tr><tr><td><strong>Terms and Conditions</strong></td><td>Terms of service and privacy policies to use BalkanID</td><td></td><td></td><td><a href="/terms-and-conditions/privacy-policy.md">Terms &amp; Conditions</a></td></tr></tbody></table>

### **Platform Demo**

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


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.balkan.id/readme.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 `build a script that syncs our docs to a CMS` 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.