Understand Owner, Admin, Editor, and Viewer roles

Space roles define what a member can do inside one space. The current roles are Owner, Admin, Editor, and Viewer; the former Editor & Approver role is no longer assignable.

Role capabilities

• Owner has the space's highest authority and is assigned to its creator.
• Admin manages members and settings, arranges the space Dashboard, edits records, and can decide pending Proposals, including changes restricted to administrators.
• Editor creates and edits space content, can create a new Database and add fields to a custom one, and can approve or reject AI-authored Proposals when the target and fields are within the Editor write tier.
• Viewer can read accessible space content but cannot perform normal writes.

Proposal decisions do not use a multi-approver chain. One eligible decision applies or rejects the pending Proposal. A human-authored Proposal, a schema change other than creating a Database or adding fields, a Dashboard layout change, or another administrator-only change still requires an Owner or Admin even when an Editor can see it in the review queue.

Database schema

An Editor can create a Database and add new fields to a custom Database, by hand or by asking the AI. Changing what already exists stays with an Owner or Admin: renaming, retyping, reordering, or deleting a field, restoring a deleted field, editing an existing field's options, editing a built-in Database's fields, and renaming, hiding, reordering, or deleting a Database. The server compares each save with the stored fields, so a save that changes an existing field is refused for an Editor even when it also adds one. A Viewer can do none of this.

Owner is not offered as a normal member-management assignment. Changing a member's role requires administrative access and takes effect from the server; open sessions receive the updated permission state through realtime events.

The interface hides actions that are unavailable, but the server checks every protected request again. A visible button never overrides the saved role.

Frequently asked questions

Can an Editor approve every kind of Proposal?

No. An Editor can only decide AI-authored Proposals whose target and fields fall within the Editor write tier; a human-authored Proposal or an administrator-only change still needs an Owner or Admin.

If a button for an action is hidden, does that always mean my role blocks it?

The interface hides actions your role cannot take, but the server checks every protected request again on its own, so the role, not the visible button, is what actually decides access.