Select to view content in your preferred language

Restrict Editing to Specific Users in Public Apps

317
3
Jump to solution
05-29-2024 04:35 PM
ZacharyUhlmann1
Occasional Contributor III

I have a Viewer Attachment App that needs to be viewable to the public with editing restricted to specific users. 

I can achieve this at the Hosted Feature Layer level via Shared Access Groups:

Is it possible to assign the editing capability of a public hosted feature layer to specific members...     

And based on User Role:

Access editing capabilities depending on role

These work on the Feature Layer but when it is featured in the Viewer Attachment App, these settings appear to be superseded and editing is disabled.

Note: 1) Editing is disabled in the settings of Feature Layer. 2) Editing capabilities were recently added to Attachment Viewer.

Thanks,

Zach

0 Kudos
1 Solution

Accepted Solutions
ChristopherCounsell
MVP Regular Contributor

You should:

  • Create a Hosted Feature Layer View (editing enabled)
  • Create a map and web app for editing
  • Share both to your internal group
  • Create a 2nd Hosted Feature Layer View (editing disabled, potentially filtered etc)
  • Created a second map and web app for public viewing
  • Share the second map, web app and public view, publicly.

Don't share the Hosted Feature Layer, ever, only the views.

The shared access update group is not really designed for feature editing. It's more for other GIS users to update the content - the map/app - without being the owner.

This sets you up way better in the longer run. Secure access to editing your data, filtering/field control, and the ability to share/unshare content with the public, without impacting other internal users.

View solution in original post

3 Replies
ChristopherCounsell
MVP Regular Contributor

You should:

  • Create a Hosted Feature Layer View (editing enabled)
  • Create a map and web app for editing
  • Share both to your internal group
  • Create a 2nd Hosted Feature Layer View (editing disabled, potentially filtered etc)
  • Created a second map and web app for public viewing
  • Share the second map, web app and public view, publicly.

Don't share the Hosted Feature Layer, ever, only the views.

The shared access update group is not really designed for feature editing. It's more for other GIS users to update the content - the map/app - without being the owner.

This sets you up way better in the longer run. Secure access to editing your data, filtering/field control, and the ability to share/unshare content with the public, without impacting other internal users.

ZacharyUhlmann1
Occasional Contributor III

Hi Chris,

Thank you!  This worked.  I struggled at the end because instead of re-creating the map from scratch directly with the View Layers, I tried to re-source the layers in the original map from the JSON in AGOL - Assist ( HERE ).  This worked, up until I attempted to open the Viewing App outside of my Organizational Account.  That was baffling, but unrelated to your post.  I resorted to recreating the map and following your protocol verbatim.

Also, I didn't realize that folks are required to have an AGOL account of some sort to access the app.  I assume there is a way to forego this requirement since we use ESRI Apps ALL THE TIME embedded in various websites.  Do you know a way to enable use without logging into an AGOl account?

Thanks again - Zach

ChristopherCounsell
MVP Regular Contributor

Please note the ArcGIS Online assistant is not an officially supported tool and making direct edits to the JSON can break your content. I would not recommend it except when required and with care.

ArcGIS Online content not shared publicly will not be accessible to users without an 'organizational' (paid) user account.

You can share the content publicly - maps, apps and layers - but would need to be aware of the editing/data security for this content.

0 Kudos