> ## 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 manage users and roles in your system
- URL: https://blog.jestor.com/how-to-manage-users-and-roles/
- Published: 2026-09-16T18:50:03.000Z
- Updated: 2026-09-16T18:50:03.000Z
- Author: Bruno Bannach

To **manage users and roles** properly, separate two questions: who can use the process, and who can change it. In **Jestor**, that distinction is built into the seat type, and the recommended default is to give most of the team a member seat rather than a builder one.

## Why permissions get sloppy in growing teams

Early on, everyone has full access because there are four people and no time for governance. The habit persists, and eventually someone edits a process they were only meant to run.

The damage is rarely malicious. It is usually a well meaning change by a person who did not know what depended on it.

What role separation prevents:

- Team members altering processes they only need to use
- Fields deleted by someone who did not know they fed an automation
- No clear owner for the structure of a process
- Access granted once and never reviewed

## Seat types and what they imply

| Seat type | What the person can do          | Who should have it                    |
| --------- | ------------------------------- | ------------------------------------- |
| Builder   | Create and change the structure | The few people who own process design |
| Member    | Use the process as designed     | Most of the team, by default          |

## Step by step to add someone

1. **Open the users area** to see the list of active people.
2. **Check your available seats** before inviting anyone.
3. **Click to add a user** and enter their email address.
4. **Select the seat type**, defaulting to member unless there is a reason otherwise.
5. **Assign the role**, which determines what they see and can do.
6. **Review periodically**, filtering by active or inactive to keep the list honest.

## Why roles matter as much as seats

The seat type decides whether someone can build. The role decides what they see inside what exists: which apps, which fields, which actions. Both together are what makes a single environment safe for a whole company.

- **Granular roles:** permissions per role, field and action
- **Active and inactive filters:** the user list stays accurate
- **Seat visibility:** you know how many are available before inviting
- **Recommended default:** member for the team, builder for the few

## Frequently Asked Questions

### Should everyone be a builder?

No. The recommendation is to keep most of the team on member seats. See [jestor.com](https://www.jestor.com/?ref=blog.jestor.com).

### Can I see how many seats I have left?

Yes. Available seats are displayed in the users area.

### What decides what a person sees?

The role assigned to them, which controls access per field and per action.

## Video Tutorial: Step by Step

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://www.jestor.com/?ref=blog.jestor.com) and see how to take your company's operations to a new level of efficiency and control.