Redirecting to signup and timeline needs multiple checks (v2)

[NamanTripathi937]

• Redirecting to Signup & Timeline – Multiple Checks

In Avkash, determining whether a user should be redirected to signup, the timeline, or another screen requires multiple checks to ensure a smooth experience.

Steps for Redirection Logic:

1. Check If the User Exists in the System
   • If the user already exists → Redirect to timeline/dashboard.
   • If not, proceed to signup validation.

2. Check If the Organization Exists
   • If the user’s email domain matches an existing org, prompt them to request access or get added by an admin.
   • If no matching org is found → Allow the user to create a new organization.

3. Verify User’s Status in the Org
   • If the user is already part of an org → Redirect them to the timeline.
   • If the user has a pending invite → Show an invite acceptance screen.
   • If the user is not part of any org → Redirect them to the org selection/setup screen.

4. Ensure Role-Based Redirection
   • Admins may have different landing pages (e.g., setup workflows).
   • Regular users should land directly on the timeline.

Additional Considerations:

✅ Session Handling: Ensure session persistence across refreshes.
✅ Error Handling: If API calls fail, provide a fallback screen.
✅ Edge Cases: Handle cases like users who left an org but want to rejoin.