Coming off the presentation on “2022 Year in Review” Webinar with Shishir, we want to kick off crowdsourcing answers to the two key questions he asked on Roles & Permissions.
[I’ll add the link to the recording here when it drops]
Shishir’s two questions:
How would you like to think about data and calculation boundaries?
When determining who can have access to a cell or data, how do you think about who should have access?
I think it would be great for people to respond here with use cases, things you are trying to do like:
- Creating a client portal where your client can see how many hours you’ve worked and invoices
- Building a list of potential candidates to hire at a startup with their requested salaries, but only certain HR leaders can see that number while everyone else can see the application
One item to think about: performing calculations on data. For example:
- Only the sales leader can see what every sales person on the team sold, but everyone could see the sum total of the team
It would also be great to get examples of things you wanted to be able to do for your clients and how you were unable to solve it in Coda today.
Shishir’s next Q:
If you receive a link to a subset of a doc (page, page set, etc.) what container do you expect to receive it in?
In other words, what would the person on the other side receive and what controls would you (or they) have over it?
Wizards like @Leandro_Zubrezki might have a wireframe for what would work here.
Perhaps a shortcut here might be something like the formula bar that only the Doc Admin could see & edit.
Personally, I’d love to see an upgrade to the Page formula, the Button formula made official, and a v2 of the Detail view. Combined with formulas on filtering data based on roles/permissions using the Coda User ID/Auth, we could solve for most of our use cases.
A bit on the Supersynchronous journey
From Day 1 we’ve aspired to be the Enterprise partner for Coda. Security, roles & permissions, and scalable workflows have been something we’ve thought about every day and tried to problem solve for.
At this point we simply tell our clients they cannot solve for roles & permissions or scalability in a Coda doc. We regularly say:
- “If they have access to the doc, they have access to the data.”
- “Coda is best used as a single doc for your org. It doesn’t really work to have multiple docs because they don’t speak to each other well.”
- “Coda does not have a good solution for two-way data syncing with Packs or docs. We’ve built something that works (ex: Affinity Pack), but it takes expert devs to customize it to your use case.”
We’ve accepted that Cross-doc cannot solve the problem of scalability. Prolific producer @Scott_Collier-Weir has provided some solutions here. (Scott, curious for your POV here!)
I’m personally excited about the potential of using Coda with Xano (https://www.xano.com/).
If Coda could solve the roles & permission + two-way sync problem, we could solve the scalable/cross-doc problem with Xano in every use case we’ve come across.
I remain enthusiastic that Coda is the ultimate workflow design tool for Enterprise orgs if these issues can be addressed.
Look forward to everyone’s feedback!