Sharing docs with teams: Best practices

[Pedro_Wunderlich]

I’ve taken quite a bit of time building our custom CRM (with the help of several of you, thank you!!).

Now that it’s done, I’m not sure what’s the best way to get my team on board. My concerns are primarily with teammates accidentally deleting tables or rows.

My question is:

1. Is there a way to share the CRM with my team in a way that they can only create new rows without deleting data?
2. What’s the best way to back up the CRM (say, create a daily backup)
3. Are there version controls of sort where I could jump back to a point in case something goes terribly wrong?
4. Could I share an individual copy of a Coda doc with each teammate but still have them linked?

How do you guys work with your team + a Coda doc? Since it’s all just one big document, it does feel that accidents could happen, specially with many chefs in the kitchen.

Thanks in advanced

[Pch]

Hi !

1. As far as I know, there is no “granular permissions” when sharing a doc but in this post, you may find some tips to kind of “get around” this while we’re patiently waiting for more control over sharing. (Plus there seems to be some Privacy Issues (there’s another post about this too here)

Hide your table and other tips to prevent user errors

While we work on sub document permissions there are a few tips and tricks to help you prevent accidental user error as others work in your doc. Do share things what are working for you. Create a section where you explicitly ask users to stay away from. Hide your tables - ( using a filter and table option) Create views that show users only rows meant for them Create buttons to add rows to make it easy and scoped. Adding automation notification that get triggered if incorrect rows are edited.

2. There are ways to backup tables using buttons and/or automations (or even a 3rd Party service like Zapier I think) but I’ve found this post very useful when I was personally looking for a way (or at least ideas ) to backup tables :

A Button to copy multiple Rows from one Table into Another

So I’ve got 2 tables I am using for a tracking document for my business. Because the larger a table gets (1000+ rows of tracked items) you get significant slowdown when adding any new rows to the table, I am employing a system when I move any already Invoiced items from the Master Table to the Archived Table. Imagine a setup like this. [Capture] With the help of some excellent Coda staff I’ve already figured out a way to set an automation to automatically move any rows that have their status s…

3. From the “Home Page” of Coda where you can see all your docs, you can access the “version history” of a doc by clicking the 3 dots (...) “menu” that appears when hovering a doc with the mouse . It will open a new tab where you’ll be able to see the previous version of a doc and/or copy one if needed

View and copy doc history | Coda Help Center

4. There’s actually no public crossing doc reference so I don’t think it’s currently doable but it’s in a beta test phase !

Sign up for Beta access to…Data from another doc AKA Coda Doc Pack

Some have requested it as “Cross-doc” others as a “Coda Pack”. Whatever you call it we’ve heard the request loud and clear on the need to sync data from one doc into another. We’re opening up a Beta program to gather feedback on our Coda Doc pack and we’d love to know what you think before we release it to the world. To sign up just fill in this form. Team mates will be able to see the tables you sync into your docs but if they would also like to sync tables as well please share this form wit…

Hope this help