---
title: "Blinding Data and Form View Permissions"
slug: "blinding-data-and-form-view-permissions"
updated: 2026-11-04T14:19:45Z
published: 2026-11-04T14:19:45Z
canonical: "help.trialkit.com/blinding-data-and-form-view-permissions"
---

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

# Blinding Data and Form View Permissions

How to blind (hide) data to specific user roles

User roles can be blinded to specific fields within forms so the data is not visible when entered by another role or when data is being [computed](/v1/docs/conditional-actions-compute) or [populated](/v1/docs/conditional-actions-populate) which needs to be hidden.

### Where Does Data Gets Blinded?

Field blinding is enforced on all field types within forms, but not within normalized tables.

When a field is blinded, there are several places in TrialKit that enforce that blinding, when the blinded role is accessing any of the following areas:

- On forms during data entry or form viewing
- Audit trails where updated data changes are displayed
- Queries Report - Hides any queries on fields that are blinded to the user role viewing the report. Form view permissions are enforced here as well.
- Report Builder/Ad-hoc reports - Hides the blinded column
- File Repository - Files uploaded on blinded upload fields will not be shown in the file repository
- PDF Exports
- Data Exports - Displays “*****” for data that exists but is blinded

There are two ways to blind data to a user role. Both are described in the remainder of this article:

- By Field
- By Form

### Blinding Data Fields

Specific data fields can be blinded within forms.

> [!WARNING]
> Edit checks on blinded fields
> 
> If edit checks exist on a blinded field, those checks will only get run for unblinded users who are saving the form.

Field blinding is configurable from two screens:

#### Within the form builder, field properties

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image(816).png)

> [!NOTE]
> Effect on multiple study versions
> 
> If a field is not blinded on version 1 of a form, but blinding is added on version 2, it will automatically also apply to version 1. This is because field blinding is not connected to the form design. It’s a role security setting.

#### From role security settings

First select the role that needs to be blinded, then open the blinding options:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image-7BDPZ01H.png)

Then select which form and fields that need to be blinded to the role indicated on the right side of the screen:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image-LY78PNW3.png)

**Blinding settings on the App form builder**

Found within [field's properties](/v1/docs/field-types-and-properties#common-field-properties)

Tap on a field within the form builder, and then open it's properties:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image(817).png)

From their tap on the roles that need to be blinded, taking note of the field name displayed at the top to verify the correct field is being set up:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image(818).png)

Tapping 'Done' at the top will save the settings. There's no need to save the form within the form builder.

### Field Blinding Audit Report

An Audit report tracks any changes made to field blinding on forms. It is accessible from the blinding configuration screen on the web:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image-BZFUJZA7.png)

### Blinding Whole Forms

It might be necessary that certain roles should not be able to view an entire form. This is easily handled with role security settings, form permissions.

Form view permissions are enforced within subject casebooks and the Queries Report, but not in all the places where field blinding is enforced (e.g. Data Exports). For that reason, it might be necessary to ***also*** blind the fields on the form if the user role has access to data exports or other reports.

Web browser:

Select the role to configure, and then form rights button:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image(819).png)

Mobile App:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image(820).png)

Tap the role to configure and then form permissions option:

![](https://cdn.document360.io/7a6694f8-a35c-4fe3-abe9-1febe8020af7/Images/Documentation/image(821).png)

From there, select which forms should have view and/or edit rights for that role.