...

• Users will consume this information beginning in one of two places: the home page (pre or post login) or from an application feature page
  • The links from the login page and post-login home page in the customer-specific deployment of the app will take the user to their program-specific page, that is not listed in the hierarchy (to make it less likely that customers will view other customer-specific stuff and get confused)
  • The feature links, such as from a training set page, will link to a public page that is generic to the application, such as the Train to Score page in the main set
• The customer-specific page for each customer will include ALL the information that is unique to the customer along with an annotated, link-based guide for using the application, e.g., start here, do this, the documentation calls it "X," but you will see "Y" and so on.
• Doing it this way means most links are stable across customers and only two links from the customer-instance of the application need to be changed on a per-customer basis: links from the login page and post-login home page in the customer-specific deployment of the app

For a demo, I will start with the AZ page, explain that it will be the starting place for most users, and then proceed through a typical use case.

Understand Scoring Online User Guide

...