I wonder if I might be mis-understanding some of the locking features for tables.
I have a bunch of control tables all on one page. That page is set to read only, and that works as planned when on that page.
So - trying to edit any of these items :
brings up this info box as expected.
However, within the database table (which is on a page that is not locked / not read only) that looks up these control tables, I’m still able to edit the values.
The locking values for the db table are the following :
Here’s the earlier data from the control table as a lookup in the db table…
And… I can easily edit it by opening the modal…
This doesn’t seem to match the logic as I thought I understood it for locking.
Does this mean there is no way of locking down data if its a lookup from another table? Is this as intended by coda / have I gone about things the wrong way? Or is it a bug? Or… So many questions!
Would love to hear how others approach this. It seems being able to lock down lookups is vital for the use of databases in business environments.