Relevance AI's Settings page hadn't been touched since the product first launched. While the rest of the platform had evolved into a polished, on-brand experience, settings had been left behind.

For a product asking enterprise customers to centralise sensitive workflows, the settings page was sending the wrong signal. It looked unprofessional next to the rest of the experience.

I led the design uplift of the entire settings experience, scoped a new Data Management page with PII masking and S3 export, and packaged the work into engineering-ready Linear tickets.

https://www.loom.com/share/b0afe4b55bc143a98cf72386d43c65fc

The Challenge

A settings page felt like an entirely different app

Click into it from the dashboard, and you'd land in what felt like a completely separate app. Different spacing, different table styles, broken visual logic, and core features buried in confusing layouts.

For enterprise customers trusting us with their data, this was a credibility problem and when I audited the experience, the problems compounded quickly.

❌ Visual and UX issues

• The page didn't share the platform's design system, branding, or layout patterns
• Primary CTAs weren't clearly defined on each page, leaving users unsure what to do next
• The side menu broke continuity with the dashboard, making settings feel like a detour rather than part of the product

❌ Hidden and broken features

• Adding users to an entire organisation was technically possible but completely hidden. Customers thought they could only add users to individual projects
• Table data was ambiguous
• There was no where to manage platform event data exports or sensitive data masking.

Dashboard

Before: Settings, Plan & Billing

Before: Settings, Projects page