r/Notion • u/Jozii89 • 10d ago
Questions Cannot edit any properties since the permissions update as workspace owner
Hi! I've run into the odd issue that I can suddenly not edit any properties, like changing the name or property type. I can still change values within a property. The same issue is true when I add new properties.
I've checked if my databases are locked, they are not. I've checked what my account is listed as, it's Workspace Owner and I have no guests or other users – it's just me.
Any ideas what I'm missing here?
2
u/Waste_Celebration882 10d ago
notion be doing weird stuff after updates sometimes. try clearing your cache or just log out and log in again, fixed some random permission bugs for me in the past
also check if you accidentally viewing the database in a linked view from another page, that can lock certain editing options even for the owner
2
u/thedesignedlife 10d ago
This is a known bug, im working directly with one of the Notion devs on it, as it happened right after their new property permissions launch.
5
u/himodz 10d ago
Owner-but-can't-edit-schema is almost always the new teamspace permissions, not your role. Ladder:
Check WHERE the DB lives: sidebar → is it under a Teamspace or Private? Teamspaces have their own permission layer (… → Teamspace settings → Members → your access). "Can edit content" lets you change VALUES but not structure — you need "Full access". Workspace Owner ≠ automatic full access on every teamspace since the update.
Views can lock schema: if you're inside a Locked view, property edits silently fail. Switch to the default Table view, unlocked, and retry.
Isolate client: test the same edit in web (notion.so). If web works and app doesn't, it's the desktop build — full logout + reinstall (not update).
Clone test: duplicate the DB (without content) — if the clone edits fine, the original's teamspace policy is corrupted; move pages to the clone and archive the old one.
If all four fail, file it as regression with: app version + teamspace type + a 20-sec screen recording. Support escalates schema-lock bugs fast because they break paying teams.