Manage the people who signed up
See who signed in to your app, what the app knows about them, and what you can do with that.
When your app has its own sign-in, AppHandle keeps track of each person who signs in. You can see that list from the desk, and you can decide whether each person may keep using the app. This guide covers what is kept, who can see it, and the controls.
See who signed in
Open the app in your desk. The app's page includes a Your users card, described as the people who signed in to your app with their AppHandle account. It shows a few of them with their name, their email address, and the date they first signed in. Until someone signs in, the card says that no one has signed in yet.
The card shows only the first few people. Select Manage to open the full list.
The full list
Manage opens Settings → App users. The panel is headed App users, and it lists the people who signed in to your published app with their AppHandle account, each with their name, email address and the date they first signed in.
Use the search box, which reads Search by name or email…, to find one person, and Load more as the list grows. Above the list it says how many you are seeing of the total.
Someone you invited to edit the app can open this list and use the controls as well. This is not a list only the owner sees.
This panel is about the people who use your published app. It is not the list of people who build it — that is Team, under the same Settings. A collaborator who has signed in to the app appears here too, marked Team, and their row says Managed under Team: change what they can do there, not here.
Block or remove someone
Each person has two controls.
- Block refuses their next sign-in and ends the session they have now. They stay in the list marked Blocked, and you can unblock them at any time. Blocking asks you to confirm first: they lose access to the app immediately and cannot sign in again.
- Remove ends their session immediately. They can connect again by signing in, so block instead if you want a lasting refusal.
A person you have blocked who tries to sign in sees a page saying Access blocked, with a line that the owner of the app has blocked their access.
What blocking cannot do
On a public app, anyone with the address can read the app's pages without signing in, and blocking does not change that. Blocking stops the person signing in and ends the session they had; it does not stop them reading the app anonymously.
If you need to keep particular people out, make the app private and invite the people who should get in. Choose who can open your app covers the setting.
What the app knows about a person
The app receives a signed-in person's name, their email address, their profile picture if they have one, and a stable identifier for them — the same one each time they sign in, which lets the app tell two people with the same name apart. It receives nothing else: no password, no phone number, and no access to their AppHandle account or their other apps.
What the app can and cannot do
Inside the app itself, the app can only tell who is signed in at that moment. It cannot list everyone who has ever signed in, and it reads only the records each person saved — unless the app has opened that kind of record up to you and your editors, or to everyone who signs in. Who can see your app's data covers that setting. Use the App users list in the desk for the full list.
You can see every record the app has stored by opening the Data tab in the desk, but the tab does not say who saved each one. Who can do what has the details.
Where to go next
Invite people to work on your app covers the people who build the app, Give your app its own sign-in covers adding sign-in in the first place, and Who can do what covers the roles inside an app.