This is becoming more and more of a problem for me in Coda. I’ve been working on information that is locked under NDA but I can’t share it with my partners unless I create a separate doc. Because there’s no way for me to organize my Coda docs, I have a long-running list of related items that I can…

I’m trying Coda and setting up a complete company structure, and this seems to be a problem. We can invite specific members to folders at the workspace level - and keep others private. This is great for most cases. Where it is breaking down is that we have many projects, and members should only be…

Replying to myself, so one solution is to put all the projects in another workspace, and then put each project into its own folder and set invitations as needed. I tried cross-workspace table syncing and it works. Not sure if there are other limitations yet. This is a hack though and problematic: …

You can make the Projects folder private, invite only those who should see all docs in the folder, and then individually share each doc with specific people. They won’t see the Projects folder in your workspace even if they are members of your workspace but aren’t added to that private folder. Docs…

Hi Paul, That sounds like a perfectly workable solution…wonderful. Thank you! I didn’t pay for a plan yet so was not able to try it. I am in the process of filling out the various risky sections in the folder structure I shared to see if there are any other blockers. I found a couple bugs so far t…

These are great notes on what the wants are for permissions and also great use-case examples. There are quite a few questions about how to handle the smaller details of permissions like these and some solutions take more work than others. These examples give us a good direction to work with though. …

Great @Paul_Danyliuk - yes I’d like to do the master, single-schema data sources common project management data structures that can store all goals, tasks etc for all projects, and the have filtered views within projects with permissions ensuring that only the project-specific data is available to p…

Can any Codan clarify if this is in the roadmap? To me this is very important since we want to keep some document sections private in our information system.

Hi @Jonathan_Solorzano , This is not on the immediate roadmap. Just to reiterate, these features are not necessarily security features. A user can copy a doc or craft a formula to access data in a doc. If you have sensitive information that cannot be shared with others, I would encourage the use of …

Hi, you’re definitely losing some Business Cases here, I was just looking for better granularity and to just don’t allow the document to be copied, as per: This Other Question Because even within the same company, you want some parts of the process to be editable/viewable by some and some parts don…

Granular Permissions

Product Feedback

Paul_Danyliuk January 11, 2020, 1:43pm 43

FYI @Ed_Liveikis you can have bidirectional cross-doc already. Not ready for prime time yet and not widely announced, but not hidden either and kinda works (see gotchas):

Topic		Replies	Views
Page level sharing Product Feedback	29	4266	March 24, 2026
What additional features do you believe are necessary for Coda to be considered the ultimate tool? Ask the Community	18	1385	September 16, 2024
Launched: Sync page access control (view-only) News from Superhuman	107	7787	February 2, 2026
Launched: New sharing features (public sharing, embeds, comment-only permission) News from Superhuman	57	12538	July 9, 2021
Feature Request Update: Page Level Permissions Product Feedback	21	650	July 27, 2026

Granular Permissions

Related topics