You can share your doc with those of your clients who have a Google account, and you can apply filters to the data using the
User() function (which references the profile of the currently logged in user), so that a user will only see a particular row if they are tagged in a particular column in that row, e.g. create a “People” column where you specify who is allowed to see the relevant row, and then set the filter condition to something like
This will work so long as you do not give your clients edit rights to the doc; if they have edit rights, then they can change the filter condition and see all the data, including from your other clients. Also, it won’t work if you share the doc via link-sharing, rather than naming specific users - the
User() function only works with logged in users.
Anyway, personally, I would be cautious about exposing data this way, when the only thing standing between one client and another client’s data is a single filter condition. There’s always a risk of some mistake or malfunction in the filter condition exposing data to the wrong client. You might be better off waiting for Coda to implement the cross-doc feature and in-doc permissions, which in theory would allow you to run one doc as a central database, and use a separate doc for each client that pulls data from the central database, but with a few more “fail-safe” layers of protection to reduce the risk of the wrong data being exposed.
Either way, it’s always a good idea to set up an extra ‘test account’ that sees what your clients see (rather than what you see as the owner of the doc), so that you can test everything thoroughly.
Those are my thoughts anyway - more than happy to be corrected by others who know their way around Coda better than I do!