Hello @Scott_Collier-Weir ,
When canvas columns were introduced, I set up a doc with authorization levels - levels managed in a table on a canvas page. Only users with authorization level ‘admin’ have access to this canvas page - and therefore access to this user table.
For users, upon opening my doc, they have access to their own rows in different tables, as well as more general rows in other tables, based on their authorization level.
So far, so good.
Up to the point where you allow users access to a canvas row, regardless of which table or area of your doc has this canvas row. Nice for freeform notes, making their own tables, etc.
But, the moment they type /table, every table in the doc is exposed. They can add a view of any table to their private canvas row, including the document user table where an admin enters user authorization levels. Remove the filters, show all columns…and the user can change his authorization level, to whatever role, like ‘admin’.
Canvas pages have their value - even today. But in shared docs, they are a ‘disaster’ waiting to happen. If you make a dashboard on a canvas page, the entire contents can be deleted or manipulated. And text and table/views can be added at will.
So, for canvas columns, we need:
- the locking settings as we know them now
- with the additional options
a) allow text and images (on/off)
b) allow new (simple) tables (on/off)
c) allow other controls (on/off)
This way we can give users acces to canvas pages to write long notes, add pictures and make (simple) tables. Why simple? Because you don’t want to allow lookup columns, or formulas to find things in other tables, to name just a few things.
And if Coda will make this for us, they might as well add the ‘don’t allow to delete rows’ option :-).
Obviously, makers should be allowed to make whatever canvas page they want.
I was not sure if I should outline my thoughts so explicitly, but I think makers need to know the consequences of using canvas columns, because as innocent as they look when used as a note taking page, it’s a wolf in sheep’s clothing.
Long story short: yes, I support your request to Coda.