Access governance for a growing platform
I designed the license management and distribution model for Creo+, so admins could see who holds what across seats, roles, and products, and grant or reassign access without guesswork.
Access lived in spreadsheets, not in the product.
As Creo+ grew across seats, roles, and bundled products, admins had no single place to see who held which license, or why. Reassigning a seat when someone left a team meant cross-checking spreadsheets and filing a support ticket, often with a multi-day turnaround.
Different stakeholders needed different views of the same data: an IT admin wanted seat-level control, a finance stakeholder wanted cost and utilization, and support needed to diagnose access issues fast. No existing view served any of them well.
Three stakeholders, one source of truth
I interviewed IT admins, finance stakeholders, and support engineers to map how each group reasoned about licenses, and where the current tools broke down for them.
Make governance visible, and self-serve
The design brought seat, role, and product data into one governed view, with role-appropriate actions built directly into it, so admins could act without a support ticket.
Governance as a platform principle
This access model shared the same underlying discipline as the history graph and commenting work: give every user, action, and record a clear owner and a clear trail. Here, that meant knowing exactly who could see or touch what, at any moment.
That governance model carried forward directly into how PTC Jetstream manages user rights across its portfolio, not just within a single product.