nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Restrict editing to authorized users while leaving the map viewable to the public

BrettGreenfield__DNR_

I've created a service that will be made available to the public which expects to see fairly regular updates. Unfortunately, now that I've created the dataset it's leaving my hands, and the group that plans on making the updates doesn't have anyone with ArcMap on their computer, thus any updates would have to go through an ArcGIS Online map. I know I can configure a service to allow editing, but my concern is that ANYONE (with the know-how) could also edit the service and make unwanted changes. I also know I can allow access only to a private group, but then the public can't view the service.

Is there a way to limit the editing capabilities to certain people, while keeping the service viewable to the public? I was thinking there might be a way to create a separate version of the service with editing capabilities, open it to a private group, and synch the public version of the service to the private version, but I'm not sure if that's possible.

Vind meer berichten getagd met

Accepted answers

All comments

MikeMinamiP1

Updated November 7, 2017

The way to do this is to create a hosted feature layer view. Learn more about hosted feature layer views here...Create hosted feature layer views—ArcGIS Online Help | ArcGIS

-------------------------

Original post

There are several options:

You can disable editing on the layer inside the web map. This will remove the Edit menu. However, a savvy user could enable it in the web map and still edit it.

You can embed the map in a web page or create a web mapping application. The user won't be able to enable editing here, but if the features are still public, they can be edited.

Disable editing on the feature layer itself. This will prevent editing at all. When you want to update the data, unshare it and enable editing. This means while updating, the map will not be available.

Administrators have the ability to open a feature layer with full editing capabilities. This could be a way to update the features while still keeping the layer publicly available. However, your editors would then need to have the role of administrator.

Published a tiled layer from the feature layer. The tiled layer would need to be updated whenever the features are updated. This can get costly and time consuming to recreate tiles.

Hope this helps,

Mike

EMiller_2

Thank you for the thread -- I am having the same issue. In my case, I have created a small group of 2 or 3 editors who will be making edits to the feature layer in the field using Connector for ArcGIS on tablet devices, adding photos as attachments.

It would be great to be able to have a public version of my ArcGIS Online map where the data is viewable but not editable, with different popup configurations.

But apparently the feature layer can't be accessed by one small group with editing privileges while being publically viewable but locked down.

If anyone has found a way around this problem, I would also like to know about it.

EMiller_2

Does anyone have any new insights on this problem?

Any comments from ESRI staff?

Thanks!

TracyGarrison

ArcGIS Online for Organizations for us has been of very limited use. Almost every application I try to make public utilizes public hosted services that I want users within my organization to edit not the public. This seems just plain obvious! Until ArcGIS Online can allow only users within a group to edit a public "hosted service" this is just a BETA application!

MirBBenesov

Do you mean this?
http://ideas.arcgis.com/ideaView?id=087E000000053ew&returnUrl=%2Fapex%2FideaList%3Fc%3D09a300000004xET%26category%3DArcGIS%2BOnline%26p%3D14

LeoDonahue

What about creating different groups, add users to groups and only share the content with users of those groups?

You could have an editor group and create editable maps targeted for users that belong to that group and share the map with that specific group.

You could have a viewer group and create non-editable maps targeted for users that belong to that group and share the map with that specific group.

..etc.

You would have to make several maps with editing enabled on some and disabled on others.

I can't help with with the other issues of savvy users enabling web editing in a map, but I though that would be limited to the person who owns the content?

DevinBartley

I have the same issue. I created a map for the public, but I want a group of staff only to update the map on a regular basis.
The previous option of "unsharing", editing the feature, then sharing again is a bit cumbersome for a non-GIS user. It would be nice to have a simpler workflow in place to facilitate an editing process within an organization.

Patricia

ShawnKraft1

So, let me see if I get this. If I enable sharing for everyone on a web map with a layer that has editing enabled...then anyone in the world can edit it?

DevinBartley

That is my understanding, and not what was I was expecting.

ShawnKraft1

There is a way to do this. Whoever is going to be editing a hosted feature layer, make them the owner of that layer. Disable editing on the web map and hosted feature layer. Then you can share the web map publicly and no one else can edit it. Except an Admin of course. I just did it and it works.

ShawnKraft1

Oh and I forgot to mention that the person doing the editing can be a User and not an Admin. Just make the User the owner of the hosted feature layer.

LarryCampVDOT

... make the User the owner of the hosted feature layer.

How do you do this?

ShawnKraft1

I have a map showing areas for recycle pickups. I did it this way. I invited the person I wanted to do the editing and set them up as a User. Then, I uploaded a zip file and created a hosted feature layer. I edited the details for the hosted feature layer and disabled editing and saved it. Then, created a web map and added the hosted feature layer and shared the map publicly. I then went in again to edit the details for the hosted feature layer and changed the owner to the person I invited(my editor). Done. Now, when the editor wants to edit, they login to AGOL, click My Content, they click the arrow to the right of its name and choose to open it in a map with full editing. When they are finished editing, they click the arrow to the right of the layer and choose to Save Layer. They close out the web map without saving it.

ShawnKraft1

Anyone try my solution? Of course, you can only have one owner but it does work.

DevinBartley

Shawn,

I have tried your solution and it works. But the problem for me is that the since the layer has changed owner, I (The administrator) cannot view that layer anymore. Is there a way for an administrator to view all layers even if she is not the owner of those layers? Seems like there is no way to go back once the owner has changed.

Patricia

MirBBenesov

Much easier it would be if there was a possibility that the layer was searchable, editable and can be attached to the map projects only to the user organization. I think it would solve many problems for us all.

ShawnKraft1

Ladybug, go to My Org and click on the Users name and then choose Manage Items. Then you should be able to see the layer.

MarkNeumann

I am adding to this thread because I also would like to see ESRI address this issue.

I have a crew of public works field workers. (around 30) They share about 6 online accounts. (organization) They all need to have full editing rights to a map that tracks action items.

This map needs to be accessible by the public. (everyone) We want the public to be able to create an action item but not edit any of the existing items on the map.

For example, when John Q Public walks down the street and trips on a hole in the sidewalk we want John to be able to open the map and enter the item. (hole in sidewalk here, FIX IT)
Public Works lead (Org user #1) looks at the map on Monday and sees the item created by John Q and directs staff to repair by scheduling the work.
Public Works crew (Org user #2) views map, sees the priority and then repairs John's item. Noting the date when the repair was complete.

Here's the jig. We do not want John Q to look at the map and see that Robert Q Public has placed another item that rivals his repair. John wants his done first so he deletes Roberts. We don't want that. We want the public to be able to add items but not edit. We need many staff users to be able to edit due to their involvement at different stages of the work.

Please, we need editing rights that can be changed at the sharing level. (Everyone/Organization)

deleted-user-zGZcJ5TpRUeA

You can't solve this problem through groups or user security settings. I have been able to find the REST endpoints on any feature service that belongs to a public map, regardless of whether or not the editing has been disabled in the map. Once in the REST services you can apply edits using the REST API.

***DISABLING EDITING IN PUBLIC MAPS DOES NOT MAKE YOUR FEATURE SERVICE SAFE!!***

MikeMinamiP1

There is an option to disable editing on layers inside a web map. This option is meant primarily for layers, such as shapefiles, that have been uploaded and stored directly in the map (and not as an item in my content). Lindsey, you are correct in saying that if you have a hosted feature layer and editing is enabled on it, disabling it with the option inside the map will only prevent edits from within that particular map. If you add the layer to another map, it would be editable. In order to disable editing on a feature layer, you have to do it from the item itself, by editing the item details of the feature layer. Then it will not be editable via a map or programmatically via REST calls.

The current solution in a pure hosted environment is to create a matching tile layer published with your feature layer. This is not an optimal solution because the tiles will quickly become out of date as edits are made, and you will need to recreate the tiles. We are currently working to better support this scenario in the hosted environment, where organizations want public access to view the layer, but limited editing access.

If you have your own ArcGIS Server, you can publish a map service with features access enabled. The public map would reference the map service, while those that need editing would access the features.

Thanks,

Mike

TracyGarrison

Mike, none of those solutions solve the problem.

I have a Winter road condition map as the snow plow drivers clear portions of the road he radios in his progress the lines are then updated. There are 30 to 50 drivers plowing the highways each calling in their progress the data is changing constantly a tiled map to go along with an editable feature services is not realistic.

The reason a lot of users want to use the hosted feature service is because they don't have access to ArcGIS Server. If they did they probably would not NEED ArcGIS Online for Organizations.

I brought this problem up to ESRI staff at the last three User conferences and to the staff of the Minneapolis office many times. It is the ONE thing holding us back from using ArcGIS online.

I could not believe it when I heard the following at this years User Conference:

ArcGIS Online Achieves Federal Information Security Management Act (FISMA) Authorization and Accreditation

They need to read this thread.

MikeMinamiP1

There is one other option that may or may not be viable for you. A hosted feature layer can have editing disabled, but any administrator in the organization can open the layer with full editing control from the item page of the feature layer (open button). I haven't set this up myself, but you can create a custom role in the organization with limited administrative privileges, which would allow the editors to edit the data, but not, for example, delete other members of the organization. With the fact that the feature layer effectively has editing disabled, any viewing of the layer by non administrators and the public will not allow editing.

We do hear what you're asking for. It is a project under active development.

Thanks for your patience.

Mike

pjdohertygis

Here is a brief explanation. For now Full Editing Control is the best option for Public Maps, in my opinion. More best practices from this link: Best practices for using layers in maps—ArcGIS Online Help | ArcGIS

"Control who can update your data

If you want everyone who has access to the hosted feature layer to be able to update the data, enable editing and choose the type of edits you want others to make. For example, you can restrict editing to adding features only or updating existing features only. You can also allow everyone to add, update, and delete features. Be aware that if your hosted feature layer is shared publicly with editing enabled, the general public will be able to edit the data.

As the owner of the features stored in the map, you can perform edits within the map viewer using the editing tools that come with the map viewer. When working with a hosted feature layer, the owner of the features and any administrator of the organization can also choose to open the layer with full editing control even if editing is disabled. (To open the layer with full editing control even if editing is disabled, open the item details, click Open and choose Add layer to new map with editing enabled from the drop-down list. You can also choose this option from the item title drop-down in My Content). This will ensure that only authorized or trusted members of the organization, such as you the map owner and administrators, can edit your data."

Andrew Stauffer Andrew Stauffer Any update to this issue or more resources related to the topic?

ThomasKonzel

Although Shawn Kraft originally penned the technique back in April 2014, some official Best Practices documentation finally arrived in the link above which highlights his process to limit undesired public editing of feature services.

MichaelKelly

I think this documentation should give you the functionality you want. It details how to limit access to public ArcGIS Online layers!

LakeCountyForestPreserves

I have tried this documentation and it worked for a Collector workflow where the public can see the layer in a map and organizational users can edit the layer. The problem I had with this process is when the public layer is incorporated into Web AppBuilder and I tried printing with the public layer turned on, I would get an printer error message (see this thread).

MichaelKelly

Ah I see you shared this already in the thread above - I didn't notice it.

I was thinking more along the lines of using it in an app like Crowdsource Manager or Geoform where you didn't want users to see records added by other users. The limit usage part of this as you have come across causes problems with printing.

MikeMinamiP1

This scenario is now supported with the latest update to ArcGIS Online. Learn more about hosted feature layer views here...Create hosted feature layer views—ArcGIS Online Help | ArcGIS

Mike

YovavZohar1

At last - A proper solution in the right direction

TracyGarrison1

Mike, am I missing something? There are all sorts of ways to restrict what an anonymous user may or may not do now. But there still is not a way, at least that I can see, that you can let your signed in "allowed to edit users" to add new features without allowing anonymous users to do the same. Why can't there just be a simple choice like Only users of this group are allowed to edit"? See below If I want my editors to be able to add, update or delete, then my only choice is that the anonymous editors can only add new features (see last line of options). I don't want THEM to be able to do any type of updating period.

• What kind of editing is allowed?

Add, update, and delete featuresOnly update feature attributesOnly add new features

• What features can editors see?

Editors can see all featuresEditors can only see their own features (requires tracking)Editors can't see any features, even those they add

• What features can editors edit?

Editors can edit all featuresEditors can only edit their own features (requires tracking)

• What access do anonymous editors (not signed in) have?

The same as signed in editorsOnly add new features, if allowed above (requires tracking)

MikeMinamiP1

Tracy Garrison‌

Hosted feature layer views (view layers) provide the ability you want. Effectively, you are creating a copy of the layer that points to the same data source. This is analogous to how layers work in ArcMap, for example. In this case, the view layer doesn't contain the data, but references it. The link to Help I provided in my previous post explains what view layers are.

We could have implemented editing controls on the layer, the way you're describing above, as another editing property. But view layers allow you to do that and much more. For example, with a view layer, not only can you disable editing of the data, but you can change how the layer is drawn or the popup information displayed. The layer can be fully configured for a different audience.

Hope this makes sense.

Mike

RandyBurton

Are there any tutorials or samples that would show how to set up views? Thanks.

TracyGarrison1

Mike, Thank you. I knew I had to be overlooking something.

Thomas1

@MikeMinami

This is an old thread but unfortunatly it seems the problem hasn't been solved.

As you described Hosted feature layer views is nice and gives more configuration possiblilities. But this shouldn't prevent implementation of editing controls on the layer where we could rectrict who is allowed to edit the layer. This would be much easier and quicker to configures . Hosted feature layer views is way more work to create, configure and manage.

It is amazing that in 2025 it is not possible to simply resctrict the capability to edit a layer to user with editable rights, in a public map.

Doe mee aan het gesprek

Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.

Snelle Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.