The users can be grouped and can inherit rights in this way. Thereby you can integrate a highly sophisticated and close grained user management that closes all potential loopholes via shortcuts with minimal effort. Only if the user has been granted the specific right by the administrator he can see or use the specific function assigned by the administrator.

The administrator can configure the rights at run-time thereby preventing a restart of the program when changing assignments. For doing so he can use an easy to handle, intuitive GUI that enables the administrator to create new users or to group or delete them directly from the application.
 
Trial (work while IDE is running)
Source: On purchase/registration
Price: $100

Features:

• Very user friendly user interface
• All Dataset descendants will be supported
• Simple drag and drop management both Design-time and Run-time
• User and group management
• User Rights to control any controls/components available on any forms
• Exclusive Watch… a thread safe control state monitoring feature to prevent external hook
• Support both design-time and run-time decrypting the rights and manage accounts
• Run As feature
• Store the security description as you like (database, binary file)
• Synch-Data-Synch support: synchronizing existing users data as well as TLogin known data format.

This complete solution features a COM object and interface wrapper to give the control back to you without having to struggle.

Full Source Code and compiled COM Object included.
 
Fully functional
Source: Included
Exe-Demo Included

The TUsers Security Component is very easy to use. With the TUsers in action, you don't even need to write code to have strong protection covering all the application. Just drop the components in your forms, create the security database (with a utility included in the component package), configure a few properties and your application is then protected.

The component has also several properties, methods and events that allow developers to implement all specific security needs of their applications easily and very fast.

The TUsers allows to control the access to all the VCL, including buttons, menu items, Actions, DBGrids, Queries, Tables and Dataset Fields. The TUsers also works with virtually all the 3rd-party components available on the market.

Available Drivers: BDE, ADO, IBX, IBO, DBISAM, ADS, DOA, dbExpress, Apollo, ASTA, SQL-Direct, FIBPlus, mySQLDAC, PostgresDAC, ODAC.
 
Trial (work while IDE is running)
Source: On purchase/registration
Price: $199.95

Enclosed XPMenu support, supports data access through/to ADO, DBX, IBX, BDE, IBO, FIBPlus, MDO, Zeos, DBISAM, ASTA3, MyDAC and MySQLDAC.

Access control auto-extract TMenu and TActionList itens. Control rights also to other components as TButtons, TDBEdits, TLabels, TFields, etc.

Log/event control with levels support.

Included Indy based component to send some mails to users. (EQ. "forgot password" in login window). Support for user profiles and login images customization.
 
Fully functional
Source: Included

• permission control per user or per user group
• user / usergroup editing at runtime & design time
• component level permission setting per form at runtime & design time
• supports any standard Borland dataset
• form level permissions can be stored in form or in table
• permissions can control a component's visibility, enabled state or perform a custom action
• usage tracking.

This article describes all of the common ways to verify a user's credentials and the special requirements for each method.

Note: Collecting user credentials from a User-mode application can be annoying to the users and can provide a possible security hole in the enterprise computing environment. The Unified Logon requirement (a requirement that the user should only be required to type their credentials one time at the Ctrl+Alt+Del screen), was added to the Microsoft BackOffice logo requirements for these very reasons. It is important to make sure that you really need to gather credentials and that some other method of client/server validation is not more appropriate. Consult the security documentation in the Platform SDK for more information on impersonation and programming secured servers.
 
Fully functional
Source: Included

To work this component requires the user that calls it to have granted one of the following permissions: Backup Files and Directories or Restore Files and Directories .

This component is usefull also when writing NT sevices because SYSTEM account have such priviledges.
 
Fully functional
Source: Included

dWinlock offers the following functions:

• Disable following keystrokes:
  • Ctrl Alt Del
  • Ctrl Esc
  • Alt Tab
  • Alt Esc
  • Alt F4
  • Win Key
  • Application Key
  • Right Mouse Button
• Hide or replace following desktop elements:
  • Windows Taskbar
  • Windows Desktop
  • Windows Start Button
  • Tray Icons in the Windows Taskbar
  • Application Links in the Windows Taskbar
  • Replacement of Windows Start menu with own menu

Allows to control the user access to your app. GUI components (menus, buttons, check boxes, radio, .., everything connected to an Action) and to any non visual functionality. Just drag, drop and connect.

With Security Builder you can:

• Build the security model of your app. at design time with few mouse clicks
• Add and remove users on fly
• Change users profile on fly
• Add/remove securized items on fly
• Securize non GUI functionalities
• Predefined User Groups - Supervisors, Power Users, ...
• Much more...

• Add TabActionList to any form you wish to be secured
• Use TabActionList designer to select the components to secure - it automatically creates abActions
• Add TabSecurity to the project (only once, typically on the main app form) then connect any List to TabSecurity (make sure you added the TabSecurity's unit in the uses clause of any securized form)
• Double click TabSecurity component, and then choose "Rebuild from client lists" (make sure all forms containing TabActionLists are open
• Before distributing remove soCreateSupervisorIfMissing TbSecurity.Options and include the UserTemplate file in your distribution pack.

Key Features:

• Simple to Use - Use TSecureActionList as you would TActionList. Set a minimum security level for each Secure Action. Set the user level and your application is secured, all the way down to the control level.
• Flexible User Level Handling - Simple event OnNeedUserLevel allows you to control getting user level. Be it a file read, a DB lookup or call a security service.
• No Data Base - Many user security apps require BDE and database connections. We impose no such requirement.
• Secure at the window control level - With Secure Actions your application is secured at a very precise level, each user function and the corresponding controls are secured.
• No user login required - Secure Actions get the windows login ID by default. You users never have to login to your app (unless you want).
• Warnings- Can warn of unsecured actions and program trying to enable security disabled actions.
• Help and Demo App - download includes a component help an a commented demo application to get you going quickly.