Illustrated beach house on a dune overlooking the coast

Letting customers design their own dashboards

When I inherited the SSO Dashboard, MLSs could already change their screens and colors, but the process was slow and clumsy, and everything else came through us: a button here, a message there, an authentication method for one market. Each request became a build, and many of those builds only ever served one MLS. The product could not scale that way.

Working with three engineers, I made customization part of the product instead of part of the implementation process. Admins configure their own vendors, authentication, branding, layout, and permissions, and all of that complexity stays behind the scenes: members keep one simple place to access everything their MLS provides.

RoleSenior Product Designer

ServiceProduct Design, Design Systems, Prototyping

TeamSole designer with three engineers

Editing the dashboard right on the dashboard.

The dashboard had been a predetermined arrangement of products, and every layout change was a customer request.

Cards became configurable objects rather than fixed components. Admins add, remove, move, and resize them directly on the home screen, so what appears, where it appears, and how much space it gets is the MLS’s own call.

Every MLS’s dashboard in its own colors.

The dashboard is the front door an MLS gives its members, and it needed to look like the MLS, not like Remine.

Colors, accent colors, logos, and visual settings are controls in the product, not custom builds. Each organization makes the dashboard reflect its own identity while running on the same underlying system.

Who can see it, and who can change it.

Members needed access scoped to their role, and not everyone on an MLS’s staff should be able to reconfigure the dashboard itself.

Administrative controls manage who can access and who can configure each part of the experience, so flexibility for admins never turns into complexity for members.

Making vendor setup something admins run themselves.

Every MLS offered a different mix of third-party products, each with its own authentication method and SSO connection. Adding or changing one had always meant a request to Remine.

We redesigned how admins add and manage vendor products, including the forms and workflows that configure authentication and SSO connections. A new product goes from decision to live on the dashboard without Remine in the loop.

Visibility into what members actually use.

Once an MLS could shape its own product mix, admins needed to see how members were interacting with it.

Reporting shows how members engage with the products available through their dashboard, in the same design language as the rest of the admin experience.

The same dashboard, sized for a phone.

Agents are on their phones between every appointment, so the dashboard meets them there. Not a stripped-down companion app, the full thing laid out for a smaller screen.

Every product, the same brand, and the same permissions, from a single build. Designed alongside the desktop views, not bolted on after.

Outcome

Self-serve

Vendors, branding, layout, permissions

Configured by admins, not requested

Large-scale MLS customers

Plus their sub-MLSs, all on one build

One front door

For every member

The complexity stays behind the scenes

A fixed product became a configurable platform serving more than eight large-scale MLS customers and their sub-MLSs, with no custom implementations. New requirements that once traveled from customer request through design and engineering now end at an admin opening configuration and making the change.