Yea, that flexibility would be ideal IMO, although the registeredLogoutURLs should be workable for us at this point. FWIW that is actually the behavior I assumed before digging into the docs. I'll definitely add the issue to GitHub, as I think it's probably part of the path to getting OIDC Certification which appears to already have an issue.
Thanks!
Sorry for the ambiguous question and suuuuper late reply, I was help hostage by another project. 
..and thanks for the info, that helps me understand its intent.
What I was speaking about is seeing some of the metadata (device name, type) in the "Manage User" -> "Recent Logins" list to differentiate the logins. After some more exploring it does look like it shows up in "Manage User" -> "Session" instead though.
Thanks!
Seems I may have found part of the answer on this GitHub issue.
Looks like the issue went from Backlog, to Designing, back to Designing last month. 
Hopefully that's a sign there is hope. 
Thanks for all the info...
The multiple application route does sound doable with some FA API work (which we'll have anyway) and backend API work on our end. We are looking at an application per customer already, which this would then multiply by the number of 3rd party services we take on, but that's probably not an issue (at this point at least).
We're a pretty small team (4 developers) that's vastly outnumbered by salespeople. 
We'll definitely keep the pro services in mind, but I think there is enough for us to get started with. I have a feeling we'll be moving to the Developer service pretty quickly after launch though. As the LDAP integration and Reactor service is very appealing.
Honestly, thanks for your thoughts and time on this..
-James