Qejaverse Onboarding Context

What is QejaVerse?

QejaVerse is a real estate platform that connects Property Developers, Real Estate Agents, Legal team and Property Buyers (Clients) through the full property purchase journey — from discovery to signed sale agreements.

Think of it as a shared workspace where:

• Developers list projects, manage units, track reservations, and handle payments
• Agents represent developers, earn commissions, and manage client relationships
• Clients browse properties, make reservations, sign offers, and track payments
• Lawyers review and approve legal documents (offer letters, sale agreements) before they are dispatched to clients

Who are the users?

What does each role do?

Developer

• Creates real estate projects and adds units (apartments, plots, etc.)
• Sets up payment plans and pricing
• Invites Agents to sell on their behalf
• Books units for clients and sends portal invitations
• Manages the full sales pipeline (reservation → offer → payments → sale agreement)
• Invites Lawyers to review legal documents before dispatch

Agent

• Gets invited to projects by Developers
• Represents the Developer to potential buyers
• Manages leads and client relationships
• Earns commission on sales
• Can also self-signup and request to join projects

Client

• Browses properties on the marketplace
• Receives a portal invitation after a Developer reserves a unit for them
• Completes onboarding (identity verification, payment plan selection)
• Signs offer letters and sale agreements electronically
• Makes payments according to their payment schedule
• Tracks their ownership journey on the client dashboard

Lawyer

• Receives a magic-link invitation from a Developer or Admin
• Reviews legal documents (offer letters, sale agreements) for compliance
• Approves or requests changes before documents go to clients
• Has a dedicated legal review dashboard

How do users get access?

There are 4 distinct entry points into the platform:

1. Self-Signup (the "front door")

• User visits the app → clicks Sign Up
• Creates account with email/password OR Google OAuth
• Accepts Terms & Conditions
• Chooses their role (Developer or Agent)
• Lands on their role dashboard

2. Invitation Links (the "side doors")

• Team Invitation: A Developer invites an Agent or Manager to their project via email. The invitee clicks a link, signs up (or logs in if existing), and gets the role automatically.
• Client Portal Invitation: A Developer books a unit for a client, system sends an invite email. Client clicks link, verifies phone via OTP, completes onboarding wizard.
• Lawyer Invitation: Admin/Developer sends a magic-link. Lawyer clicks, gets access to legal review dashboard.

3. Marketplace Discovery (the "discovery door")

• Anonymous user browses public project listings at /discover
• Shows interest in a property → completes a 9-question qualification flow
• If scored as "Hot" lead → offered to self-register as a Client
• If "Warm/Cold" → an agent will contact them

4. Add Role (existing users)

• A user who already has one role (e.g. Agent) can add another role (e.g. Developer)
• Phone verification required
• Both roles accessible via a role switcher in the navigation

Key things to know while testing

• T&C Gate: Every new user MUST accept Terms & Conditions after first login. You cannot bypass this.
• OTP Verification: Phone verification is required for invitations and marketplace flows.
• Emails & OTPs on Staging: This is a staging environment — emails and OTPs are sent to the actual email/phone you enter. However, if you use fake emails or numbers that cannot receive messages, you can retrieve OTPs from the backend. You have been given access to the OTP doctype in the backend (Frappe desk) where all generated OTPs are logged. Navigate to the OTP list to find your code.
• Backend Access: You have Frappe desk accounts with read access to key doctypes (OTP, etc.). Use this to verify data and retrieve codes when testing with fake credentials.
• Google OAuth: Works with any real Google account. Creates a platform account on first use.
• Invitation Tokens: Links expire after 30 days. Email must match exactly.
• Role Gate: Only appears for self-signup users. Invited users skip it (role is pre-assigned).

How to retrieve OTPs and verification codes

When testing with emails/phones that can't receive messages:

1. Log into Frappe desk at https://staging.qejaverse.com (you'll be given credentials)
2. In the search bar, type "OTP" and open the OTP list
3. Find your entry by email or phone number
4. The code and expiry time will be visible

Alternatively, if you use a real email address, OTPs will arrive in your inbox normally.

URLs you'll use

Your testing environment

Bug Reporting

When you find a bug:

1. Mark the test case as FAIL in the spreadsheet
2. In the Notes/Bugs column, include:
   • What actually happened (vs. what was expected)
   • Screenshot if possible (paste link or attach)
   • Browser you used (Chrome, Safari, etc.)
   • Whether you were on mobile or desktop
3. If it's a blocker (prevents you from continuing), flag it immediately to the test coordinator

Read this once, then open your assigned test sheet and start working through it row by row.