I am increasingly frustrated with the seeming refusal of the Coda team to incoporate permissions at the Doc and Page levels. This is causing a lot of organizational issues with our company, and there are workarounds that aren’t exactly true permissions settings. This should be a very simple and easy thing to do that I have seen asked about SEVERAL times in the community, but it seems the Coda team is just unwilling to implement this feature.
We have several locations for our company as well as different companies within our structure, and the folder-only solution is NOT at all helpful for us. I don’t want to have to pay extra for separate workspaces at this point in our company as we are still fairly small, but we are really needing to have the ability to set permissions at the Doc level to help create some privacy between the locations when it comes to employee information. As our company grows, the folder solution is just not scalable, especailly since folders are unable to be nested (though this still wouldn’t be the solution we would want, just having THAT ability would be immensely helpful).
It really is mind-boggling WHY the Coda team just doesn’t see any reason to implement this, but as our company continues to grow, the need for this feature is increasing.
Coda Team, please, please offer a solution to this. You HAVE to realize this structure, no matter how dear to all of you, is not a valid solution for the many people who use your product who have asked multiple times about having a feature like this.
Coda is DEFINITELY not refusing to implement permissions. It is not a “simple and easy” thing to do as you claim.
Coda has been working on this for years, and the 3rd of four phases was announced here:
You can see in the look-ahead below that security is on the top of the list for 2025. It does not mean that it will be the first to be released, It is a very complex implementation to do.
Considering this is pretty standard with other applications similar to Coda, I would disagree that it is not “simple and easy”. I certainly don’t mean it’s a simple on/off switch, by any means. But this has been something requested for a long time with this, and it is really affecting the efficiency of our team being able to find what is needed as we have so many folders that have ONE Doc with ONE Page just because we can’t have permissions at the Doc and Page level. This just not at all efficient, nor is it something that should take years to implement.
You don’t have to agree with my opinion, but this is something that really should’ve been implemented when it first released.
DOC LEVEL
Jessie - Let me know if I am off base if I am misunderstanding the request, but you definitely SHOULD have the ability to set permission per doc. The issue may be that you have everybody shared into the folders which will supersede any doc level permissions. In our org, for instance, I own a few folders to help my personal organization, but I share users into each doc individually. For instance:
Folder “A” (only shared with me and my direct report) contains:
A team hub for each team (supervisor as editor, frontline as viewers)
Folder “B” (only shared with me) contains:
A project management doc (shared with managers and IC’s across several teams as editors)
A leadership team meeting agendas doc (supervisors only as editors)
Note how the folder contains limited shared folks, but the docs contain the majority of shared users.
PAGE LEVEL
Beyond that (at the page level) Coda’s structure of database info accessible across a doc independent of the page is what would prohibit page privileges at this point. My current workaround (for view only resources): filtered views and sync pages. For instance we have resource documentation in a central doc, for instance a “Company Wiki” shared with you only. In the “Company Wiki” doc, you could have several pages like “Sales View”, “Customer Success View,” etc. Then in a separate doc like “Sales Team Hub” that is shared with the entire sales team, you can sync page “Sales View” in checking the box allowing them to see it without access to “Company Wiki”
Is it pleasant? NO
Is it easy? NO
Does it get the job done? YES