# Force sign out and back in?

**URL:** <https://community.glideapps.com/t/force-sign-out-and-back-in/66752>\
**Category:** Ask for Help\
**Created:** [October 4, 2023, 1:27pm UTC](https://community.glideapps.com/t/force-sign-out-and-back-in/66752 "2023-10-04T13:27:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![HeartwoodTreeCo](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/heartwoodtreeco/32/8150_2.png) [@HeartwoodTreeCo](https://community.glideapps.com/u/HeartwoodTreeCo)\
**Post date:** [October 4, 2023, 1:27pm UTC](https://community.glideapps.com/t/force-sign-out-and-back-in/66752/1 "2023-10-04T13:27:09Z")

</div>

I have a public app (It’s really for internal use and could be made private), but it’s public with required sign in. It’s set to collect real email addresses, but virtual email addresses are still showing up. I’m assuming this is because the real email address setting was changed and it doesn’t force users to log out and back in when the setting changes. It’s been this way for many months.

If signing out and back in would result in real email addresses being collected, what would be an easy way to force that to happen? Or should I just make it a private app with the users table if we want to know which employee was making entries?

---

<div class="post-metadata">

**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\
**Post date:** [October 4, 2023, 5:48pm UTC](https://community.glideapps.com/t/force-sign-out-and-back-in/66752/2 "2023-10-04T17:48:01Z")

</div>

> [@HeartwoodTreeCo](#):
>
> If signing out and back in would result in real email addresses being collected, what would be an easy way to force that to happen?

I don’t think this will work. Anonymous emails are still internally linked to the real email address. Signing out and back in would still link the user to the row with the anonymous email.

> [@HeartwoodTreeCo](#):
>
> Or should I just make it a private app with the users table if we want to know which employee was making entries?

This could work, but you would have to delete user records to force people to sign out, then re-add the rows with the correct email so they could be allowed to sign in again. Even though the anonymous email does not match their real email, it’s still internally linked, so just making an app private will not force people out until their user row is actually deleted.

I think you would be better off manually using the email addresses, or possibly force the user to enter and overwrite the email address (not sure if that’s allowed or not). Also consider that you may need to delete user data to ensure that new user rows are created.

> **[Delete User Data](https://www.glideapps.com/docs/essentials/security-and-user-data/delete-user-data)**
>
> Learn how to delete user data securely.