We should be able to set permissions on a feature class (table) to allow different permissions based on user/role. Such as allow Add/Edit, deny Delete, or allow Edit, deny Add/Delete. Currently can only allow [Nothing|Select|Everything]
When data is not versioned, and not archived it is possible to support individual insert or update or delete permissions for edits made directly from ArcGIS Pro. However, when the data is archived or registered for versioned editing the model does not support individual permissions. While it may appear that edit operations are inserts, updates, or deletes the model used by ArcGIS may not translate to the same DBMS-level operations. For example updates and deletes to versioned data are actually inserts at the database level. For a user to successfully edit using traditional or branch versioning, or non-versioned archiving, all permissions must be present. For edits made via feature services, it is the service publisher that is actually executing the edit in the database, rather than the portal user who is performing the edits.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
