Feature Request: Guest Access / Lazy Authentication for Dashboard and Browsing

[amina69]

🎯 Objective

Allow users to fully browse the website and view all dashboards as an unauthenticated guest. Users should only be prompted to Sign Up or Log In when they attempt to perform an interactive action (e.g., saving data, creating configurations, posting comments, or accessing private settings).

---

👤 User Story

As a prospective or casual visitor,
I want to explore the website and view the public dashboards without creating an account immediately,
So that I can understand the value of the platform before committing to a signup process.

---

📋 Acceptance Criteria

1. Public Browsing (Guest Mode)

• Unauthenticated users can access the homepage and navigate through all main dashboard views.
• Dashboard metrics, charts, and data visualizations should render fully using public or placeholder/demo data.
• A subtle, non-intrusive banner or banner message can be displayed suggesting users login to save their progress (optional, up for design review).

2. Interactive Action Gates (Auth Wall)

• If a guest clicks an interactive button (e.g., “Save”, “Create New”, “Export”, “Submit”), the action is intercepted.
• Instead of performing the action, a modal or redirect should prompt the user to Sign Up or Log In.
• Crucial: After a successful authentication, the user should be automatically redirected back to the exact dashboard page they were viewing, ideally with their pending action preserved if technically feasible.

3. State Management

• Ensure API endpoints supporting the dashboard browsing do not require a bearer token or session cookie for public data reads.

---

🛠️ Proposed Technical Implementation Plan

1. Frontend Routing: Update router guards to allow guest access to dashboard paths (remove mandatory authentication middleware checks from browsing routes).
2. UI Interceptors: Wrap interactive components in an authentication check wrapper or trigger an auth modal via a global state manager (e.g., Redux, Context, Pinia) when an unauthorized interaction occurs.
3. Backend Support: Ensure public GET requests to dashboard analytics bypass auth middleware on the server side.

🎨 Design & UX Notes

• The login prompt shouldn't feel like an aggressive roadblock; it should clearly explain why they need an account at that specific moment (e.g., "Sign up to save this custom dashboard configuration").

[Deyanju23]

@Deyanju23 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Can i work on this please?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Deyanju23 to this issue.

[drips-wave]

Congratulations, @Deyanju23! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @Deyanju23: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊