I’m one of the people in charge of Configuration Management in my organization (a small team of around 18 people, including developers, managers and HR). Naturally, I’m very interested in exploring ways in which Coda could replace some of the tools we use every day. I’m optimistic of the benefits it can bring in terms of UX, simplicity and lower costs across many use cases.
I’ve been using Coda since march and have successfully introduced the use of Coda (Free Plan for now) in some key workflows that involve relatively small docs. We’re considering the possibility of investing in Coda’s Team Plan, but first I’d like to check if it’s feasible to do what we have in mind.
I have carefully read the plan descriptions in the Pricing page, and the info you can see when clicking “Locking” and “Hide” over a section in a document, but I’m still a bit confused regarding how these features work in practice. So, if it’s ok with you, I’d like to explain a basic use case, and I appreciate if people using the Team Plan (or above) can help me clarify a few questions I’ll write below. Thank you very much in advance!
USE CASE: Time tracking
I’m thinking about using a Coda doc as a basic time tracking tool. To simplify things, let’s say I have a table with four columns: Person, Start Time, End Time, Task description.
One way to put it in production would be to share this document with all the team, and trust that people add/edit their own time entries on the one master table. However, it would be nice if this had a little more control. Specifically, that each person could only see/edit time entries relating to his or herself. It’s not critical to completely prevent people from seeing other people’s entries, but if it can be done, even better.
My questions about this:
If I (as the doc admin) use “Hide” on a section, does it prevent other people from “unhiding” it? Is this related to any setting seen in the “Locking” menu?
Let’s say I have my one master table, and then create one view of this table for each person in the company. Each of these views would be filtered by the Person column. Can the locking permissions be set up such that people can add/edit rows on their corresponding views, but not be able to alter the value under the “Person” column (messing with other people’s entries)?
Under the Locking settings, I see that the option “Interact only” includes “Add rows” and “Change table values” but I don’t see “Delete rows”. Does this mean that under this locking strategy, people (non-admins) can never remove rows from those tables?
These are my main concerns for now. Any info or suggestions are very much appreciated. Thank you!