Signing into a User's Web Account from the Client

Follow
Using the Logon to Web button, staff can sign into a user's web account from the client and view the account from the perspective of the user. This enables staff to assist users with their web accounts by being able to see the web pages as the user sees them. Only staff with the appropriate client access permissions will be able to see the Logon to Web button and log into a user's account. Staff who have not been granted permissions to use this feature will not see the Logon to Web button on the User form.

The Logon to Web button, located on the user form, allows you to log into a user's web account, view the information as the user sees it, and request items for the user from within the web interface.

  1. Search for and open the user record.
  2. Click Logon to Web.
  3. If the user is currently logged into the web account when you attempt to access, a popup message will ask if you want to proceed with the login.
  4. Replying Yes ends the user's web session and logs you into the account. Replying No returns you to the User form.

Tracking Staff Logons

Tracking of staff logging into user accounts via the Logon to Web feature is maintained in the Event Log.

Configuring Logon to Web

Configure the Logon to Web feature by giving staff client access permissions to log into user's web accounts. Sites using RemoteAuth will also need to use the StaffProxyWebURL key in the customization manager.

Client Access Permissions

In order for this feature to work, staff must be given client access permissions to log into user's web accounts. Access permissions are configured in the Module Permissions section of the Staff Manager. Permissions are not given to staff by default, so the Can Logon to Web as User checkbox must be checked for each staff user that will use the feature. If permissions are not granted, the staff user will not see the Logon to Web button on the User forms.

The StaffProxyWebURL Key

The purpose of the StaffProxyWebURL key is to allow those sites using RemoteAuth to enter a value pointing to an unprotected directory and bypass their ISAPI filter. By default this key (found under System | General in the ILLiad Customization Manager) is left empty, and staff log into the web session via the system URL. This key is not used unless a value is assigned.

 

Questions?

If this article didn’t resolve your issue, please take a moment and answer a few questions to help improve our documentation:

Feedback