Specific/dedicated user for system automations

Hi ​@wandile02 

From what I can find the system does not provide a setting to change the user to another account. Automated processes are always run under the admin user account.

You can post on this Ideas | Community as well if it’s a required feature.

@wandile02 Dasun's right, and you've got the docs behind it. The help says "The system uses the admin user account to run scheduled processes." In the 2026 R1 code the user name is hard-coded as admin (admin@tenant on a multi-tenant site). That includes scheduled import scenarios. Business events triggered by a record change or a schedule run their subscribers as admin too, even when another user made the change.

Your dedicated user still has a place, for anything that signs in. A REST integration runs as the login you give it, so that name shows in Created By. If any of the POs in your screenshot came from an integration using the admin login, or from someone signing in as admin, those are the ones you can move.

For the automations themselves, keep people off the admin account so admin in Created By means the system did it. Julia Lukina recommended exactly that here: https://community.acumatica.com/reports-and-generic-inquires-115/bc-should-show-they-are-the-user-who-did-the-work-18310

Don't restrict the admin account along the way. Acumatica Support traced a schedule returning no rows to admin not having access to the tenant's branches: https://community.acumatica.com/other-developer-topics-290/automated-schedule-adding-branchid-null-to-where-clause-25483

Hi All,

Thanks for the clarification ​@Steve Milner & ​@DasunPerera91