Hi,
Yes, the container workflow starts the child workflow as admin because it is started in the back-end, and not directly by the user.
When you start a child process the metadata from the parent process is copied to the child process when it is started, I would add the user information you require (initiator?) to the parent's metadata before starting the child workflow, and use that value in the child workflow.
Will