"Viewer" permissions settings not working.

Permanently deleted user

February 17, 2018 18:08

We have a two sites and each site has two viewers in them. We have tried about every combination possible to allow a specific Windows Integrated - Windows Group access to one but not both viewers in the "Viewers" section of the permissions page on the site. No matter the combination, the viewers both load. We have only a single windows group in play, and the "Site" is checked green, "Viewers" is checked green, "Viewer1" is checked green, "Viewer2" is checked RED.... Viewer1 and Viewer2 both load for the user?

 

According to Mike's response here: https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&#!/feedtype=SINGLE_QUESTION_DETAIL&criteria=ALLQUESTIONS&id=906f2000000fxwpAAA

 

The only permissions that can be set are : map services, map layers, and site workflows.

 

Is that the case? If so, why are other options even present on the Permissions page? This is very confusing and not very intuitive. Am I missing something?

0

• 

  Nico Burgerhart

  February 17, 2018 21:35

  The HTML5 Viewer does not use viewer permissions—only the Geocortex Mobile App Framework uses viewer permissions. This means that viewer permissions do not affect whether a user can launch an HTML5 viewer in a browser. In particular, Deny permission does not prevent users from launching the viewer in a browser. This is indeed not very intuitive.

  0
• 

  Permanently deleted user

  February 18, 2018 16:15

  I guess I was thinking the Viewer permission settings would control whether or not the user would get the "Access Denied" message on screen. That was my hope, that the user could attempt to open the viewer in a browser, but if they belong to a Windows group that had been blocked, that they would see an "Access Denied" message in the viewer... the same message a user sees when you explicitly grant (green check) permission to a "Site" and a user that is not in that group attempts to open the Viewer. This would be a nice enhancement... or links to the help page from the permission screen would also be beneficial as the UI somewhat goes against intuition by not doing what it seems like it's allowing you to do. Anyway, we are going to work-around this by creating additional sites. It's dual maintenance but at least it's clear on who has access to what.

  0
• 

  Permanently deleted user

  February 18, 2018 16:20

  Edit... there is a help link on the permissions page... I just missed it.

  0
• 

  Andrew Vitale

  July 02, 2018 15:47

  I am finding myself in a very similar scenario.  I have a request from management to make a Site visible to users outside of my organization, but in a “View Only” capacity.  We do not want to give these outside users the ability to download or export any of this data (sensitive information), but we are OK with them viewing and generating pre-approved reports.  My vision is to create a different Viewer in this existing Site and, based on users permissions, automatically redirect them to that particular viewer in that Site.  When they log out, have them be redirected back to the “Default” (or publically available) viewer. 

   

   

   

  The UI for these setting are not terribly intuitive, as was already stated here.  

   

   

   

  Lance, did you find an acceptable work around for this?  I understand I can build a new viewer in the same Essentials Site and give these outside users the individual URL to that particular Site/Viewer combination.  But this seems a bit too burdensome and potentially confusing to these outside users.  If this is not possible out of the box, am I looking at creating a workflow for this capability? 

   

   

   

  Any insight would be appreciated.  Thanks!

  0

Please sign in to leave a comment.