Great question!
Updates include Adds, Edits, Deletes, and Syncs.
When you add or edit a row, it counts as one Add or one Edit. It is not dependent on the number of fields.
1 Like
We hope that most customers will use both an App (mobile use cases) and a Page (desktop use cases) for their projects now that they’re both included on all plans
Hopefully, that helps offset the cost of the Pro plan when you initially think you might only need a App but you could benefit from an App and a Page
1 Like
API functions will stay the same on the new team plans. The readTable function currently allows a user to pull all rows in a table, not individual records
Which use cases do you have where you would like to pull individual records?
BTW, and sorry if this was answered before, we can have one app and page with the same dataset. Does it count as one project or two?
I actually managed to move my app from the old team to a new one and it was straightfoward
A project is a project, regardless of the dataset. So, yes it would still be two projects even if they share the same data.
3 Likes
I currently don’t have a use case but I am in the planning stages of developing an app which will have an external database not supported by Glide and in order to keep the databases in sync I will want to update individual rows in the external database and also on the Glide side. If a row has been changed by a user in Glide I will want to do a read before doing any kind of update so I don’t walk on any changes. In other words the database will be able to be updated from both ends. And I will have to synchronize manually because the external database is not supported by Glide. The external database does have API access so I may just need to implement dual update dual write and dual delete when changes are made on the Glide side.
1 Like
Thanks, I’m trying to understand how it will affect me as it’s a live application and it took a lot of time to implement.
Migrating from your current per-project plan to a team plan won’t require you to rebuild your project, so no worries there 
1 Like
So this wouldn’t cover the need for a project that serves a desktop interface as well as mobile/tablet one without counting as two things.
I guess our best option would be to make pages and use them on mobile with the UI provided for them
I think that was one of the primary goals for glide, was to allow users to create multiple projects that reference the same set of data while being billed as a single team instead of being billed for each project seperatly.
3 Likes
Sure, that’s why it made sense to me to consider a pair of page + app with the same dataset/purpose to be one project.
But it was just a question anyway, it’s clear.
It makes sense that the amount of projects we can make is actually big enough on Pro for that scenario, although on Starter I think it should be 10 projects in this case
Looking over the new pricing matrix (great way to compare plans btw), I don’t see any reference to team member permissions. David had responded to someone last year saying permissions would be added to business plans in the future, so just curious if permissions will be available and at what plan levels. Thx!
Hey, Gannon!
We don’t have permissions just yet, but that is on the roadmap. Right now, all members of your Glide Team are by default Editors
I can’t promise which team plans will have permissions, but I would imagine a role, such as “Viewer,” would be included on every plan
Any specific roles you are looking for?
Hey, David. I appreicate you getting back to me. I think @Rasha did a good job summarizing in his post. At a minimum, if would just be nice to at least have 2 permission levels:
Admin — move, duplicate, share or delete apps/pages; publish rights on all apps/pages; edit/delete teams and invite team members; manage account (e.g., billing, closing, etc).
Editor — create new or edit existing team apps; publish any new apps/pages they create; request publishing on all existing apps/pages they edit
This is just off the top of my head and may need to be nuanced a little. Just looking to minimize the possibility of catastrophic “oops, I didn’t know” moments. 
1 Like
Ah, okay. We have experimented with enabling multiple Admins (i.e., not just the Team owner), so once we roll that out, it should be what you’re looking for
In my Free Team, I am limited to three published apps. As I develop, I may publish an app just to test it on a device as opposed to testing it in the app builder. When I am done proto-typing, can I “unpublish” it to make room for developing another app? If so, how?
This would also apply to the Starter Team when I upgrade to that. The limit there is five apps published.
You can unpublish Pages by going into your Privacy settings and clicking “Unpublish”
Unpublishing Apps will have the same process. We are working on releasing that now
In the meantime, you will not need to worry as the Published Project quota is not fully enforced yet
4 Likes
Thank you for the clarification @DJP! Another related question - with a details screen that has X text entry components for a row, if a user entered or edited text in all X entry fields, will that be X updates or a single update for the row? Thank you so much for your help!
I think this could depend on a couple of things. If you are using a native glide form, then nothing is submitted until you click on submit, so I think it should be considered as one update as it’s all sent to glide at one time.
However, if you are using a custom homemade form or just a details screen with user specific columns or standard basic columns, then I imagine it would depend on how quickly all entry components are filled. I assume glide will batch multiple updates into one if they are changed quickly enough, but if you take your time filling each entry in a custom form, then it may be syncing after each component is filled, or possibly while it’s being filled.
3 Likes