How To: Login as Another User
For testing purposes, C4C allows to create a test user which impersonates a business user.
This feature allows you for example, to respond to issues related to a specific business user without having to use the logon data of the business user. User impersonation avoids the need for screen sharing or password transfer.
The test user has the same page layouts, data access, or query results as the business user. Please note that the test user user cannot however impersonate the business user’s Home view, calendar, or Feed.
If data is modified by the test user, the change is tracked with the test user identity details so that the business user data is unaffected.
To impersonate another user, modify the table by entering the dedicated test user and the corresponding business user:
- Go the Administrator workcenter.
- In General Settings, click “Login as another User”.
- Click “Add Row” and then click the value selection for the Test user. The default query fetches all users with User ID “KEYTEST*”. You can create such a user in the Business Users, or use any existing user; in the latter case, remove the default value of the query (expand Advanced Filter) and then select the user.
- Enter the ID of the user you wish to simulate.
- If you wish to display the business user’s name with the test user ID, tick the box “Copy business user name to keytest user name”.
- In the Business User view, find the test user and enter a password for them. The logon password of the test user is not affected by any table modification.
is the created Business user KEYTEST* relevant for license costs?
thanks in advance
That's the catch. I guess it will as this is just another business user. I am curious to know too. 🙂
Hi Carolin, sorry for the delay.
As for my understanding, a Keytest user is being handled like a normal Business user and hence will be counted as such.
So, basically, for testing purposes anyone who is designated can literally copy personal data to a testing user data space and work as if that was the real user. An operator who logins as another user can send and receive sensitive data on behalf of the user.
Furthermore, for "testing" purposes, complete impersonation is possible where any operator with the credentials in his hers hands can print screen this "testing" data and send it anywhere.
Thanks for the explanation but one small question at my side:
Does it take into account the employee master data of the user we use for the KEYTEST*?
For example, will it take into account the main indicator registered in the sales data of the employee, in its configuration? (Employee workcenter > Employee X > Edit > Sales Data)
Thanks in advance for any reply,