> 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/updates/release-notes/insight-visibility-management-and-access-change-tracking.md).
# Insight Visibility Management and Access Change Tracking
Our latest updates bring more context and control — helping you see what’s changed, compare access with context from previous campaigns, and manage insights and access with precision across your tenant.
#### [Tenant-Level Insight Visibility Management](/iam-risk-analyzer/findings/configure-insight-visibility-for-your-tenant.md)
You can now manage which insights are visible across your tenant from the new **Insight Visibility** tab on the **Rules and Playbooks** page. This gives teams finer control over which insights appear throughout the app — helping reduce noise and keep attention on the findings that matter most.
You can now view and search through all insights enabled on your tenant, on a per-integration basis, and toggle visibility on both system-generated and custom-defined insights — hiding any that are not relevant to your workflows. By default, all insights remain visible.
#### [Access Change Status](/user-access-reviews/access-review-management/tracking-campaigns-and-performing-access-reviews/understanding-review-statuses.md#access-change-status)
Access reviews now include a new **Access Change Status** column, giving reviewers clear visibility into how each access item has evolved across campaigns. You can now instantly see whether an access item is **new**, **unchanged**, or **modified** since the last campaign — giving reviewers context and helping reviewers focus attention where it’s needed most.
Each access item is labeled with one of the following statuses:
* **Added Access** – Newly introduced items not present in previous completed campaigns.
* **Unchanged Access** – Items that appeared previously without any changes, with links to view how it was actioned upon in the past.
* **Modified Access** – Items that existed before but now have updated permissions or metadata, with detailed comparisons available.
Access change tracking occurs at the time of campaign creation, reflecting a **snapshot of access as of that moment**.
#### [Enhanced Custom App CSV Mapping](/getting-started/setting-up-your-tenant/application-integrations/custom-application-integration-data-upload.md)
We’ve refreshed the CSV-mapping workflow to make configuring **custom-app** data faster and clearer. The updated UI provides smarter automatic column matching, clearer canonical-field details, and real-time validation for required fields.
Unmapped columns are automatically added to metadata, optional fields can be ignored, and defaults can be set directly within the panel. A new **Entities-Only Mode** lets you quickly upload entity/identity-only information with safe defaults for all access-related fields, streamlining scenarios where only account data is available.
If you have a requirement for our custom apps feature, contact us to enable it for your tenant.
---
# 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/updates/release-notes/insight-visibility-management-and-access-change-tracking.md?ask=&goal=
```
`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.