> ## Content Index
> Fetch the complete content index at: https://blog.jestor.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# How to Handle Sensitive Fields in a Shared Process
- URL: https://blog.jestor.com/handle-sensitive-fields-shared-process/
- Published: 2026-09-17T22:36:52.000Z
- Updated: 2026-09-17T22:36:52.000Z
- Author: Bruno Bannach

To **handle sensitive fields in a shared process**, the sensitivity has to live on the field rather than on the process. Splitting a process into two just to protect one column creates more problems than it solves.

## Why processes get split unnecessarily

The instinct is to separate what should be restricted.

- Two tables maintained because one field was sensitive
- Data duplicated between them and drifting apart
- Reporting impossible across the two halves
- Handoffs added where none were needed

## What field-level control enables

| Capability                   | Effect                                    |
| ---------------------------- | ----------------------------------------- |
| **Field visibility by role** | One process, different views per team     |
| **Editability by role**      | Some roles read, others write             |
| **Conditional editability**  | A field locks after an action is taken    |
| **Separate panels**          | Reference data isolated from input fields |

## How to configure it in Jestor

1. Keep one process in **Jestor** and apply permissions at field level.
2. Hide sensitive fields from roles that do not need them.
3. Use read-only access where a role should see but not change a value.
4. Use conditionals so a panel becomes read-only after approval.
5. Apply the same restriction to indicators, so dashboards do not reveal what records hide.

## Why choose Jestor for shared sensitive processes?

**Jestor** carries permissions into the open card, forms, and indicators alike, which means one process can genuinely serve several audiences without duplication.

Conditional editability adds the time dimension: a value editable before a decision can become fixed afterwards, without a separate process for the two states.

## Frequently Asked Questions

### Do I need two processes for sensitive data?

No — field-level permissions handle it. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can a field lock after approval?

Yes, using conditionals on the panel.

### Do dashboards respect field permissions?

Yes, indicators are permissioned too.

## Video Tutorial: Step by Step

Check out other practical tutorials on the Jestor YouTube channel.

## Get to know Jestor

With **Jestor**, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by **AI**. Discover Jestor at [jestor.com](https://jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.