Access levels renamed (October 2025)

Guide

The changes go live on October 31, 2025.

What happened?

In the recent update, we've renamed access levels so that they are consistent across Space, Database, and Entity levels. We've accumulated plenty of accidental complexity over the years, and now it's time to get rid of it.

The changes did not affect the actual access, only the names: no one has lost the capabilities they had or gained new capabilities. No action items for you, no reason to panic 😅. Sorry for the kerfuffle, though.

What changed?

Levels	Old → new name	Why?
Space + Database	Creator → Architect	`Creator` used to be ambiguous: does it mean someone who created the thing or someone with the highest access? `Architect` describes our favourite person who designs a workspace (or a Space/DB) for their company — check out our Architects Weekly newsletter.
	Editor → Owner	`Editor` already used to include the abilities to publicly share entities and revoke access, so it was a mislabeled `Owner`.
	+ Editor	The proper `Editor` access with the abilities to edit and delete but not publicly share entities was missing.
Space	Viewer → Commenter	`Viewer` used to include the ability to comment, so it was a mislabeled `Commenter`.
Space	+ Viewer	The proper `Viewer` access with the ability to read but not comment entities was missing.

Overview

Here are the updated set of access levels (aka templates) at a glance with new ones in green and updated ones in yellow:

		⚙️ configure	👀 read	💬 comment	➕ create	✍️ edit	🗑️ delete	🌐 share externally	👤 revoke access
Architect	Space	+	+	+	+	+	+	+	+
	Database	+	+	+	+	+	+	+	+
	~~Entity~~
Owner	Space		+	+	+	+	+	+	+
	Database		+	+	+	+	+	+	+
	Entity		+	+	+	+	+	+	+
Editor	Space		+	+	+	+	+
	Database		+	+	+	+	+
	Entity		+	+	+	+	+
Contributor	Space		+	+	+	±	±	±	±
	~~Database~~
	~~Entity~~
Commenter	Space		+	+
	Database		+	+
	Entity		+	+
Viewer	Space		+
	Database		+
	Entity		+
Submitter	~~Space~~
	Database				+
	~~Entity~~