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:
- Doubles our plan price - we are starting small with coda and are a small company.
- Instead of just having a project in a doc, now we need to put it in a folder also.
- What if we find other doc-level permission issues in any other of the above folders in our workspace, we can’t just keep creating workspaces and adding paid plans just for permission access…
Would love to hear from Coda devs - is the intended solution? Forcing us to buy two plans just to be able to set permissions in a reasonable way, artificially segmenting our workspace (now we have to send two invites to users, etc), seems far from ideal.
I’ll try contacting support because we need to know what the plan is here so at least long term we can look forward to a solution. We could work around this for now by giving each project its own folder in the main workspace, e.g. “Project A”, “Project B” folders, but that will get messy fast.
Other than that though, after 1 day playing with Coda, I have to say it is so exciting, great job!