It would be helpful in production environments to be able to separate the execution of editing web maps and publishing (making the edits live). Often edits need to be synchronized with other processes, or changes to the web map can take some time to make; which can be difficult to arrange into maintenance windows. The current functionality of a simple "Save" operation that immediately makes changes permanent reduces flexibility with respect to preparation for maintenance windows. One could just make the edits and wait for the window to save, however this leaves the edits vulnerable to loss. Ideally, the edits should be saved as they're made and then the user can opt to publish all the saved changes.
For users not requiring this functionality, existing behavior could be the default, but the desired functionality could be enabled with a toggle when necessary. Even better if an administrator can set which behavior is default for the organization.
