> ## 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 Structure Granular Permissions in BPM Processes
- URL: https://blog.jestor.com/granular-permissions-bpm-processes/
- Published: 2026-09-15T20:22:04.000Z
- Updated: 2026-09-15T20:22:04.000Z
- Author: Bruno Bannach

Structuring granular permissions in a BPM process means each user or role sees and edits exactly what their part of the process requires — not the entire table, not every field. In **Jestor**, **Security** permissions apply by role, field, and specific action across any process.

Coarse permissions in a shared process create two problems at once: unnecessary exposure of sensitive data, and confusion for users who see fields they don't actually need.

## What coarse permissions cause in a shared process

- Users seeing entire tables when they only need one stage or view
- Sensitive fields (salary, contract value) visible to people who don't need them
- No way to let someone view a record without also letting them edit it
- Permission models that don't map cleanly to how teams actually work

## How granular permissions work in BPM

- Permissions are set by **role**, by **field**, and by specific action (view, edit, approve)
- Different stages of the same process can expose different fields to different roles
- Sensitive data can stay hidden from roles that don't require it, without hiding the whole record
- Changes to permissions apply immediately as roles or processes evolve

## Why Jestor fits this use case

- Granularity extends to individual fields, not just entire modules or tables
- SOC 2 Type I and II certification backs the platform's overall security practices
- The same model applies consistently across every BPM process in the company
- Permission changes don't require restructuring the process itself

| Permission level | What it controls                          |
| ---------------- | ----------------------------------------- |
| Role-based       | Which processes a user can access         |
| Field-level      | Exactly which data is visible or editable |

## Video Tutorial: See It in Action

🎥 **Video Tutorial:** [Gestão de Usuários: Novos Filtros e Estilo](https://www.youtube.com/watch?v=Z1EYYRY1CGw&ref=blog.jestor.com)

See how user management and filters support granular permission control.

## Frequently Asked Questions

**Can different stages of a process expose different fields?** Yes, field visibility can vary by role and stage. More at [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

**Is the platform independently certified for security?** Yes, it holds SOC 2 Type I and II certification.

**Do permission changes require rebuilding the process?** No, they apply directly without restructuring the workflow.

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 and see how to take your company's operations to a new level of efficiency and control.