Created feature layers in bulk using user-managed datastores and edits on by default?!?

[SeanLawrence]

I created feature layers in bulk using user-managed datastores that have 'write' credentials to the database schema and by default the feature services have editing off....but....if I'm signed in to the Portal in ArcGIS Pro as 'creator' I'm able to edit and save with that feature service.  I feel like the feature service should have control of the editing capabilities.  It clearly doesn't in this case.  Am I missing something?

This is on newly installed 11.4 Portal/Server. 

ESRI documentation says:

Ensure that the privileges granted to the user specified in the database connection are appropriate for each dataset.

When you create feature layers in bulk, editing is not enabled on the layers. However, you can enable editing on the feature service in ArcGIS Server Manager or from the portal. If no one should edit data through these bulk-published feature layers, connect to the database as a user who has only privileges to select data from the feature classes and tables, and do not enable editing on the feature service.

I feel like you used to be able to publish with a database connection file that had write privileges but control editing on the service level.  If I was to follow this...I'd have to separately publish new feature services for editing and read-only?!?

[dgiersz_cuyahoga · Accepted solution]

If you publish something that can be edited, even though 'enable editing' is unchecked in the Portal Item's Settings, the owner and administrators can still edit the data.  Is the Creator you are using to access the services the Item owner?

[SeanLawrence]

On a call this morning with ESRI support...Funny enough when trying to reproduce the issue, the edit capability stopped working in Pro this morning on the call (logged in as same user).  I couldn't make edits unless the capability was activated on the service.  BUT, I was able to make edits in the map viewer in Portal but not in the classic map viewer.  They are investigating, but mentioned it's not typical behavior.

To answer your question: the user with creator was the item owner.

[SeanLawrence]

Oh scratch that, it seems the user in Pro was not the data owner but the user in Portal map viewer was.  So this would indicate that the data owner user can edit even with feature service editing capabilities turned off.