Skip to Content
Trips Enjoy
User Flows

User Flows

How every role registers, gets approved and uses the platform, with rule traces.

Trips Enjoy: User Flows

Document control

Version 1.0
Date 9 November 2026
Traces to BRD v1.1, SRS v1.1, ERD v1.0

These files describe, for each app and role, how a person registers, how their access is approved, and what they can do once active. Each flow has a UF ID, the actor, the trigger, numbered steps, the rules that apply (BRL, FR), and edge cases. Screens are named by their SCR (web) or MSCR (mobile) IDs from the screen coverage audit where one exists.

Flows by role

RoleRegisters viaApproved byPlan neededLands on
Traveler/register/traveler or the appNobody (active on verification)No (Free default)Trip browse
Organization/register/organization (web only)AdminYes (Starter default)Organization workspace
EmployeeEmail invitationOwner (permissions)Organization's planOrganization workspace
Platform driver/register/driver or the driver appAdminYes (Basic default)Driver home
Platform photographer/register/photographer or the studioAdminYes (Basic default)Studio home
Organization-owned driver or photographerSMS or email invitationOrganization (accepted on assignment)Organization's plan (OD-19)Driver home or studio home, organization-scoped
ModeratorAssignment by organization (phone)OrganizationOD-06Vehicle home
ParentTraveler accountNobody; eligibility by planExplorer or VIPParent tracker
AdminInvitation by Super adminSuper adminStaffAdmin home
  • "Must verify" means a one-time code (BRL-20): 5-minute expiry, 5 wrong codes pause 15 minutes, resend after 45 to 60 seconds.
  • Every registration form records country (BRL-23); the country sets the market (BRL-27).
  • Every plan-limited action can end in the upgrade prompt (UF-SHR-06).
  • Every list and screen exists in Arabic (right to left) and English.
  • Values marked (placeholder) or [OPEN] follow BRD section 11.

On this page