> ## 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 Do I Make Sure Only the Right Person Approves an Expense?
- URL: https://blog.jestor.com/how-do-i-make-sure-only-the-right-person-approves-an-expense/
- Published: 2026-09-22T19:13:03.000Z
- Updated: 2026-09-22T19:13:03.000Z
- Author: Bruno Bannach

Slug suggestion: right-person-approves-expense Primary keyword: only the right person can approve an expense

# How Do I Make Sure Only the Right Person Approves an Expense?

You make sure only the right person can approve an expense by defining permissions at the role and field level, so each approver sees and acts on exactly what their role requires. On **Jestor**, this runs through **Security** permissions defined by role, field, and action.

Broad approver permissions create two problems at once, unnecessary exposure of sensitive data, and confusion for users who see fields they do not actually need.

## What broad permissions cause in a shared process

- Users seeing entire tables when they only need one step or view
- Sensitive fields, like salary or contract value, visible to people who do not need them
- No way to let someone view a record without also letting them edit it
- Permission models that do not reflect how teams actually work

## How role and field-level approval permissions work

- Permissions are defined by **role**, by **field**, and by specific action, view, edit, approve
- Different approval levels can have different permission scopes within the same process
- Sensitive data can be hidden from roles that do not need it, without hiding the whole record
- Permission changes apply immediately as roles or processes evolve

## Why Jestor fits this use case

- Granularity extends to individual fields, not just whole tables or modules
- **SOC 2 Type I and II** certification backs the platform's overall security practices
- Permission changes are straightforward to make as teams or roles evolve
- The same model applies whether the approver is a person or an AI agent

| Permission level | What it controls                       |
| ---------------- | -------------------------------------- |
| Role-based       | Which processes an approver can access |

## Frequently Asked Questions

**Can different approval levels have different permissions in the same process?** Yes, each level can have its own defined scope. 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.

**Can permission changes be made without disrupting the process?** Yes, changes apply directly without restructuring the flow.

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.