I’m currently running a closed BETA for my Glide app, with privacy settings set to Private. The app is only accessible to users whose email addresses are listed in the “users” table.
I’ve invited a small group of early adopters (13 people) to try out the app. I first asked them for the email address they wanted to use for login, and then used the Share > Invite Users feature to send them an email invite with a link to access the app.
However, I noticed that under the Usage section of my Glide account, it shows a limit of 20 users, and it indicates that I’ve already used up 13 (the 13 early adopters). I’m concerned that Glide is counting these early adopters as team members, but they should just be regular app users.
From what I understand, there shouldn’t be a limit to the number of registered app users—only team members are limited. Did I use the wrong method by inviting them via Share > Invite Users? Should I be using another method to give them access during this beta period?
Additionally, how can I remove these 13 users from being counted as team members and make sure they’re only treated as regular registered users?
Okay, that’s one of the new plans, and it is indeed limited to 20 users.
So what you are seeing sounds correct.
Team members are different, they are editors of your Apps. You can see a list of Team Members in the Members section of your Glide dashboard. You are limited to 5 team members on the Team plan.
Ok, so I suppose this user limit only applies while the app is set to Private, correct? If I were to make the app Public, would I then have unlimited users?
No, it makes no difference whether the App is set to public or private, the same limit applies.
You can purchase additional users at $3 each per month.
The only plan that gives unlimited users is the Maker plan, but that has other limitations. Most notably it’s restricted to personal users only.
So, it’s not possible to have more than 20 monthly active users in Glide… I didn’t expect that
I would switch to the Maker plan, but in that case, I wouldn’t have access to the Glide API features, which my app relies on…
This really limits the potential use cases for Glide. Very disappointing news