Builder, Member or Viewer: Which Seat Should You Assign?

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

Open the users area in Jestor and add a user by email.
Choose the seat type — member is the recommended default.
Assign a role, which carries the access rules for their function.
Filter the user list by type later to review who holds which seat.
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.

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

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,