What's the Difference Between Member and Builder User Types When Granting Team Access
In Jestor, the "member" seat type is recommended for people who use the process day to day, while "builder" is meant for those who actually configure tables, apps, and automations — which changes the level of access and responsibility each user has.
Why is the default recommendation to use member for the team?
Making the whole team builders would give anyone the ability to change how the process is structured, when the goal is usually just for them to use the process that's already set up.
What are the differences between member and builder?
| User type | Main role |
|---|---|
| Member | Uses the already configured process, without changing its structure |
| Builder | Configures tables, apps, automations, and the process structure |
Why choose Jestor to manage different access levels?
Jestor combines the seat type (member or builder) with configurable roles, letting you define detailed permissions — like who can create tables or manage other users — beyond the basic distinction between using and building.
Should every team member be a builder?
It's not recommended; the general guidance is to reserve the builder type for whoever actually builds the process structure.
Can a member edit records within the process?
Yes, members use the process normally, filling out and updating records according to their role's permissions.
Can there be more than one builder on the same account?
Yes, more than one person can have the builder seat type, depending on the company's needs.
Video Tutorial: Step by Step
Check out more practical tutorials on Jestor's YouTube channel.
Get to know Jestor
With Jestor, each team member has the right access level — using the process or building it — without mixing the two responsibilities.
Get to know Jestor at jestor.com and see how to take your operation's efficiency to a new level.