Discover identity systems before proposing single sign on

A network with several identity directories rarely has one answer to a single sign on request. The account executive should inventory users, systems, and decision owners before describing compatibility. Parent accounts and independently supported schools often follow different paths.

Technology chief Arlo says, "Will single sign on work for every user before school starts?" Account executive Mei replies, "We need to review each directory and the people who manage it before we can answer that. Which schools use separate support, and how are parent accounts created today?" Arlo says one school has an outside IT provider and parents use another portal. Mei says, "That gives us two distinct integration questions. I suggest a technical workshop with the school provider, your central team, and the parent portal owner. We can map staff, student, and parent journeys, then agree which connection to validate first."

Mei does not turn a desired calendar date into an installation commitment. She also keeps account architecture separate from a sales demonstration. The workshop produces a shared diagram and a sequence the technical owners can assess.

Draw three user paths for a fictional school network. Practice asking who provisions each account. After roleplay, check whether you named every external system and whether the next meeting includes a person able to answer for it.