Title: Add Domain Account or specified accounts to Atera and to Shell/Scripts

Currently Atera uses system and current user for scripts and shell. Adding Domain credentials to Atera would eliminate storing passwords in clear text under scripts and make management easier for accessing domain resources - network drives etc...

With a system account - there is no access to domain network resources like drives. Yes there are work arounds using net use and possibly adding a domain account under Services.msc - Atera - Logon - domain account. What if the domain account breaks?....I mean yeah, there is a possibility to powershell that but that does not work at scale and we'd have to touch every end point and the same with changing account credentials.

Current user - Hopefully our endpoints are local users or domain users logged on. Maybe they should install some software without admin priv right?

Imagine adding a domain admin or even specified accounts as an option having easier access to domain drives and we don't have to wait for microsoft to fix Winget. Its like killing two ants with one shoe.