The security context for a background workflow can differ depending on how the workflow is initiated.
When a background workflow is initiated manually by a user using the Run flow command, the workflow operates in the context of the initiating user and their security privileges. Therefore, a background workflow that is run manually can only perform steps that the user could do themselves.
When a background workflow starts based on an event, the workflow operates in the context of the user who owns the workflow. Usually, this is an administrator. Therefore, a background workflow that is triggered can run with elevated privileges and can perform steps that the user is not able to. It does have the downside that any record created or updated will have the administrator's name stamped on the record and not the name of the user.
There are several reasons for considering switching to a real-time workflow. Let's see how a real-time workflow...
