Asset actions are always run in the security context of the user initiating the action. If an action requires administrative privileges on the target machine, the user clicking the action must have those privileges. You cannot run actions under scanning credentials instead, if this is what you're asking. This feature is on our customer wish list, but we do not have a release date for it.
To run an action under a different user, you'll either need to:
- Run your browser under that user, by Shift + right-clicking on your browser shortcut.
- Add runas to your action command under Configuration\Asset Pages. More information on this can be found here.
For some operations, like shutting down a computer for instance, you could use a deployment package instead of an asset action. Deployments are run on the target machine itself, under the machine's scanning credential, its system account or its currently logged on user, depending on which run mode you choose. More info on deployments can be found
here.