> 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/findings/configure-insight-visibility-for-your-tenant.md).

# Configure insight visibility for your tenant

Insights can be [defined by you](/iam-risk-analyzer/findings/setup-insights-using-entity-filters.md), or generated as part of our [entity discovery](/getting-started/entitlement-data-discovery/entity-discovery.md) process while connecting new applications. These may include insights about missing MFA, unused access for a period of time, terminated users, or users who act in the capacity of a manger, among others (plus custom insights you might have defined yourself). 

Some of these may not be relevant after a while, or may be adding to the noise while reviewing access in a tenant with a large number of insights. Alternatively, some discovered and created insights might have a degree of overlap. In this case, you can **hide insights.** This will make it so that hidden insights are not shown anywhere on the tenant, for any user.

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

### How to Hide Insights

1. **Navigate to the insight visibility section**
   * In the **navigation sidebar**, go to the **Rules & Playbooks** section and select the **Insight Visibility** tab.
2. **Filter and/or search for the insight you wish to disable**
   * You can search by insight or application name, and filter by insight status (hidden, visible, all). Remember — insights are on a per application basis. For instance, you may decide that the **MFA Missing** insight is not important for App A, but you want to see it while reviewing access for App B.
3. **Toggle visibility for the insight**
   * This will instantly hide any reference to this insight across the tenant.
   * Note that this is distinct for the active/inactive toggle on the Custom Insights page — that controls whether your custom created insights are applied alongside discovered insights, while this controls actual visibility of all currently available insights on your tenant regardless of the source.


---

# 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/findings/configure-insight-visibility-for-your-tenant.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.