In this article we'll cover how to reconfigure Pharos to run as a different user. There are many different scenarios where this could come in handy. The top one being that the current user is deactivated in the system and can no longer execute any Pharos actions that were scheduled on their behalf. No matter the reason, we'll need to take the same actions.

We'll need to remedy the situation by first clearing out all the scheduled jobs started on behalf of the previous user, then we'll update the email service configuration and re-launch background processes by simply navigating to Pharos Admin. 

For detailed directions please follow the steps below.

Step 1

The first step is to deactivate Pharos background processes that have been launched as another user. To begin, let's navigate over to the Setup page in Salesforce. From there, follow the directions below:

Step 2

Repeat Step 1 above until all scheduled jobs from the list below are deleted:

Note: you will likely NOT see all the jobs listed above running in your org. That is expected, you'll only need to remove what you do find.

Step 3

Now we need to reconfigure our email service to run on behalf of a new user. To begin, let's navigate to Salesforce setup, as usual. 

Step 4

Locate the user you'd like to run Pharos as. If you are already logged in with this user then simply 

Navigate to Pharos Admin tab and wait until it loads. This action will reschedule all Pharos background processes to run on behalf the user you're currently logged in as.

Note: If you'd like to run Pharos as an integration user or some other system user you will need to login as them first before navigating to Pharos Admin. For instructions on this please refer to the official Salesforce help article here. 

Our recommendation is to run Pharos as a Sys Admin user with a Salesforce license type, to avoid any disruptions to core functionality. 

And we're done! It is a good idea to monitor logs in the next day or so to make sure they are being created without issues. If you have notifications configured, such as Slack or Teams, please double check that these are running as well.