User Seats

Understand the difference between user types and their powers.

Seats

What's a user seat?
User seats are defined by your subscription plan. They define the maximum powers of a specific user.

For example: if you have a member seat and you want to edit a low-code function, you'll not be able to.

🚧

Seats should not be used as permissioning

We strongly recommend managing all user permissions through roles.

What's the difference between seats and permissioning?
To perform an action in your Jestor, both your seat and your permissions must allow it. Your final level of access is determined by the intersection of these two — essentially, the most restrictive combination applies.

Example:

• Seat: Member.
• Permissioning: full power to access and edit the structure of the table "clients".
  Result: Members can access and create records on the table "clients", but cannot create new fields or add automations in this table.

What are the seat types?
There are 4 types of seats: Members, Builders, Viewer, Portal (beta), Requestor (beta).

Member Seat

These users interact with the internal Jestor tools built by Builders. They can navigate and use all tools created by Builders, but they cannot build or modify structures—except for creating pages.

Example of powers:

• Create, edit, write, and delete records.
• Upload and download data.
• Send messages in the chat.
• Move cards on a kanban board.
• Interact with dashboards.
• Click buttons.
• Fill out forms.
• Edit their Information.
• Individual login and password.

🚧

Members cannot be super-root admins

As such, they are not — and should not be — allowed to manage your Jestor account.

Builder Seat

Builders can create and edit structures, and they also have all the powers available to Members.

Example of powers:

• Create and edit apps
• Create and edit tables
• Create and edit fields
• Create and edit roles
• Create and edit automations
• Manage low-code tools

Requestor Seat (Beta)

This seat is designed for light internal use, such as creating tickets and tracking their progress.

• Can fill out forms but has read-only access to all other tools.
• Cannot access tables directly.

Portal Seat (Beta)

Limited power users for external users, such as clients, partners, suppliers, etc. It's not intended to be used by someone from your company.

• Can fill out forms but has read-only access to all other tools.
• Cannot access tables directly.
• Cannot be used by company employees who share the same email domain as the account owner. For example, if Nike owns the account, users with emails like [email protected] cannot be added.

Viewer Seat

Read-only access to app pages.