---
title: "Role or Permission Criteria for Reader Review Forms or Reader Tab Materials"
slug: "role-or-permission-criteria-for-reader-review-forms-or-reader-tab-materials"
status: "new"
updated: 2026-07-21T20:51:31Z
published: 2026-07-21T20:51:31Z
canonical: "knowledge.technolutions.net/role-or-permission-criteria-for-reader-review-forms-or-reader-tab-materials"
stale: true
---

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

# Role or Permission Criteria for Reader Review Forms or Reader Tab Materials

Use filter criteria to show a reader review form or reader tab material only to users with a specific role or permission. This pattern is useful when a workflow, bin, or tab is broadly available, but a specific review form or material should appear only for a smaller group of readers.

Workflow read permissions can control access to many workflow areas, including workflows, bins, and tabs. Reader review forms and individual materials in reader tabs do not provide a separate custom read permission setting. To control visibility for those objects, add criteria that evaluates the current user.

For more information about review forms, see [Workflow Review Forms](https://knowledge.technolutions.net/docs/en/workflow-review-forms).

> [!WARNING]
> 📝 Note
> 
> Permission-based criteria checks permissions assigned directly to the user. It does not account for permissions inherited through roles. If staff inherit the permission through a role, use role-based criteria or add criteria for both the role and the permission.

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/creating-role-or-permission-criteria-for-reader-review-forms-or-reader-BBJmZ4T5PriPlFS) in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? [Let us know](https://community.technolutions.net/get-inspired/new?post_type=gnHx7As1gZ8r6Ld)!

## Before you begin

Before adding criteria, identify the role or permission that should control access.

- Use a role when access should follow membership in a reader group, committee, or staff cohort.
- Use a permission when access should follow a standard or custom permission that is assigned directly to users.
- Use both when some users receive access through a role and others receive access through a direct permission.

## Opening the review form criteria

This example applies criteria to a reader review form. Use the same Current User join pattern when configuring criteria for a reader tab material.

1. Open the Workflow Editor.
2. Open the workflow that contains the review form.
3. Select the **Review Forms** tab.
4. Select the edit icon for the review form configuration.

![Workflow Editor Review Forms tab with the edit icon for a review form.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/01-o1hiCg7lcWGDlvCUxbgfq.webp)
5. Open an existing review form configuration or create a new review form configuration.
6. Configure the bin, review form, required setting, and other review form settings as needed.
7. Set **Base** to **Application.**

## Creating role-based criteria

Create a subquery filter that checks whether the current user has a specific role.

1. In the review form configuration, add a subquery filter.

![Review Form Configuration popup with the subquery filter option.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/02-GFKmgzggcjW5dEpGXibvX.webp)
2. Select **Join.**
3. Under **System**, select **Current User.**

![Join popup with Current User selected under System.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/03-9BWcXELan28G36uP5bO2h.webp)
4. Select **Save.**
5. Select **Join** again.
6. Under **Current User**, select **Role User.**

![Join popup with Role User selected under Current User.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/04-eEtj4xbxEItJV4e29B3xo.webp)
7. Select **Continue**, and then select **Save.**
8. Select **Join** again.
9. Under **Role User**, select **Lookup Role.**
10. Select **Continue**, and then select **Save.**
11. Add a filter for the role name:

![Role-based subquery filter with Lookup Role Name criteria.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/05-DJzJkJCeDaz28pUxwtcZh.webp)
  - Select **Filter.**
  - Under **Lookup Role**, select the **Name** filter.
  - Select the role that should be able to view the reader review form or material.
  - Select **Save.**
12. Leave **Aggregate** set to **Exists.**
13. Enter a descriptive name for the subquery filter, such as `App Review Committee Role Exists`.

![Completed role-based subquery filter named App Review Committee Role Exists.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/06-MqwwIbRSLcfdoAKLIfOno.webp)
14. Select **Save.**
15. Select **Save** again to save the review form configuration.

## Creating permission-based criteria

Use a similar subquery filter when access should depend on a permission that is assigned directly to the user.

1. Create a subquery filter.
2. Add the **Current User** join.
3. Add the **User Permissions** join.
4. Add the **Lookup User Permission** join.
5. Add a filter for the **Lookup User Permission** name.
6. Select the permission that should be able to view the reader review form or material.

![Permission-based subquery filter using Lookup User Permission Name criteria.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/07-bBoZaQLmMOUPfqJ07z0SZ.webp)
7. Leave **Aggregate** set to **Exists.**
8. Save the subquery filter and the review form configuration.

> [!WARNING]
> 📝 Note
> 
> Permission-based criteria checks direct user permissions only. A user who inherits the selected permission through a role will not match this filter unless the permission is also granted directly to that user.

![User permission settings showing a permission assigned directly to a user.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/08-XBaCh7RZiK5FVEn6XpS6K.webp)

## Combining role and permission criteria

If some users should qualify by role and others should qualify by direct permission, add criteria for both access paths. For example, create one subquery filter that checks for the relevant role and another subquery filter that checks for the relevant permission.

![Review form criteria with role and permission subquery filters.](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/09-kWEQ785uAO2DojMtvLlU1.webp)

## Testing the criteria

After applying the criteria, verify that the reader review form or reader tab material appears only for the intended users.

1. Test with a user who should see the form or material.
2. Test with a user who should not see the form or material.
3. If you are using permission-based criteria, test a user with the permission assigned directly.
4. If you are using role-based criteria, test a user with the selected role.
5. If results do not match your expectation, review whether access is coming from a role, a direct permission, or both.

The criteria apply when staff open the relevant file in the Reader. When the current user matches the configured role or permission criteria, the review form or material appears. When the current user does not match the criteria, it remains hidden.