> 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/iam-risk-analyzer/rbac-analyzer/role-confidence.md).

# Role Confidence

<figure><img src="/files/NJOvChefZXKR5k8bdQHV" alt=""><figcaption></figcaption></figure>

The **Role Confidence** tab provides a comprehensive mapping between departments, job titles, managers, and the roles they have been assigned within BalkanID, along with their respective **Role Confidence Scores**. These roles are generated through an advanced algorithm that calculates the most relevant roles for each department and job title based on their access patterns and permissions.

### Role Confidence Score

Along with identifying BalkanID roles for RBAC, BalkanID calculates the the confidence score, i.e., *significance* of each role for a given job title, department, and manager. The goal of this analysis is to discern the importance of roles within job titles and departments, spotlighting those that are prevalent or considered "birthright."

Just as importantly, the score draws attention to a specific role within a job title and department that warrants closer monitoring — to prevent potential security issues, to ensure productivity (and address any decline in performance), or to clean up access left behind by an employee's lateral or upward movement.

The confidence score is calculated based on three factors: **department**, **job title**, and **manager**. High scores indicate strong alignment between the role and the department/job title/manager cohort. Lower scores highlight areas that may require further review.

#### Legend

| Color         | Threshold                                                                                              | Confidence          |
| ------------- | ------------------------------------------------------------------------------------------------------ | ------------------- |
| 🟢 **Green**  | More than **75%** of employees with a given job title, department, and manager have access to the role | High confidence     |
| 🟡 **Yellow** | More than **50%** and up to **75%**                                                                    | Medium confidence   |
| 🟠 **Orange** | More than **25%** and up to **50%**                                                                    | Low confidence      |
| 🔴 **Red**    | **25% or less**                                                                                        | Very low confidence |

A high-confidence role is one that nearly everyone in a cohort already holds — a strong candidate to formalize as a birthright. A very-low-confidence role is one that only a few members of a cohort hold, which may signal an exception, drift, or access that should not be part of the role at all.

{% hint style="info" %}
Confidence is about **cohesion**, not danger. A low-confidence role is not automatically risky. It simply means the access is not uniformly shared by the cohort. Pair confidence with the Role Risk Factor to understand both *how role-like* and *how risky* a cluster is.
{% endhint %}

### Improving confidence scores

* For roles with lower confidence scores, review the associated permissions and compare them with the actual needs of the department or job title under a manager.
* Adjust role assignments as necessary so each role accurately reflects the permissions required for the specific functions of the department or job title.
* Regularly update the roles and their associated permissions based on evolving organizational needs and feedback.

After adjusting assignments or policies in your IdP, re-run the RBAC analysis to confirm the confidence score moves in the right direction.


---

# 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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/iam-risk-analyzer/rbac-analyzer/role-confidence.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.