User Seats

Learn the difference between members and builders.

Most Jestor plans allow unlimited users. 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 no-code seat and you want to edit a low-code function, you'll not be able to. Although you didn't block it explicitly, only the developer seat can access the low-code function area.

What's the difference between seats and permissioning?
In order to do something in your Jestor, both your seat and permissioning have to allow it. It's the intersection of powers, or "sum of restrictions", that results in your final powers.

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 3 types of seats: Members, No-Code (Builder), and Developer (Builder).

Builders: They have the power to build and edit the organization structure and edit records. There are 2 types of builders:

  • No-code: they can build all the system structures using no-code tools and premium blocks.
  • Developer: they have all the powers of a no-code builder plus: access to low-code tools, developer fields, and super-advanced permissioning rules.

Members: They can edit records and write text on pages.

You can check the differences between builder types and prices here.

Member

Members are unlimited users. You can use it for your own team, suppliers, clients, and others.

They are "users that use" the Jestor internal tool built by builders (No-code and Developer). They can navigate and interact with all tools built by builders. However, they can't build or create new structures, except for pages.

Example of powers:

  • Create, edit, write, and delete records.
  • Create pages.
  • Create tasks.
  • Send messages in the chat.
  • Move cards on a kanban board.
  • Interact with dashboards.
  • Print pages.
  • Click buttons.
  • Fill out forms.
  • Edit their own Information.
  • Write text on pages.
  • Individual login and password.

Members are not allowed to be super-root admins. Therefore, they can't (and shouldn't) be able to manage your Jestor account.

No-Code/Business Builder

No-code/Business builders can create structures and automations without using code. They have all the powers of a Member, plus builder powers and tools.

Example of powers:

  • Manage tables, views, apps/dashboards, and pages.
  • Install templates.
  • Settings access to user management, plans, themes, language and region, roles, and history log.
  • Manage users, seats, and plan.
  • Manage automations.
  • Manage chat channels.
  • Manage workspaces.
  • Manage APIs.

Manage = Create, edit, and delete powers.

Low-Code Builder

Low-code builders can do all that the no-code builders can, plus access to low-code tools and special features.

Example of powers:

  • Manage low-code functions.
  • Manage low-code triggers.
  • Manage low-code webhooks.
  • Developer fields and blocks (tagged as "Dev").