Partner Portal

Each partner signs in on their own, finds the guide they need, and sees where their request stands, without asking on WhatsApp.

Try the demo demo.realo-partner.com How it was built

The Help Center in the Partner Portal, as the project manager sees it: eight categories, each with its guide count (9, 7, 10, 18, 14, 6, 12, 5), “All guides 81”, and an edit-mode button. Demo data. — 1The Help Center, as the project manager sees it: every guide for partners, sorted by topic. Demo data.

The Help Center in the Partner Portal: “All guides 81” and the list of guides, starting with Getting Started. Demo data. — 1The Help Center, as the project manager sees it: every guide for partners, sorted by topic. Demo data.

The mess

The know-how was scattered, and the questions kept coming back.

ReaLo’s operational know-how sat in old categories, general articles and guides in PDF files. Every new partner asked the same questions, and every request got lost in a thread.

Illustration: what know-how in files looks like, several versions of one guide and a question that keeps coming back. Not ReaLo’s files.

The system

One system that every partner signs into on their own.

Every guide for partners together, and a short request form that shows where each request stands. Behind the scenes there’s project management too, and a secure place for passwords and access.

One table, two roles.

The permissions are built into the system itself. Switch roles and see what each one sees.

View as:

Two of the 7 roles

The requests screen as the project manager sees it: every request from every partner, with project management in the menu. Demo data. — 2The requests screen, as a project manager and a reseller partner see it. The same demo data, in excerpts from the screen.

The request-number column on the project manager’s requests screen. Demo data. — 2The requests screen, as a project manager and a reseller partner see it. The same demo data, in excerpts from the screen.

Everyone sees only what’s theirs.

Every user has a role and a scope. The system admin sees everyone; a partner sees only what’s theirs.

Every guide sorted by topic, and editable inside the system
Every request with a status, comments and files, and a record of who did what
Project management: tasks in order, from a ready template
Passwords and access kept somewhere secure, with a record of who opened them
7 roles, and each one sees only their own
Files go straight to cloud storage

User management, as the system admin sees it: name, email, role, status and scope for every user. The reseller partner’s scope is “Partner”, not “Global”. Demo data. — 3User management, as the system admin sees it. Demo data, an excerpt from the screen.

The names column from user management. Demo data. — 3User management, as the system admin sees it. Demo data, an excerpt from the screen.

Now

Before, and now.

Before: A scattered PDF libraryNow: One Help Center, in 8 categories
Before: Requests in threadsNow: Every request with a status, and every partner sees exactly their own
Before: “Who has it?”Now: Every request has an owner and a due date

A small detail from the build

The project manager sees every country, and manages no users.
In the demo, on the role’s card: ProjectsRequestsKnowledge base without User admin
A reseller partner sees only their own requests, and their own chains and stores.
In the demo, on the role’s card: Own requestsOwn chains & stores
Every demo login is a real account, and the data resets every night.
In the bar at the top of every demo screen: the data resets nightly at 04:00 UTC

What I did: Product, scoping, design, full development and launch.
What it runs on: Next.js and Prisma on Neon Postgres. Sign-in through NextAuth, files in Cloudflare R2, all running on Vercel.

Check it yourself