Application users are the actual users of the application. In the users module, you can add, enable, disable and configure them. By default your own network user name will be added with all rights.
The active setting allows you to remove access from a network user. Since the application grants permission via the Windows logon user, the user name has to be the same as the Windows user, this also prevents the user from starting the application if disabled while showing a message box that access to the database was denied.
If you add a user, specify the username correct – the username without the NetBIOS domain name as it was added by default to the system with your own user.
All the rights are self-explanatory, they will add and remove the buttons and lists from the main menu that a specific user can see.
Full name is something you want to fill out, this is used in various drop drown fields throughout the application.
Please make sure you fill the field email with the correct email address so you can use it in the reminders are email target address.
Reminder-filter should be by default the username, you can specify only the users username or comma separate e.g. team-mates there. If you use a wildcard (*) this user will see all active reminders on the main menu.
There is one additional user in there – SYSTEM – this user is special. It has the tblUsers.ID = 1 and is partly referenced in some sub-tables for the default entries. I recommend leaving it alone, it does not have any logon-rights or rights at all – but helps to identify some system activity.
Further can you some of the history tables where the user left entries. Those are not all of them, I gave up after a while putting them always there because there was no need for it. You could either remove am all or add more if you want to.
Most important to know is how the LDAP Sync. Member attribute works. Only users who have this flag set will execute the actual LDAP synchronization as well as the Printer page count SNMP queries. Automated emails e.g. from Reminders are independent from this attribute and will float on any instance.
You can define a different language on the user level. If the field is empty, the system language from SysConfig will be applied. Alternative, you can define the language in this field. It has to correspond to the column names in the three tables that are used for localization, see SysConfig for more information. This allows to use the multilingual capabilities of the system on a per user basis.
As of version 3.5 of the database you can use one of the following three keywords:
- Language3 (note, this is empty, not set by default and would fall back to Enlglish)
- create an Active Directory user for this sole purpose
- add him as database user
- set the flag LDAP Sync. Member
- set the flag No Error Messages
- this will avoid any single PopUp error message – until a max. count (SysConfig) has been reached
- have this user always logged on in e.g. a Remote-Session on a dedicated/defined workstation / server
- open the database and let it run..
- additionally – I recommend monitoring as it is mentioned in the floating principle to make sure the system is executing the tasks and you get alerted if it comes to an hold
Data field and reference overview
- Active / Disabled (disabled users and non existent can’t open the system)
- username (needs to be the Windows User Name without the domain)
- Full Name
- Status Notes
- Right Level on Link Lists
- email (for e.g. reminders)
- reminder filter (username, usernames comma separated if a supervisor / team leader, * – wild card if all / any)
- Is LDAP sync member
- No Error Messages
- Rights to modules