Defaulted a lot to airtable recently to kick off projects that require sort of a database and table UI. However, more often than not I am missing the following features:
Providing users with an easy sign up to start working with the table (decoupled from airtable sign ups)
Git like version control
Detailed user rights management
Real world example:
Record A contains work schedule information for employee A.
Record B contains this type of information for employee B.
Employee A is able to see and change information in record A only.
Employee B is able to see but not change information in record B only.
Do you guys share these experiences or have other thoughts on this? Really thinking about building a table tool that covers those problems …
I think Coda clients who stress over this can set up appropriate locking to ensure individuals can just alter their columns, and use Forms, and so on as a method of allowing individuals to connect with w/the right piece of the informational index.
In light of your representative record model, I figure you can make a page where you channel a recipe down to the information coordinating with the client, so they can just see data for themselves yet not for any other person, and you either lock/conceal the remainder of the doc or use CrossDoc to make that dashboard.
In case you’re attached to Airtable as your information base, look at Softr.io for a simple encounter layer on top of Airtable. It’s quite new however worth looking at (it’s free for the fundamental elements to kick you off).
Fascinating to hear that you have comparative requirements in the Notion setting. Intrigues me, would you be able to expand a smidgen on your utilization situations where you wish for better privileges the executives and/or adaptation control?
Thanks for the extensive reply and walk through how to solve those problems in Coda. As mentioned I am experiencing these problems in the airtable specific context of a database like tableUI where I am collaborating with others. Your coda based formula sounds feasible. Is Coda also your go to tool for those cases where you want to basically store alter and track data in a table view?
thanks for pointing to softr.io - well known and already tried it. However it feels kind of unnatural to me to stack another tool (softr) on top of my airtable base just to have an experience layer that could also come in an integrated way (User UI + Admin UI <-> API <-> database). What are you building with softr on top of airtable?
One normal grievance with idea clients is they utilize a worldwide undertaking data set for all assignments, yet cant makes restricted perspectives on the errand data set per customer without uncovering all their other work. this equivalent idea applies to a ton of information I track in thought - timesheet data sets per worker uncover all timesheets and venture monetary information, with no alternative to make a timesheet input see that doesn’t uncover our whole monetary design.
Coda appears to be a doc on a superficial level, yet in the engine is a social data set apparatus with an extremely amazing equation language that you can use to allude to your information in the material. So that’s right, the larger part of my own utilization instances of Coda incline intensely into the even side of the instrument. One disclaimer - you should contemplate the measure of information you intend to place in the data set. I think Airtable handles a huge number of columns obviously superior to Coda today, yet on the off chance that your informational index is more modest than that, may merit investigating. Eager to assist on the off chance that I can.
ideally, you would only have to use one tool, but the benefit of multiple tools is that they specialize in what they do (a database that’s really good as a database, and a frontend that’s really good at experience/speed/etc.). I’ve really only used Softr for prototypes so I can’t speak to how well it would do for you in detail. Glad you’ve checked it out!
If this is an internal app, I would also give a vote to Coda
Do you feel like Coda would be satisfactory for the Notion use case I’m portraying, where information in a timesheet data set is moved up to a venture data set, however, there are limitations on how individual clients can communicate with said information?
Right now our system works beautifully but a single rogue actor could delete all the data. also it is not ideal for every freelancer / employee to see all financial data