In case of an employee for example where they have information you want to retain from their profile, but you don’t want them to have access anymore because they are terminated.
1 Like
You could at least change the email address to something that would never exist or type in a bunch of random characters. I think that should be enough to immediately boot a user if you are whitelisting you users.
Just note, that something like the email address in the user profile can only be changed via API or directly in the builder.
3 Likes
You can create a column for “Active” as a bolean. Then change the accessibility to the app to only those that have Active checked.
Or you can create a table for previous employees and move their contents to that table. Information still available, but they can no longer log in.
2 Likes
I don’t know if this method would be secure. If a user is still signed in but inactive, they might still be able to access the underlying data because visibility is not a security feature.
This would be viable though as the user row would be taken out of the user table, which would immediately sign them out.
3 Likes
That is an excellent question, there should be a solution for this!
2 Likes
Another solution which might be better is to maintain a separate whitelist table with only email addresses. That table would be separate from the user table. You can remove the user from the whitelist table without interfering with the user table and it should still sign them out immediately.
4 Likes
This is what I do.
2 Likes
Same, this is what I do in some apps.
1 Like
I’m doing a variation of the second suggestion. Thanks!