Clarification on Public - No Sign In

Quick question Hive Mind.

I’ve only made private apps with sign in up until now under my work profile, but my church has asked me to make a simple app for the church to use that has a few features and public to anyone there can use it.

I have to make it under the free version for them to see if they like the potential (I bet they will) before they go to upgrade to a paid plan and let me go wild with the integrations and features :star_struck:

When I go to setup the privacy settings, if I select Public → No Sign In, will that basically mean as many people can use the app as they want and it won’t count towards the 10 users for the Free Plan since they aren’t signing in with an email???

If so, are there cons of doing it this way? Does it affect individual experiences in anyway? Such as if one page on the app has a dropdown box and someone selects an option from it, will that same selection appear on everyone’s screen even if they didn’t select that? I know I won’t have this problem once they upgrade to the paid plan and I have unlimited users and can use USC’s, but again, I’ve never done a free and public app and don’t want to hit limits…

Also, if anyone can use it and not interfere with each other, I do want to make sure a couple of users have “admin” like access to the app to edit things like contact info, about screens, and calendar events. In order to keep everyone from having this ability, I’ve thought about making the ellipsis icon on collections and what not have an option that says something like “Edit (Admin Only)” and it pops up with a number input where the people that have the ability to edit input a code that must match a predetermined code in a table in order to access a new screen that lets them edit and save the fields. Does that sound like a feasible plan, or is there an easier way while keeping this free and public? (I can’t wait for them to upgrade…)

Thanks in advance Hive Mind!

1 Like

Yes. If users don’t sign in, then there is no way to count them as users.

If you use user specific columns to hold the dropdown value, then it won’t be a problem. Different experience for different users.

That’s not secure as anyone can snoop the data and find that code. If it’s only a couple of admin users, why not have optional sign in and set up your edit functionality to only be accessible to those couple admins? You can still whitelist only the admins so you don’t have a bunch of other users signing in for no reason.

So I can use USC’s even though the majority won’t be signing in?

And if I do this Privacy setup instead, I can still have the congregation not count towards the 10 limit, only the admins?

Yes. There is no user to link them to, so they will only store values until the app is closed, but it still works.

If users access the app but don’t sign in, they are not counted. Only users that sign in are counted.

2 Likes

Thanks Jeff, you’re awesome! Have a good day!

1 Like

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.