Root > Tools > Viewer > Interface > Configure user accounts window

Configure user accounts window

Previous pageReturn to chapter overviewNext page   

EurekaLog Viewer's Configure users window:




This window is invoked from main window by selecting "Configure"/"User accounts" command from toolbar:




Note: the toolbar is configurable, if you can't see this button - then you need to reconfigure toolbar and add this button).


This command is only available for certain types of databases, which supports different user's accounts. There is only FireBird database with these capabilities in initial release of EurekaLog Viewer from EurekaLog 7. This command is disabled for view mode. In-memory and file-based databases do not support user's accounts.


This command also can be disabled, if you have insufficient rights on target database (you can change current database in settings). See also: defaults.


You can use "+" or "-" buttons to add or delete user's account.


If you create a new account - then you must specify a password. If you leave "User Password" column's value empty - the account will have no password.


If you edit an existing account - then you must leave "User Password" column's value empty if you do not want to change password. Or you can enter new password. Note, that you can't reset password to empty one.


"Role Name" columns represents right, which you want to give to user. There are the following values available:



See Database roles to more information.


See also:

Send feedback... Build date: 2023-05-05
Last edited: 2023-03-07
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: