...
Top Level Navigation: Admin App users in prior releases first select "Settings" (features against their single ODS instance such as Applications, Descriptors, Reports) or "Global" (Vendors and Claim Sets). The Vendors page already suggests, even, the natural workflow: define Vendors, define Applications within those Vendors, obtains Keys. Given the natural order of that workflow, we recommend swapping the order of the "Settings" and "Global" navigation items, and then renaming "Settings" to "ODS Instances":
Work in Progress: Early designs for Multi-Instance predated the above deployment recommendation. They involved defining instances in Admin App using a URL / Key / Secret, and then adding an instance selection drop down within the ODS Instances screen. We're beginning to think that design is mistaken, especially in light of the desire for a single API. Therefore, the pivotal design questions come down to the capabilities of the ODS both present day and in the future for this recommended deployment diagram, and whether key/secret therefore need to be per User, or per User+Instance, etc.
User Management: Roles, Permissions, Registration & Login
...
See User Management for Admin App (Multi-Instance Mode) for technical design of the users/roles/permissions aspects of Multi-Instance.
...