Back to work
05Case Study · Module 03 · 2025

Admin Dashboard.

The platform side of the Serenepass marketplace — a focused console for the Serenepass team to approve hotels, moderate offers, oversee bookings and watch commission revenue in one place.

Role
UI/UX Designer
Type
SaaS · Operator Console
Module
03 of 04
Tools
Figma · Lovable · ChatGPT
Serenepass admin dashboard overview
01Module Overview

The control room for a two-sided marketplace.

The Admin Dashboard is where the Serenepass team runs the platform: onboarding hotel partners, moderating the offers that reach guests, keeping the bookings ledger clean and watching commission revenue roll up across every property. It sits alongside the Marketplace and the Hotel Dashboard as the third connected surface in the product.

02Problem

Two sides, one team, no single source of truth.

Before this dashboard, hotel onboarding, offer reviews, refunds and revenue reporting lived in spreadsheets and inboxes. Approving a new property meant chasing documents across email; resolving a refund meant pinging the hotel on WhatsApp. The platform team needed one console that mirrored the operator and guest surfaces without becoming a second job to learn.
03Admin Roles

Scoped access, shared chrome.

Super Admin

Full access — platform settings, commission, payouts and admin roles.

Moderator

Approves hotels and offers, resolves refunds, suspends users — no platform config.

Finance

Reports, commission breakdowns, payouts and bank info — read-only on moderation.

04Information Architecture

Eight sections, one sidebar.

Dashboard·
Hotels·
Offers·
Bookings·
Users·
Reports·
Payments·
Settings
05Final Screens

Ten screens, one console.

Every screen reuses the same KPI strip, filter row and tabbed table — so a Moderator who learns Hotels already knows Offers, Bookings and Users.

Login — Serenepass Admin Dashboard
Login

A focused single-card sign-in over a venue hero, with EN/AR toggle and Remember Me — the same brand moment used across all four Serenepass surfaces.

Dashboard Overview — Serenepass Admin Dashboard
Dashboard Overview

Four platform KPIs (Total Hotels, Active Offers, Total Bookings, Total Revenue with commission) above three Quick Actions that surface the work admins actually open the console for: approve hotels, review offers, resolve refunds.

Hotels Management — Serenepass Admin Dashboard
Hotels Management

Status KPIs + filters (status · location · date) above a tabbed table — All / Active / Pending / Suspended. Inline view, edit and suspend actions keep moderation a one-click loop.

Hotel Profile — Pending Approval — Serenepass Admin Dashboard
Hotel Profile — Pending Approval

Contact person, login info, hotel imagery, and a Documents Verification block (trade license, tourism license, Emirates ID) sit beside large Reject / Approve actions — every signal an admin needs to decide, on one page.

Hotel Profile — Performance — Serenepass Admin Dashboard
Hotel Profile — Performance

Approved hotels open into a four-tile performance summary (Offers · Bookings · Revenue · Pending Payouts) with tabbed sub-views for Offers, Bookings, Payments, Bank Info and Contact.

Offers Management — Serenepass Admin Dashboard
Offers Management

Cross-hotel offer moderation with status, category, duration and hotel filters; tabs split All · Active · Pending · Expired · Suspended so the review queue stays one click away.

Bookings Management — Serenepass Admin Dashboard
Bookings Management

Platform-wide bookings ledger with payment-status filter and inline confirm / cancel / refund actions — the same row model as the Hotel Dashboard, scoped to every property at once.

Users Management — Serenepass Admin Dashboard
Users Management

Guest accounts with role, status, join date and last-login columns; suspend, resume and delete live inline so support can act without leaving the table.

Reports & Analytics — Serenepass Admin Dashboard
Reports & Analytics

Total Sales, Net Revenue, Refund Amounts and Total Bookings KPIs over a 12-month revenue trend and a Top 5 Hotels by Revenue chart, with tabbed sub-reports for Revenue, Booking Trends and Commission Breakdown — and a one-click PDF export.

Settings — Platform Configuration — Serenepass Admin Dashboard
Settings — Platform Configuration

Tabbed settings (Platform · Payment Gateways · Commission · Notifications · Admin Roles) with grouped Branding and Localization cards — every platform-wide lever in one place, with explicit Save / Discard.

06Key UX Decisions

Where the design earned its keep.

Quick Actions over a feed

Approve Hotels, Review Offers and Resolve Refunds sit above the fold with live counters — the admin's three real jobs, not a generic notification feed.

One-page hotel approval

Contact, login, imagery and document verification share a single screen with the Approve / Reject actions, so no decision needs two tabs.

Commission transparency mirrored

Gross · Commission · Net columns from the Hotel Dashboard reappear in Reports and the per-hotel Payments tab — the same money model from guest to platform.

Inline moderation

View / approve / reject / suspend live in the table row across Hotels, Offers, Bookings and Users — opening a record is for context, not for action.

Tabbed sub-views, shared chrome

Every management page uses the same KPI strip → filters → tabbed table pattern, so admins learn the console once.

EN/AR everywhere

The language switch in the header persists across every page, matching the guest and operator surfaces and respecting the Gulf market.

07Design System

One language across guest, hotel and admin.

The console reuses the marketplace's deep navy + heritage gold palette, the same Display / Body type pair, and the same primitives from the Hotel Dashboard — KPI tiles, filter chips, tabbed tables, inline action icons, status pills and the EN/AR header switch. Admins, operators and guests all live inside one design language.
08Outcome

One console, three audiences.

The Admin Dashboard closes the loop with the Marketplace and the Hotel Dashboard: hotels are onboarded, offers moderated, refunds resolved and commissions settled — all without leaving a single console, and without the platform team needing a separate tool to learn.