Hi, There is a plethora of reasons why not to make two web applications. This is very noticeable in a large organization and sometimes it is just far more efficient to have One Web App. Double the product to maintain, double the Change management processes and documents (including docs to maintain), more stuff to, in essence, piss off business (non-GIS and field guys) .. double the 'stuff'. Having one app as the go to is much more efficient in 'SOME' instances. I say some, because it really depends on the business and the ask. One thing that is Super irritating about ESRI is this mentality of Separating eveything. Spin on a map for the basket of layers.. .then another for this... though it might seem like a good idea to keep maps simple, in big organizations, that fails hard. Business wants integration, insight with rich context...one stop place for larger view to the organization. 100's of web maps doesnt work. There will always be the ask for 'but I want some of what is there and other there in this... How this is done... You create multiple ArcGIS Server Services and associate each AD Group Accordingly. Granularity exists. You can have one group only be able to UPDATE and CREATE while another has 'admin' - Update, Query, Create, Delete and another, the view. Or in the Ops case, two layers that they dont want each other to see. View is easy, you hit the MapServer service instead of the FeatureAccess Service. all layers can be added in the web map (or layers in App) and you remove any flagging dialog of 'unable to load layer' so that the other group is not aware that they are 'missing' a layer). As far as the Ops Group A - edit and view a layer that cant see Group B and VisaVersa. is quite easy. Group be isnt part of Groups As Service... layer fails to load (Controlled at ArcGIS Server Level- OR if you want to go fancy, SOI - server Object Interceptor) , Visa Versa. For scenarios that I typically go through where as business wants a layer visible to all or a certain group (VIEW (aka Query only) and wants another separate group to be able to 'edit' - create, update and then another group with Create,update and Delete capability... You have your THREE services (with each of its managed AD groups)... you add the VIEW layer through the MapServer level , you add the editing feature services .. but have the symbology transparent. you remove the layer from the TOC. If you log in as a viewer, you see the one layer... view the content If you log in as Group B - you can click on the viewer layer ... but what you are really clicking on with editing ability is the feature (transparent service). You can now edit (based on settings for that service). We do this quite often.
... View more
If anyone happens to be asking, how does one change this in Portal (Enterprise GIS)... You can change to custom so that any Web Apps built in Portal will reflect the new icon. To make the changes in Portal: (2d and 3d viewer app types) Browse to the Portal Install directory (each Portal if HA) [portal install directory]\apps\webappviewer\images Rename the shortcut.ico to shortcut_ORIG.ico Add your favorite ico that youd like to be used in all web app 2d viewers and name it shortcut.ico You can make the changes for 3d viewers as well. [portal install directory]\apps\webappviewer3D\images
... View more