Skip to Content
Trips Enjoy
User Flows

Organization Dashboard

End-to-end flows for the organization dashboard (UF IDs, steps, rules).

Surface: business.trips-enjoy.com (web only for registration; the dashboard is responsive). Roles: organization owner, employee.

Registration

FieldRequiredNotes
Owner full nameYesBecomes the owner account
Owner email and phoneYes, both verifiedD-20
PasswordYesSecond factor set up on first sign-in
CountryYesSets the organization's market, currency, tax rules and time zone
Legal name and trade nameYesArabic and English
Commercial registration numberYes
Tax numberYes where the market requires it
Registration documentsYesCommercial registration, tax certificate; PDF, JPG or PNG up to 10 MB
Business address and categoryYesCategory: school, corporate, religious, tourism, event, other
Billing contactYesEmail for invoices
Plan choiceNoShown without charge; Starter if none (D-77, D-24)

Approval

Application enters the admin queue; the applicant sees "under review" with the 2-working-day target.

Admin checks documents and registry details (manual in phase 1).

Decision: approve (tenant created on the chosen plan or Starter, owner invited); request changes (14 days, reminder day 7, one 7-day extension); reject with reason (appeal within 14 days, re-apply after 30 days).

Every decision notifies the owner in their language.

Flows

UF-ORG-01. First sign-in and setup

Owner signs in with email and password; sets up an SMS or authenticator second factor.

Setup checklist: profile and logo, time zone (defaults from market), invoice settings, first vehicle type, first vehicle, invite staff, onboard own drivers and photographers, payout bank details.

Empty-state home shows the checklist and plan usage.

Rules: FR-ORG-02, FR-EMP-06.

UF-ORG-02. Switch organization

A staff member whose email is listed by several organizations sees the organization switcher.

Choosing one changes the workspace; data from the other is never shown.

Rules: FR-AUTH-07, BRL-01.

UF-ORG-03. Invite and manage employees

Invite by email with a permission template (Operations, Finance, Support, Manager) or custom permissions across trips, bookings, operations, accounting, coupons, employees, fleet, subscription, integrations, analytics.

Link valid 7 days; on first sign-in the employee sets a password and second factor.

Change permissions (history shows actor, time, before and after); suspend or remove (access ends at once).

Edge case: the plan's employee limit is reached; the invite is blocked with an upgrade prompt. Rules: FR-EMP-01 to FR-EMP-06.

UF-ORG-04. Fleet

Vehicle types: name, seat grid, labeled seats, accessible and blocked seats; archive.

Vehicles: plate, model, year, type, seats (must match), registration validity.

Rules: FR-FLT-01, FR-FLT-02, FR-FLT-06.

UF-ORG-05. Own drivers and photographers

Invite by SMS or email (valid 7 days) with name, phone, country; license for drivers.

They appear only in this organization's lists and are accepted on assignment.

Removing one releases their future assignments and alerts operations.

Rules: FR-ORG-03, BRL-05.

UF-ORG-06. Create a trip (wizard)

Basics: title, description, category, cover image, language.

Schedule and route: start and end, time zone, pickup points, stops, destination on a map.

Vehicles: add vehicles up to the plan limit, each with a vehicle type and label.

Staffing: per vehicle, driver (own, or platform through a deal on Growth and Enterprise) and moderator (with phone); trip photographer (own or platform).

Programs: add programs with pricing model, price or tiers, type flags, capacity; up to the plan limit.

Seating: company-assigned or self-select (Growth and Enterprise); priority window for Explorer and VIP.

Pricing and capacity: base price in the market currency; child tracking switch (Growth and Enterprise).

Publish: save draft, publish publicly, or publish to a target list.

Edge cases: missing step blocks publishing and names the step; monthly active-trip limit reached; market not live. Rules: FR-TRIP-01 to FR-TRIP-03, FR-TRIP-07, FR-PRG-01 to FR-PRG-06, FR-ORG-05, FR-SEAT-07.

The full state machine, including cancellation and remedy paths, is the trip lifecycle workflow.

UF-ORG-07. Hire a platform supplier (deal)

Search platform drivers or photographers by date availability, region, rating badge and price.

Propose a price for a vehicle or the trip; the supplier sees trip, route, date, vehicle and pay.

Counter back and forth with no round limit; each offer expires 72 hours after the last counter.

Accept: when both sides accept the same terms, the deal is finalized and the supplier assigned.

Rejected or expired: the slot reopens for another supplier.

Rules: FR-NEG-01 to FR-NEG-07, BRL-04, BRL-26.

UF-ORG-08. Move a trip to Ready

Staffing board shows each vehicle's driver and moderator status and each open deal.

Ready is refused with the list of gaps until every vehicle is staffed and every deal finalized.

A staffing-gap email arrives 48 hours before departure; reassignment is allowed until 24 hours before.

Rules: FR-STF-03, FR-STF-07, BRL-07.

UF-ORG-09. Manage bookings and seats

Bookings list with filters by state, vehicle and program; passenger roster.

Booking detail: passengers, seats, programs, totals, payments, refunds, notes.

Seat map in assign mode: drag passengers to seats; conflicts refused.

Handle cancellation requests after the policy cut-off within 2 working days.

Rules: FR-SEAT-06, FR-BKG-04.

UF-ORG-10. Change a trip after bookings

Edit programs, vehicles, seat mode or times.

If confirmed bookings are affected, the system lists them and requires sending remedy offers before saving.

Travelers have 7 days to choose; unresolved cases go to admin.

Rules: FR-TRIP-06, BRL-24.

UF-ORG-11. Cancel a trip

Cancel with a reason before the trip starts; the preview shows bookings and the full refund total.

All confirmed bookings are cancelled and refunded in full; suppliers and travelers are notified.

In Progress trips cannot be cancelled; the screen points to incident handling.

Rules: FR-BKG-06, BRL-30.

UF-ORG-12. Live operations

Trip command view on departure day: vehicles on a map, occupancy per vehicle, check-ins as they happen, incidents in real time.

Look up any passenger to see their vehicle and status.

Review end-of-trip reports and add a note.

Rules: FR-TRK-01, FR-TRK-03, FR-CHK-06, FR-CHK-07, FR-MOD-06.

UF-ORG-13. Coupons

Create, pause, resume and revoke coupons for own trips; per-coupon analytics with 7, 30 and 90-day presets; count limited by plan (active and paused). Rules: FR-CPN-01, FR-CPN-07, FR-CPN-08.

UF-ORG-14. Invoices

B2C invoices issue automatically on confirmation; B2B when the buyer gave a tax number.

Issue a manual invoice for a group or corporate buyer.

Corrections by credit note only.

Rules: FR-ORG-07, BRL-28.

UF-ORG-15. Accounting and settlements

Trip accounting: base revenue, program revenue, coupon impact, supplier costs, commission, gateway fees.

Ledger browser with filters; exports by plan.

Settlements: one per completed trip, with lines per party, status, and closure when paid and dispute-free.

Rules: FR-ACC-02, FR-ACC-05 to FR-ACC-07.

UF-ORG-16. Analytics

Trip, page, customer and provider analytics (Growth basic, Enterprise full), date presets and export. Rules: FR-ANL-01, FR-ANL-04.

UF-ORG-17. CRM and webhooks

Connect a CRM; register webhook endpoints and choose events.

See deliveries, failures and replay any delivery for 7 days; rotate the secret (old secret valid 24 hours).

Rules: FR-ORG-06.

UF-ORG-18. Plan and billing

Current plan, usage against limits, renewal date, invoices.

Upgrade (at once, prorated) or downgrade (cycle end); cancel.

Grace banner during failed renewals with retry dates.

Rules: FR-SUB-02 to FR-SUB-04, FR-SUB-08.

UF-ORG-19. Child-safety reports

Staff file a report about a child passenger; the case routes to the escalation contact; the list shows status. Rules: FR-PAR-07.

UF-ORG-20. Branding (Enterprise)

Logo and colors applied to public trip pages, emails and invoices. Rules: FR-ORG-08.

UF-ORG-21. Employee first sign-in

Actor: employee. Trigger: opening the invitation link within its 7-day life.

Sets a password from the invitation email; the link dies after 7 days and the owner can resend.

Enables a second factor (SMS or authenticator); organization staff enter it at every sign-in.

Lands in the organization workspace with only the permissions the owner granted.

Edge cases: expired link (owner resends); lost second factor (owner resets through support). Rules: FR-ORG-03, FR-EMP-02, FR-AUTH-04.

UF-ORG-22. Coupon lifecycle

Actor: organization owner or employee with the coupon permission. Trigger: creating a campaign.

Creates the coupon: type, stackability, window, usage limits, minimum spend; it activates at once or at the window start.

Watches usage on the coupon list; pauses and resumes at any time.

Revokes with a reason when the campaign ends; revoked codes fail with not found.

Refunds reverse redemptions: usage counts fall back, and an Exhausted coupon returns to Active if its window is still open.

Suspicious redemptions raise an abuse flag for admin review within 2 working days.

Edge cases: exhaustion mid-checkout (the code fails cleanly at Summary); per-user limits freed by refunds. Rules: FR-CPN-04, FR-CPN-05, FR-CPN-06, FR-CPN-07.

UF-ORG-23. Fleet mid-lifecycle

Actor: organization owner or fleet manager. Trigger: changing the fleet while trips exist.

Adds a vehicle with its type and label; the seat map derives from the vehicle type's rows and layout.

Assigns vehicles to trips up to the per-trip limit; labels flow through to published trip pages and tickets.

Removes a vehicle only when no future bookings depend on it; otherwise the removal names the blocking trips.

Edge cases: seat mode changes on a trip with bookings follow the trip-change remedy rules. Rules: FR-ORG-04, FR-FLT-03, FR-FLT-04, FR-FLT-05, FR-SEAT-01.

UF-ORG-24. Consume the public API

Actor: organization developer. Trigger: integrating bookings, trips or webhooks with external systems.

Creates an API key from organization settings; the key carries the organization's plan limits.

Signs requests with the key; reads trips, bookings and availability through the public endpoints.

Registers a webhook endpoint and verifies the signature; deliveries retry 5 times over 24 hours and remain replayable for 7 days.

Rotates the signing secret with a 24-hour overlap so in-flight deliveries keep validating.

Edge cases: secret rotation (old secret valid 24 hours); missed events (replay from the event log). Rules: FR-API-01 to FR-API-07, FR-ORG-06.

On this page