IMS cares about authentication and authorization; and for that you don't need to have multiple identities on AEM Stage and PROD environments. That's the reason your identity is tied to your email address and that you can connect only a single external directory (e.g Azure Directory) per domain to IM...

Make sure that the user does not have the "replication" privilege on that page. Then the default "request for approval" workflow is invoked, which you can customize.

So you want to map your Stage environment to use directory 1, while PROD is using directory 2? Can you explain why this you require this?  

since AEM release 12255 a feature is included, which allows users which are member of the "administrators" group to unlock all pages (also the ones not locked by themselves). This was hidden behind a Feature Flag, but that should be enabled to all environments by now.

I normally object to this approach, because the session object is not thread-safe. And even if this normally not a problem with just reading (as you barely corrupt on-disk data) there is no guarantee that you won't get inconsistencies in in-memory data-structures.I know that it works in at least som...

It's not possible to uninstall this package; it has been deployed, and parts of it have been incorporated in the immutable area and therefor it cannot be uninstalled. To get rid of the immutable parts it's enough to just deploy without this package being included.But that does not mean that the muta...

the order of actions on author is like this:* replicate the content* Update the last_replicated* properties That means, that this value will always be off.

no dedicated license required.

I am aware of some thoughts to support log-forwarding to other systems than Splunk. You might want to contact customer support which can probably get you in contact with the right Adobe folks.

In AEM CS I would store this information in the user profile and request that the usersync feature is enabled. Nevertheless this information will not reach the authoring instance when using usersync, which is correct. If you want users to store data in publish and being able to review/modify it on p...