For those in the community on Enterprise teams: a nice update to share. 
You can now give someone more than Edit access without making them the Doc Owner. Full Access sits between the two — they can manage sharing, lock and unlock pages, and move the doc, but they can’t delete it or publish it. It’s especially useful when a Doc Owner is out, and someone else needs to hold things down.
A few things worth knowing:
- Full Access can do most of what a Doc Owner can do. That includes managing sharing, locking and unlocking pages and tables, and moving the doc.
- But it stops short of ownership. Full Access users can’t delete a doc or publish it. Those actions stay with the Doc Owner.
- It’s a Maker-only role. Only Makers can hold Full Access. If you try to give an Editor Full Access, they’ll be added as Editor instead — no friction, no failed sharing actions.
- Downgrading is straightforward. If needed, Full Access can be downgraded back to Edit at any time.
We know neither of these is a small ask, and both have been long overdue. Tell us what’s working and what you still need.
4 Likes
This, and the other new update on doc subfolders, is super exciting! What I’m still craving are more granular permission controls in the other direction though:
-
- Ability for only certain users to view specific source tables within a document… ALL THE TIME we run into the issue where a few admins need to access the entire database, but different sub-groups of people only need to see certain views (ie. without financials, etc) – and current sync page limitations have left us without a solution.
-
- Ability to lock edit access on only specific column(s) within a table
Thanks!
4 Likes
Hey @Chrissy_Eckman!
It is great to hear from you after a bit of a hiatus — hope all is well!
I completely hear you on the granular permissions. Trust me, you are far from alone in wanting this feature like… yesterday 
Jason from our product team shared a note in the forum a little while back to shed some light on where it sits on the roadmap and the reasoning behind why this very popular request has been a work in progress. If I had a magic wand to make anything happen, this would be right at the top of the list. I am hoping an update is not too far off, and I will be shouting it from the rooftops the moment there is good news to share.
5 Likes
+1 +2 +3
And for all users. Not only Enterprise. Please
3 Likes
Being able to lock columns would do so much work. If you could set it similar to how you control button disabling or something?
4 Likes
I can see the potential value in this new user type, though it feels like there is still room to refine the mechanics. Currently, treating editors as “maker-lights” continues to cause some friction in workspace design.
A highly effective solution would be to align the role precisely with its name: empower editors to edit and update, while keeping creation and deletion exclusively in the hands of makers. This clear separation would instantly resolve a lot of structural issues. I recognize this approach might limit those who treat Coda strictly as a note-taking tool—a use case the company clearly wants to support with this latest addition—but sharpening these permissions would make building and managing documents much smoother.
3 Likes