> 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/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/viewing-your-reviews.md).

# Viewing your reviews

## Viewing Your Access Reviews

The Access Review Table is your central hub for managing and acting on access reviews. It provides a comprehensive display of all access relationships relevant to your campaigns, showing what entity (Identity or Connection) has access to what other entity (Connection or Resource), with what specific permissions, all within a given application integration.

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

***

### Exploring Review Details

Every piece of information presented in the review table is designed to be interactive, allowing you to quickly dive into more context:

{% hint style="info" %}
When enabled, the **Compliance Violations** column shows current risk affecting an access relationship. See [Compliance in access reviews](/compliance-controls-and-posture/compliance-overview.md#compliance-in-access-governance) for details.
{% endhint %}

#### Viewing entity metadata

To see more information about a user, connection, or resource, click on it's cell in the table. A side panel will open showing additional context pulled directly from the connected application.

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

#### Understanding Relationship Permissions

To see all permissions tied to an entitlement, click the value in the **Permissions** column. This opens a side panel that explains the privileges that the entity has access to within another entity.

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

#### Understanding the Access Provider Column

The **Access Provider** column helps you understand *how* a user has access to a connection or resource by showing the complete chain of relationships that grants that access. This includes both direct assignments and indirect (nested) access paths through groups or roles.

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

For example, if a user inherits access through multiple nested groups, the Access Provider column will display the full hierarchy — such as:

> *User → Group A → Group B → Resource X*

This gives reviewers full visibility into *what provided the access and through which entities it flows*, making it easier to verify if access is appropriate or excessive.

{% hint style="info" %}
To generate this full chain of access for reviews under a campaign, make sure to toggle the [**Include Nested Entities**](/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/creating-campaigns.md#campaign-details) setting while creating your campaign.
{% endhint %}

***

### Understanding Review Grouping Options

BalkanID offers two ways to view your reviews, allowing you to choose the best option for your review workflow: **Ungrouped** and **Grouped by Entity**.

#### Ungrouped Reviews

When reviews are **Ungrouped**, each individual access relationship is displayed as a separate row in the table. This view allows you to **approve or deny each access at a granular level**, giving you precise control over every entity relationship.

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

#### Grouped by Entity Reviews

When reviews are **Grouped by Entity**, all access relationships associated with a single Identity or Connection are consolidated into one row in the table. This grouping allows you to **action upon all reviews associated with that specific entity at one time**, streamlining the review process for entities with many accesses.

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

To see all the individual reviews associated with a grouped entity, simply click on the "**Eye" icon** in that entity's row. This will open a detailed view showing all underlying granular accesses.

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

***

## Viewing a review's audit log

BalkanID provides a detailed **Audit Log** for each access review, allowing you to track all decisions and changes made over time. This audit trail is crucial for compliance, understanding decision-making, and troubleshooting.

{% hint style="info" %}
If an [**Attestation Set**](/user-access-reviews/access-review-management/configuring-access-reviews-and-campaigns/attestation-sets.md) was required for the campaign, the audit log will include the attestation questions and the reviewer’s answers alongside the approve/deny action.
{% endhint %}

The way you access the audit log depends on whether you're in the "Ungrouped" or "Grouped by Entity" view of your reviews.

***

### In Ungrouped View:

When viewing reviews in the **Ungrouped** format (where each access is a separate row), you can directly access the action log for any specific review:

* Navigate to the **"Details" column** for the review row you want to investigate.

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

* Clicking on the detail icon in this column will open a **sidebar**. This sidebar provides comprehensive information about the review, including its full details and a chronological **audit log of all actions taken** on that specific review.

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

### In Grouped by Entity View:

When reviews are **Grouped by Entity**, you first need to access the granular details for the entity before viewing individual review action logs:


---

# 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/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/viewing-your-reviews.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.