Members & roles

Roles

Access inside a context is role-based, and admin-only powers are individual actions inside pages, never hidden pages — everyone sees the same sidebar.

• Owner — full administrative control, including deleting the context permanently. Owners can change member and admin roles and transfer ownership.
• Admin — manages the context layer, its settings and its people — including inviting members and admins, and promoting members — but cannot delete the context or change an existing admin or owner.
• Member — can edit and create pages, upload files, connect a data source (their credential joins the context's shared pool), and restore a page to one of its own earlier versions.

Roles govern administration, not content. If the context uses content permissions, anyone — owners and admins included — sees only what their buckets or full access cover, and can edit or restore only pages they can read.

Administrative actions

Admin or owner is needed for: context identity, Slack, Website and direct Postgres connections, deleting sources, retrying a failed process, and invitations.

Invite teammates

Open Settings → Members to see the team and pending invitations. Admins and owners can invite by email, choosing member or admin. Invitations remain pending until accepted and expire after seven days; an admin or owner can revoke one or send a fresh invitation.

Pensieve operators manage the model policy. Context owners and admins do not choose model assignments; see Models.