! This page is related to backlog item “UPAM-Feature matrix-2026-13” which will be included in version 2 of the Universal Process Automation Model. Content op this page can therefore change.
Having a business solution, in this case a process automation platform, where the concepts of accounts and users is implemented is very useful.
The account is the employee that runs the app. The user is the employee that is logged into the app. This sounds the same, but does not have to be. This is explained below.
When an employee opens the app, her account is the account and she is also the user. But the app supports logging in as another user, meaning she can become another employee.
This concept allows employee to become other employees. This of course raises a red flag, as it should be, but…
From a testing perspective, allowing one employee to become another employee allows the employee to test multiple roles with just one account. This is really very useful which will save a lot of time.
So how does this apply to Forms and Flows?
The Forms and Flows app does NOT include the feature to login as another user.
There is a copy of the Forms and Flows app with two changes, being:
- The removal of all create, update and delete logic. The copy can thus only be used for reading.
- The option to login as another user.
This copy of the Forms and Flows app must only be shared with application managers. This way, application managers can exactly see what other employees (users) see when using the main app. This will greatly improve the understanding of situations allowing better support.
There is another copy of the Forms and Flows app with one change, being:
- The option to login as another user.
This copy of the Forms and Flows app must only be shared with testers and only in a non-production environment. This way, testers only need their own account to be able to test multiple roles by switching users. This will greatly improve the speed of testing saving valuable time.