Simplified Account Flow Around Google Sign-In and Strengthened Account Deletion Confirmation
We organized general user login and signup around Google accounts and improved account security by requiring checks and accurate email confirmation during account deletion.
When there are multiple login methods, users easily confuse which account they signed up with, and the risk of the web and Extension having different authentication states increases. We simplified the general user public flow around Google sign-in and organized account deletion to go through a more explicit confirmation process.
Login methods should be simple, and account deletion should be made hard to execute by mistake.
What Changed in This Update
- General user flows for /login and /signup are provided centered on Google sign-in.
- Removed unnecessary password change and reset UI from the public account screen.
- Requires deletion impact guidance and check confirmation before account deletion.
- The user must enter the exact email of the current account to proceed with the deletion request.
- The Extension does not create a separate login authority but uses server binding by checking the 5by.ai web session.
- Maintains a model where tabs and windows in the same Chrome profile share the same web session and Extension state.
How to Verify
- Select Google sign-in on the 5by.ai login or signup screen.
- Check the current login email at /account.
- If account deletion is needed, read the guidance and complete the check and email confirmation.
- If the Extension login status differs, first check the web session in the same Chrome profile.
Example in Actual Usage Flow
For example, to verify this change, the user selects Google sign-in on the 5by.ai login or signup screen. They check the current login email at /account. Then if account deletion is needed, they read the guidance and complete the check and email confirmation. Finally, if the Extension login status differs, they first check the web session in the same Chrome profile. In this flow, the following conditions should also be checked. Account deletion is not automatically executed without explicit user confirmation. Therefore, this update is not just adding one more notice item but enabling the user to check the start, result, and limitations of the feature within the same flow.
Before and After the Change
Before the change, users had to guess this feature or notice from other screens or navigate across multiple pages. After this update, we organized general user login and signup around Google accounts and improved account security by requiring checks and accurate email confirmation during account deletion. However, items where public notices and actual account/runtime status may differ need to be checked separately, and notice text alone should not be interpreted as expanding permissions or availability.
Scope and Things to Note
- Account deletion is not automatically executed without explicit user confirmation.
- The Extension's Sign in does not create its own password or separate access/refresh flow.
- Employee fallback authentication is separated from the general user public UI.
- When using different 5BY.AI accounts simultaneously, the Chrome profile separation model is the standard.
Why This Change Matters in the Overall 5BY.AI Structure
This update addresses convenience improvement and authentication authority integration together. Users log in once on the web and use the same account state managed by the server across the Extension and multiple tabs. Account deletion, conversely, requires stronger confirmation to guarantee user data control and safety.
Criteria for Verifying This Update
- The public screen title, summary, and actual provided feature should describe the same content.
- Adding a new feature should not arbitrarily change existing Saved, Anchor, Handoff, and account flows.
- Conditions that are in preparation or vary by account should be marked separately without exaggerating as fully available.