Use the app's sign-out action, backed by the supported authentication SDK, rather than only hiding the signed-in screen.
The current SDK clears the local app token and asks the server to revoke that person's sessions for the app. Server revocation is best-effort: an offline browser or older deployment may not complete it. Older apps may need the current SDK and authentication template before they behave this way.
Switching accounts
Current sign-out behavior records that the next login should ask the person to sign in again, rather than silently continuing the previous app session. Test sign-out followed by sign-in on your published app, including a second account.
The app's session and the platform's shared sign-in session are different. Signing out of one app is not a promise that every other app or the Overskill dashboard is signed out.
If your app immediately signs the same account back in, ask the builder to check its SDK, login route and published version. Do not solve it by deleting only a visible profile name.
Revoke access is an administrative action that blocks a person from the app. It is not the button ordinary users should use to sign themselves out.