Use Cases for Application Login

2810
0
01-30-2014 08:39 AM
ElisabethLandstorfer
New Contributor
Hi everybody,

I'm a little confused about the possible use-cases for App Login.
Technicaly it is clear and the FAQ and the Terms of use are helpfull, but don't answer all questions.
In which scenarios it is allowed to use App Login and when it is necessary to use Named User Login?
e.g. There is company with 600 employe. 50 of them are using Desktop, Collector, publishing content,.... They would need a named user account. The rest (550) wants to see some common organization-only maps. Nothing special, but maps not everybody (public internet) should be able to see. Could they make a webmap, publish it to the organization, develop a webmap app, deploy it on their intranet server and eg integrate the web app in their intranet (and authorize the application via Application Login)? Or does anybody in the compayn needs to have a Named User Login for the subcription?
Or there is allready some solution in place, an non-geo solution with some sort of user management and licensing. And this solution should be geo enabled. eg. with a function to calculate a drivetime around an address, no further sharing or data management with AGOL. Is it necessary that every user of this solution use an Esri named user? Or is it allowed to integrate the drive-time analysis via application login?

Thank you, EL
Tags (2)
0 Kudos
0 Replies