Select to view content in your preferred language

Users Without Update Privileges Have Selections Shown as Editable with Edit Widget

223
2
Jump to solution
08-27-2024 12:17 PM
Labels (1)
AlexCarter1
Occasional Contributor

When setting up a service to be used in Experience Builder, we removed the privileges to update geometry for editors, as we do not want them to modify geometry—only to create features and edit attributes. We also removed the update privilege in the Edit widget.

However, when clicking on an existing feature in Experience Builder, it still shows the option to modify the geometry. Although attempting to edit it does not actually allow changes, this inconsistency is confusing. Why does Experience Builder display the option to modify geometry when the user does not have the privilege, and the Edit widget update setting is turned off? Is there no differentiation between owners and editors built into the system?

Thanks,

Alex Carter

0 Kudos
1 Solution

Accepted Solutions
abureaux
MVP Frequent Contributor

Did you remove permissions at the widget level? If so, a user's permission currently override the widget's setting. This is apparently logged as a bug. See similar post here.

View solution in original post

0 Kudos
2 Replies
abureaux
MVP Frequent Contributor

Did you remove permissions at the widget level? If so, a user's permission currently override the widget's setting. This is apparently logged as a bug. See similar post here.

0 Kudos
AlexCarter1
Occasional Contributor

This makes sense. The way permissions are structured is somewhat complex, but I believe I have it figured out now.

Data Editors won’t have geometry editing capabilities because their service level permissions have been removed.

My main account will display the geometry editing option due to its higher privileges compared to a Data Editor, but editing will still be restricted by the service level permissions.

Owners will have both the option to edit geometry and the necessary permissions to do so, as their privileges override the widget’s settings.

Thanks for the information—it helped clarify the issues I was experiencing.

0 Kudos