INTERNSHIP PROJECT
01 · Ardent Privacy · 2026
Simplifying Consent Management Across Admin, Manager, and
Client Roles
Consent Management · Enterprise SaaS
Role: UX Design Intern
Timeline: Mar – May 2026
Platform: B2B SaaS Web
Team: Solo Designer (Me)
I was the Solo UX Designer on this project. My role was to go through the current design and see what I can do to make it better. The project ran from March to May 2026, interspersed with other work rather than as a single continuous sprint. While I consulted the team to discuss my ideas and get feedback, this work was entirely my own.
Hi!
MY ROLE
BRIEF
One product. Three users. Three completely different problems.
Ardent Privacy's Data Discovery dashboard helps enterprise data privacy teams identify and manage sensitive data across their systems. The existing design had grown fragmented over time with six separate risk cards, inconsistent labeling, and visualizations that were hard to read at a glance. I led the UX redesign of this dashboard, working closely with the engineer who built the original version, to make it clearer and more usable for the range of stakeholders who actually rely on it.
PROBLEM
Same data. Three completely different mental models.
The signal to redesign came from multiple directions before it became a formal project. Client and internal demos had repeatedly flagged the existing dashboard as unintuitive, something prospective and current customers struggled to read at a glance. Eventually, our CEO caught the same issue firsthand during a demo, which turned it into a priority.
STARTING POINT
The design existed. The hierarchy didn’t.
There was already an existing version of the dashboard. In the CEO’s own words, it needed visual improvements and better UI. Talking to him, the engineers, and internal managers (direct client access wasn’t available to me as an intern), the core issue became clear. The dashboard showed everything at once. Every metric, every card, at full depth, all the time. The data was correct. The hierarchy wasn’t.
Starting point: The existing design
CHALLENGE
“The CEO wanted maximum information at first glance. I believed the best dashboards answer one question immediately and then earn the right to go deeper.”
The CEO wanted density which meant every metric visible at first glance. His logic was sound: enterprise users are power users. They want data, don’t hide it. I thought showing everything at once and making information accessible weren’t the same thing. In a platform where Admins manage 30+ applications, cognitive overload becomes a trust problem. So instead of pushing back and losing, I aimed to find a solution that gave him what he wanted while giving users what they needed.
SOLUTION
Progressive disclosure through flip cards.
Default state : key metrics at a glance
Flipped state : full application detail on demand
Each application tile shows a default state, the name, status, key metrics. Enough to scan. Enough to know everything’s okay. Flip it, and you get the second layer: App ID, Tenant ID, Host IP, assigned manager. Everything the CEO wanted visible, accessible on demand rather than all at once. Nothing hidden. Nothing overwhelming. The mechanic made it into the final product.
Final Admin Dashboard : annotated
DESIGN
Same system. Different perspective.
Admin Dashboard
Top row answers ‘is everything okay?’ in one scan. ‘Today’s Overview’ panel surfaces what needs action. Application carousel with flip cards below. Trend graph and platform breakdown at the bottom. Priority first, detail below.
E6E6E6
Manager Dashboard
Scoped to their applications from the start. The flipped card shows dialog lists with language versions and approval status, not just what exists, but where it’s stuck and who has it.
Client Dashboard
The most restrained design of the three. Consent overview in plain language, a full activity log showing what was allowed or denied per dialog, and a ‘Modify Consent’ button on every row. Their data, their terms, their control.
OUTCOME
Shipped. Used. In production.
Three role-based dashboards shipped into the live TurtleShield UCM product. The flip-card progressive disclosure mechanism, proposed against initial pushback, is in the final product used by enterprise clients today.
MY CONTRIBUTION
End-to-end UI design across all three roles · Information architecture ·
Progressive disclosure mechanic (flip cards) · Stakeholder alignment · Full Figma handoff
TurtleShield UCM : final delivery
REFLECTION
What I’d do with more time.
With more time, I’d push for lightweight user testing, even with internal stakeholders playing roles. Most of my decisions came from CEO and engineer conversations, which is valuable but not the same as watching someone misread something in real time.
The notification system is also a space I’d develop further. There’s a more robust, async, role-filtered version of the ‘Today’s Overview’ panel that I’d want to build properly.
Let's Create Something Amazing Together!
Got a project in mind? Need a design buddy? Or just want to chat about coffee and pixels?
Aasmita Bhattacharya | 2026
