Coda has so much more flexibility than Notion and I love that. But there are a few things we’ve noticed in the migration that are really frustrating:
- There aren’t row-level access controls in a database. You can’t put confidential information in a doc because of this and the number of new docs and cross-syncs is unmanageable
- There aren’t page-level access controls. Similar issue as the above
- Slack notifications that show the previous and new value of a field (I know there is a hack to do this but it’s….super hacky)
Some things that Notion doesn’t have (either) but I really wish Coda would have:
- Conditional layouts/visibility of fields based on the value in 1 or more other fields (i.e., if Field A = “Red” then I don’t see Fields B, C, D). Regular survey forms have this and it’s really really important
- Automations that are near instant. What we need is the ability to populate a field, based on links we make to other databases, but still allow an overwrite (it can’t be a formula field). For example, let’s say Project is part of a Company. I link Project A to Company A. I want to pre-populate field X on Project A with Company A’s sector field but allow an overwrite in field X
i am voting for your first few wishes for row-le el and page-level access controls so we can safely put confidential information in our wlorkflows
2 Likes
Fully agree - one feature you wish for, already exists:
“Conditional layouts/visibility of fields based on the value in 1 or more other fields (i.e., if Field A = “Red” then I don’t see Fields B, C, D). Regular survey forms have this and it’s really really important”
You can already do this! You just need a view / connected table for each layout / case you have. Then you can refer these layouts in anyway you want. It will then open the row in the layout you set for each case (the layout is cointained within each view of table). Here’s a simple logic you can Customise and expand as desired.
EDIT: It is then advisable to adjust the standard layout in the original table so that everything is hidden and the button is highlighted. If users open the row by right-clicking or expanding it, the function will not be applied – they must click on the button.
2 Likes
As far as I know, there’s no true page-level or row-level access controls in Notion either.
To share a page with a view of some table (e.g. tasks filtered only for that client), you have to ‘share’ the whole table, otherwise the view won’t load for that person. And when the whole table is shared, it’s not a big trouble to access it in its entirety from its view.
I verified this behavior a year ago; maybe something have changed already, idk, I don’t use Notion.
P.S. Just checked, it’s still the same. Click here and see the whole table:
3 Likes
We looked into this solution and it’s an interesting hacky one. But what we really want is a dynamic layout so that the change to Field A in the Layout 1 automatically switches to a Layout 2 so the remaining fields to fill change. In the absence of this, all staff using this have to know which fields to skip based on what entries they’ve made. Going into and out of a card to switch layouts just doesn’t work
3 Likes
Ahhh, at least now in Notion, when you open any entry in a database you can change the share settings on the plan we’re on
1 Like
+1 for all of these. All quite needed here
3 Likes
You can use buttons to switch between layouts! Create a button column, set the action to OpenRow, and then set the View to a table containing the layout you want.
1 Like
