# Introducing Full Access for Enterprise Users **URL:** \ **Category:** News from Superhuman\ **Created:** [August 5, 2026, 3:23pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202 "2026-08-05T15:23:25Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Ruggy-Joesten](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/ruggy-joesten/32/50260_2.png) [@Ruggy-Joesten](https://connect.superhuman.com/u/Ruggy-Joesten)\ **Post date:** [August 5, 2026, 3:23pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202/1 "2026-08-05T15:23:25Z")
_ **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. ![FullAccess_Docs_July2026 (1)](https://global.discourse-cdn.com/coda1/original/3X/b/3/b3218f3e79c1cc66c912584f967736571bed314e.gif) 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. ---
**Author:** ![Chrissy\_Eckman](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/chrissy_eckman/32/45286_2.png) [@Chrissy\_Eckman](https://connect.superhuman.com/u/Chrissy_Eckman)\ **Post date:** [August 5, 2026, 4:32pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202/2 "2026-08-05T16:32:52Z")
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: - 1. 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. - 1. Ability to lock edit access on only specific column(s) within a table Thanks! ---
**Author:** ![Ruggy-Joesten](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/ruggy-joesten/32/50260_2.png) [@Ruggy-Joesten](https://connect.superhuman.com/u/Ruggy-Joesten)\ **Post date:** [August 5, 2026, 4:51pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202/3 "2026-08-05T16:51:46Z")
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 not](https://connect.superhuman.com/t/feature-request-update-page-level-permissions/60617)e 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. ---
**Author:** ![Stefan\_Stoyanov](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/stefan_stoyanov/32/24536_2.png) [@Stefan\_Stoyanov](https://connect.superhuman.com/u/Stefan_Stoyanov)\ **Post date:** [August 5, 2026, 6:19pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202/4 "2026-08-05T18:19:23Z")
+1 +2 +3 And for all users. Not only Enterprise. Please ---
**Author:** ![Samuel\_Langford](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/samuel_langford/32/47844_2.png) [@Samuel\_Langford](https://connect.superhuman.com/u/Samuel_Langford)\ **Post date:** [August 5, 2026, 7:12pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202/5 "2026-08-05T19:12:34Z")
Being able to lock columns would do so much work. If you could set it similar to how you control button disabling or something? ---
**Author:** ![Christiaan\_Huizer](https://yyz1.discourse-cdn.com/coda1/user_avatar/connect.superhuman.com/christiaan_huizer/32/28269_2.png) [@Christiaan\_Huizer](https://connect.superhuman.com/u/Christiaan_Huizer)\ **Post date:** [August 6, 2026, 1:00pm UTC](https://connect.superhuman.com/t/introducing-full-access-for-enterprise-users/61202/6 "2026-08-06T13:00:48Z")
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.