> ## 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 Design Roles and Permissions for Your Team
- URL: https://blog.jestor.com/design-roles-and-permissions/
- Published: 2026-09-17T22:29:21.000Z
- Updated: 2026-09-17T22:29:21.000Z
- Author: Bruno Bannach

To **design roles and permissions**, you define access by function rather than by individual. Each role carries its own rules, and people inherit them by being assigned to it.

## Why per-person permissions become unmanageable

Configuring access individually works until the third or fourth hire.

- New joiners needing access replicated by hand
- Nobody able to say what a given person can actually reach
- Access left in place after someone changes function
- Audits that take days because nothing is grouped

## What a role should define

| Dimension        | What it controls                               |
| ---------------- | ---------------------------------------------- |
| **Role**         | Which apps and tables the function can reach   |
| **Field**        | Which fields are visible or editable           |
| **Action**       | Whether a user can open, edit, or only view    |
| **Record scope** | Whether they see all records or only their own |

## How to configure it in Jestor

1. Open the roles area in **Jestor** from the users screen.
2. Review the existing roles, each with its own ID and user count.
3. Create a role per function — finance, operations, support — rather than per person.
4. Set its access rules by app, field, and action.
5. Assign users to the role when inviting them, so access is inherited.

## Why choose Jestor for granular access?

**Jestor** applies permissions by role, field, and action, which is what lets one app or dashboard serve several functions without building a separate version for each.

Record-scoped permissions go further: a salesperson can be limited to deals where they are the responsible person, on the same panel a manager uses to see everyone.

## Frequently Asked Questions

### Should I create a role per person?

No — create one per function and assign people to it.

### Can a role see only its own records?

Yes, permissions can be scoped to records where the user is responsible. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Can I see how many people hold a role?

Yes, the user count appears on each role.

## 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.