People, roles & permissions

Manage who belongs to each workspace and what they can do there. Every member gets one of four roles as a baseline, and you can fine-tune access table by table and even field by field. Understand the four roles Every workspace member has exactly one role, which sets their default access to every table in that workspace: • Admin — full control. Views, creates, edits, and deletes records, and is the only role that can invite people, remove members, change roles, or set per-table and per-field overrides. • Editor — views, creates, edits, and deletes records. No member or permission management. • Contributor — views everything and creates new records, but cannot edit or delete existing ones. • Viewer — read-only. Useful for stakeholders who only need visibility. Roles are set per workspace, so the same person can be an Admin in one workspace and a Viewer in another. Per-table overrides can raise or lower these defaults for individual tables. See who has access Open People & access from Manage workspace at the foot of the rail. Each member appears as a card showing their name, email, current role, and a short description of what that role allows. Your own card is tagged you. Each card also shows a workspace count, such as In 3 workspaces — how many of your workspaces that person belongs to. Workspaces you are not a member of yourself are never counted. Invite someone to the workspace Scroll to Invite someone at the bottom of the People page — or press Invite person at the top of the Permissions page to get there. Choose a person under Person, pick a Role, and press + Invite. The picker lists only people who already share a workspace with you and are not yet members here. When everyone you share a workspace with is already a member, the Invite someone section disappears. Inviting someone who is already a member changes nothing, so a double-submit is harmless. Change a role or remove someone On a member's card, pick a new role from the dropdown — it saves as soon as you choose. You can also change roles on the Permissions page, where each role button includes a reminder of what it allows. Press Remove to take someone out of the workspace. You cannot change your own role or remove yourself; another Admin has to do that for you. Invitations, removals, and role changes made on the People page are recorded in the audit history. Grant access to a whole folder The Folder access card sets one person's access to every table in a folder at once — Full, Read and create, Read only or No access. This is what replaced giving somebody a separate workspace, and unlike a separate workspace nothing they can see loses its relationships to the rest of your data. Access resolves in one order: an explicit override on the table wins; failing that the folder's grant applies; failing that their role decides. Marking the folder hidden removes it — and its name — from anyone without a grant. Override access for a single table Open Permissions, pick a person from the Members list, and find the Per-table overrides section. Each table has an override dropdown with five settings: Inherit from role, Full access, Read & create, Read only, and No access (hidden). Your selection saves the moment you make it. Overrides work in both directions. Full access lets a Viewer create, edit, and delete in that one table, while No access (hidden) hides a table completely — even from an Editor. Choose Inherit from role to remove an override and fall back to the role's default. The Effective column shows the result of role plus override as chips — View, Create, Edit, Delete, or Hidden — so you can confirm exactly what that person can do. Use Open → to jump into the table itself. Hide or lock individual fields Click a table's name in the overrides list to expand its fields. Each field has its own dropdown: Inherit, Read only, or Hidden. A Hidden field is invisible to that person and cannot be edited; a Read only field is visible but locked. Field overrides only tighten access — if someone cannot edit the table, every field stays read-only for them regardless of the field setting. Setting a table to No access (hidden) hides all of its fields automatically. A chip next to the table name counts how many fields have overrides, so restricted fields are easy to spot later. Tips • Dropdowns on the Permissions page save the moment you change them — there is no separate save button. • After setting overrides, check the Effective column — it shows the combined result of role plus overrides, chip by chip. • Use Permissions → on a member's card to jump straight to that person's override view. • New invites default to the Viewer role — a safe starting point you can raise afterwards. • Set an override back to Inherit from role (or a field back to Inherit) to return to the role's normal access. Good to know • Role and override controls are visible to every member, but only a workspace Admin's changes are accepted — anyone else gets an error when they try to save. • Remove takes effect immediately — there is no confirmation dialog. • Only the People page writes to the audit history. Role changes made on the Permissions page — and table or field overrides — are not recorded, so change roles from the People page when you want a paper trail. • Removing someone does not clear their per-table or per-field overrides; if you re-invite them later, the old overrides apply again. • Contributors cannot edit any existing records — including rows they created themselves. Give them the Editor role or a Full access override on the relevant table if they need to make changes. • Field overrides can only restrict — you cannot make a single field editable for someone who cannot edit the rest of the table. • Both pages are workspace-scoped: check which workspace is active before changing roles, or you may edit access in the wrong one. Who can do what • Only a workspace Admin can invite people, remove members, change roles, or edit per-table and per-field overrides — the server rejects these changes from any other role. • Admin rights are per workspace: being an Admin in one workspace grants nothing in any other. • Any member of a workspace can open the People and Permissions pages and see the member list and each person's access. • You cannot change your own role or remove yourself from a workspace — another Admin must do it. • The invite picker only shows people who already share at least one workspace with you, so one team's directory is never exposed to another. • A brand-new account belongs to no workspaces and sees nothing until it creates a workspace or is invited to one.