QuerySurge offers three different User Roles:
- Admin(Administrative) User
- Standard User
- Participant User
The Admin User Role has access to all areas of QuerySurge with full access to create and update QueryPairs, to schedule and execute, to report and to administer QuerySurge. The Standard User Role, has full access to create and update QueryPairs, to execute and to report in QuerySurge; the Standard User does not have access to the administrative features. The Participant User Role can view all QuerySurge assets, but is not allowed to make any changes; nor is the Participant User allowed to execute in QuerySurge. User access is summarized in the table below.
|Feature||Admin User Role||Standard User Role||Participant User Role|
|View Test Result Data|
|Access Administrative Features|
Creating a User
To create a User, in the Administrative view, click on the Users node in the left nav tree. Use the Add button at the lower left of the central pane to launch the Add User dialog. The starred fields are required to create a user. (Note that Users are required to have passwords.)
The User Role drop-down list contains the different User Roles: Admin User, Standard User and Participant User.
Editing a User
After User creation, User data may be edited by either double-clicking on the User or by single-clicking and using the Edit button toward the bottom left of the main pane. Note that when editing, the User password fields are not populated; the password is changed only if a new password is entered. If the User data is edited and the password fields are left blank, the current password is unchanged.
When you deploy QuerySurge, by default QuerySurge authentication is handled locally. Many organizations use LDAP for authentication, however, so you can switch QuerySurge over to authenticate from your LDAP server. The procedure for this setup is described in the QuerySurge Authentication with LDAP article.
Changing a Password
Passwords may be managed either by a QuerySurge Admin user using the User Edit tool shown above, or by the user, from the QuerySurge Help menu (upper right):
Note: This feature was added in QuerySurge version 4.6.