Autodesk SSO setup

Personal data security is a fundamental need for Autodesk and its clients managing team access. SSO reduces the possibility of poor security practices. By automating SSO setup through an intuitive, self-serve application in the Account Portal, we encouraged software administrators to enable SSO, saving time and reducing reliance on support teams.

Problem

SSO adoption was low due to a cumbersome setup process. Administrators had to complete it over the phone with support, including a 72-hour manual domain verification.

Goals

Automate the SSO setup by allowing admins to complete domain verification and configuration in a single, intuitive digital flow. Give them a sense of control and clarity. Expected business results are increased security through broader SSO adoption and a measurable decrease in support call volume.

My role

Created UX, interaction design and user workflow from the ground up.

Leveraged feedback from project managers, engineering, peer designers, and users.

Iterated on task flows, design-copy dynamics, and component selection.

Handed off pixel-perfect mockups and assisted in development and QA.

Initial concepts

I started by gathering the key technical requirements for establishing the SSO connection. The UX challenge was to guide users through a complex, multi-step process. I outlined the initial flow in four high-level steps and presented it in a diagram.

User workflow draft

The initial design concept I drafted used a stepper to show the sequence of all actions and to orient users in the process.

I reviewed the design with the team, and as we explored it further, I identified the need to include additional requirements:

Domains and SSO connections are flexibly interrelated. Users should always have access to both the list of added domains and the list of SSO connections, with the ability to modify either at any time.
Each step in the flow is non-linear. Users can start by either adding a domain or setting up SSO. At any point, they can add another domain, switch to setting up SSO, or pause domain verification and return to it later.
All basic steps include several sub-steps and options to accomplish the tasks.

Based on these findings, I realized that a single linear flow would be lengthy and wouldn’t provide an inside of lists of available domains and connections. In the revised concept, I split the flow into two main parts and added flexibility for users to move back and forth between them.

Revised requirements and user workflow

Technical requirements

Add a domain 
- manually or 
- import CVS
Verify a domain
- customer uploads an HTML file to their website directory or 
- customer ads a TXT record to their domain name system
Link the domain to an SSO connection
- set up an SSO connection
- name connection
- add identity provider
  - automatic setup (file upload) or
  - manual setup
- test your connection
- link the domain
- test connection with users
- turn on SSO
Manage SSO

User workflow

Design overview

With a deeper understanding of the requirements, I structured the design around tabs, enabling users to switch between key parts of the SSO setup while easily referencing domain and connection repositories. Across both flows, I used components such as modals, drawers, and steppers to guide users clearly through each task.

Task 1: Add and Verify Domain