Hi @moriah-morgan_0490 ,
Glad to see the environment un-scoping worked! It's definitely possible to get environment-scoping of credentials to work... but it'd probably be best to confirm what you're looking to accomplish.
The main purpose of the environment-scoping is to enable limited management access to Otter. For example, users can edit/maintain all configuration except for production servers. Take a look at Multiple Environments per Server to see how the behavior works.
I assume that you're running the Inedo Agent? We're still learning the exact privileges ourselves
We've seen systems restricted in very unexpected ways (and only in the field of course, never or own environments), and they don't give any logical error messages. But we'd love to help you get this working, so we can document it.
Here's what we know so far:
local administrators seem to have no problems; this is what most people do, because it's domain credentials they are interested in using and it doesn't matter if they're an admin on that particular server
try running the Inedo Agent as the user you wish to impersonate as; this will identify most permissions issues
make sure the user target has permissions to the extension cache path and appropriate root paths; see the Agent Configuration File
"run as a service" permission seems to be important
logging into the server as the impersonated user (at least once) may help for some scripts, so we've heard
antivirus or other security tools may block this impersonation as well
Let us know what you find :)