---
title: "Action Visibility Rules To Hide Actions on Report"
slug: "action-visibility-rules-to-hide-actions-on-report"
updated: 2021-03-12T15:05:35Z
published: 2021-03-12T15:07:29Z
canonical: "documentation.decisions.com/action-visibility-rules-to-hide-actions-on-report"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://documentation.decisions.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Action Visibility Rules To Hide Actions on Report

Example Lab ArticleWhile Example Lab projects are resources for public use, articles and assets are not actively maintained. Screenshots and features are from the specified version below. These references may become dated as new versions are released.

---

## Overview

| ## Example Lab Details |
| --- |
| **Version** | 6.10.2 |
| **Root Folder** | Example Lab-Action Visibility Rules To Hide Actions on Report |
| **Modules** | None |
| **Dependencies** | None |

This Example Lab demonstrates how to use an **Action Visibility Rule** to hide user actions on a report.

---

## Explanation

For this example, an entity data structure **TestEntity[ExampleLab]** was used to provide records on the Report. The **Create Test Data For Reports** Flow will create test data that will be stored in the **Test Data** Folder. In the configuration folder for this entity, two **User Action Flows** were created; "Regular User Action", "Special User Action". In addition, there is an **Action Visibility Rule** that is configured to hide the "Special User Action" from any non-admin users. The **Dashboard Folder** contains the Page with the Report that will display the records. When users right-click they can view the actions. **All Users Group** has permissions to the project folder with the permissions "Can Use', "Can View", "Can Edit".

To test the **Action Visibility Rule**, two accounts will be needed. One account needs to be added to the Administration Group. The other account should be an non-admin account. View the dashboard form both accounts. The non-admin Account will not have the "Special User Action" available to them to run on the Report.

Reference Articles[Entity Action Visibility](https://documentation.decisions.com/docs/action-visibility-rules)  
[About Folder and Portal Permissions](https://documentation.decisions.com/docs/about-folder-portal-permissions)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Action%20Viz%20RUle.png)

![](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/Actions.png)

---

## Project Download

The examples attached were developed to be instructional and were not developed as officially supported components. For more information or to engage our service team to develop fully supported, production quality solutions, please contact services@decisions.com. Import the project below to a Decisions environment on version 6.10.2 or later using our [Importing/Exporting](https://documentation.decisions.com/docs/exporting-and-importing-overview) article.  
  
  
[ExampleLab[ActionVisibilityRulesToHideActionsOnReport].zip](https://cdn.document360.io/6ef8bcc1-6489-4486-9ad1-83acff7e5df0/Images/Documentation/ExampleLab%5BActionVisibilityRulesToHideActionsOnReport%5D.zip)

---