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

# Builder, Member or Viewer: Which Seat Should You Assign?
- URL: https://blog.jestor.com/builder-member-or-viewer-seat/
- Published: 2026-09-17T22:30:27.000Z
- Updated: 2026-09-17T22:30:27.000Z
- Author: Bruno Bannach

Choosing between **builder, member or viewer** determines what someone can do structurally. Roles then determine what data they can reach. The two decisions are separate and both matter.

## Why seat type is decided badly

Seats are usually assigned at the moment of inviting someone, when nobody is thinking about it.

- Everyone made a builder because it avoids future requests
- Processes changed accidentally by people using them
- Read-only stakeholders given edit access unnecessarily
- No review once the team grows

## What each seat type means

| Seat        | Can do                                  | Suited for                               |
| ----------- | --------------------------------------- | ---------------------------------------- |
| **Builder** | Configure and change how processes work | The process owner and a small build team |
| **Member**  | Use processes and fill records          | Most of the team, most of the time       |
| **Viewer**  | See without editing                     | Stakeholders who need visibility only    |

## How to configure it in Jestor

1. Open the users area in **Jestor** and add a user by email.
2. Choose the seat type — member is the recommended default.
3. Assign a role, which carries the access rules for their function.
4. Filter the user list by type later to review who holds which seat.
5. Keep super root access to one or two people at most.

## Why choose Jestor for access discipline?

**Jestor** recommends member as the default explicitly: the team should be using the process, not changing how it works. Building is a separate responsibility, and treating it that way prevents accidental changes.

Because seat type and role are independent, someone can be a member with broad data access or a builder with narrow access — the two questions do not have to be answered the same way.

## Frequently Asked Questions

### What should most people be?

Members — the recommended default. See [jestor.com](https://jestor.com/?ref=blog.jestor.com).

### Is a viewer the same as a member?

No, a viewer sees without editing.

### How many super root users should there be?

Ideally one or two in the whole company.

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