It is typical of SaaS products that the functionality is associated with and owned by the licensed end user. Thus, the operations provided by the SaaS products are used by the end users and the result produced is associated with the logged-in user.
This creates the problem that the work products or solutions created are not visible at the enterprise level. So, what happens when a user leaves the organization? Do we lose the functionality and the work products created by that end user. How do you monitor, manage, and know the outcomes of the work done by that end user? These are common problems and affect many of the SaaS products which are licensed to the end user.
This affects integration workflow products like Hire2Retire which provides pre-packaged business process automation for the employee lifecycle and resource provisioning where the HR to AD integration workflows run in the end user accounts. We heard this challenge from our customers and created the solution by providing the admin user the ability to impersonate any of the users in the organization. By doing so admin can see and update workflows created by the end-users and to be able to view the processed employee event or “Observe” the workflows of that user.
What happens when a user leaves the organization? The admin can share the designed and running workflows to another account and run it from a new account. We recommend, however, to always run production workload from a dedicated account to segregate end user activity of design and UAT from the production workloads which are critical business processes of the organization.