A tool that helps IT and security teams keep track of digital certificates across a company, and replace the ones about to expire before they cause a problem.
Every computer or piece of software that connects securely to something else relies on a digital certificate, a kind of ID card that proves the connection can be trusted. Certificates aren't permanent. They expire on a set schedule, and an expired one can break a connection or open a security gap.
Certificate Manager is the part of Tanium that keeps track of every certificate across a company's computers, flags the ones expiring soon, and walks someone through replacing them before that happens. It's used by IT and security teams responsible for making sure none of a company's certificates lapse unnoticed.
Replacing a certificate is a multi-step process:
Before this redesign, each of those steps lived on different pages — a certificate inventory page, an activity log, and a certificate detail page. The person doing the replacement had to hold the sequence in their head and navigate the product to match it, rather than the product guiding them through it.
I consolidated all of it into a single certificate inventory page with a streamlined replacement process. Every certificate's replacement status now shows directly in the list, which step it's on, and how many steps remain, so a team can see the state of every certificate in the company at a glance.
Replacing a certificate became a short wizard, launched directly from the inventory grid instead of a separate page. It walks a user through the five steps in order and always shows which step is current and which steps are already done.
I designed every state the wizard could be in for each of the five steps, so engineering had a complete reference for how the product should behave at every point in the process.
Instead of a separate detail page, a certificate's full information opens in a side panel next to the grid. A user can check on one certificate, or see exactly where a replacement stands across every computer it affects, without losing their place in the list.
This project received early positive feedback from users who reviewed the designs, but it didn't ship because the platform it was built for is being phased out in favor of a new site-wide architecture. I'm including it because the design process and the problem it solved demonstrate how I approached a fragmented, multi-step workflow.