---
title: "Legacy form rules that fire for users in different roles"
slug: "legacy-form-rules-that-fire-for-users-in-different-roles"
updated: 2026-04-27T19:38:10Z
published: 2026-04-27T19:38:10Z
canonical: "help.quickbase.com/legacy-form-rules-that-fire-for-users-in-different-roles"
---

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

# Legacy form rules that fire for users in different roles

When you create a condition based on the user, you tell Quickbase that you want to trigger a form action based on the role of the user editing the form. You can hide or show fields to users in (or not in) a particular role; you can also choose whether to make fields required or editable for users in certain roles.

## Operators for the user

When basing a condition on the user's role, you can choose either of these operators:

- Is in the role
- Is not in the role

## Example

On a form used to manage projects, I want to ensure that only users in the Manager role are able to edit the Approved field.

For my rule's condition, I should select:

| When: |  |  |
| --- | --- | --- |
| The user | Is in the role | Manager |

For my rule's action, I should select:

| Action |  |
| --- | --- |
| Make editable | Approved |

Otherwise, when the user is not in the role Manager, make read-only Approved.