# Database Saving **URL:** https://community.glideapps.com/t/database-saving/79177 **Category:** Ask for Help **Created:** [January 13, 2025, 9:20pm UTC](https://community.glideapps.com/t/database-saving/79177 "2025-01-13T21:20:38Z") **Posts on this page:** 1 **Showing post:** 5
### Author: ![MaximeBaker](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/maximebaker/32/80877_2.png) [@MaximeBaker](https://community.glideapps.com/u/MaximeBaker) #### Post date: [January 14, 2025, 12:50am UTC](https://community.glideapps.com/t/database-saving/79177/5 "2025-01-14T00:50:35Z")
You can’t use the same Glide Table across teams unfortunately. Google sheet would work under 25k rows, but if you update a row on one GS from Glide Data Editor, the other team will consume one update for each sync. So can go up very quickly. Here is a post that you might like reading: > [@Security tip: Managing role-based permissions in Glide apps](https://community.glideapps.com/t/security-tip-managing-role-based-permissions-in-glide-apps/77854): > > If you’re using Glide apps and need secure control over user permissions, be aware that Glide’s visibility conditions (like showing or hiding buttons for certain roles) are not a security feature. While these conditions are helpful for managing the app’s appearance, they do not protect actions at the backend level. Key Points to Protect Your Data Row Owners for Data Protection: Enabling “Row Owners” is effective for securing individual records (for viewing, editing, and deleting), but it does… --- _[View the full topic](https://community.glideapps.com/t/database-saving/79177)._