• Company
• |
• News
• |
• Contact us
• |
• Site Map
• |

• Visual Guard for .NET
• Visual Guard for PowerBuilder
• _________________________
• Visual Expert for PowerBuilder
• Visual Expert for Oracle
• Visual Expert for Sybase ASE
• Visual Expert for MS SQL Server
• _________________________
• Enable for PowerBuilder
• REX for PowerBuilder

• Try Visual Guard for .NET
• Try Visual Guard for PowerBuilder

• How to...
• Visual Guard Forum
• Visual Guard .NET Update List
• Visual Guard Technical documentation

Visual Guard for PB  Key Features  How Does it Work

Visual Guard for PB   Key Benefits Key Features Authentication Permissions How Does it Work Permissions Examples See a Demo Try Visual Guard for PB Price Request		How does it work?   What is in Visual Guard: The Repository: A secure place to stores users, profiles and permissions. The Visual Guard Engine: a component included in your application that modifies it dynamically according to the user's permissions. Developer Workshop: An application for developers to create permissions without coding Profile Manager: An application for administrators for daily User and Identity management. When using Visual Guard, profile and user management requires no special development skills. A non technical person (super-user, administrator, head of department...) can easily manage them. They can declare profiles, grant them permissions and associate them to users. It releases the IT department from the daily profile and user management. (screenshot) A sample application integrating Visual Guard What happens at runtime? The user logs onto the application Visual Guard connects to the security repository and retrieves the user's permissions. The Visual Guard engine then modifies the application according to these permissions. Example: When a window opens, Visual Guard may hide buttons and filter data. More info => Getting started Implementation process: Add Visual Guard engine to your project and activate the security (just a few lines of code required). Implement the Visual Guard login window (or use your own login window). Create a security repository and declare your application in this repository. Using Developer Workshop, developers define all the permissions available for this application. As a result, a permissions catalog is created. It will be used later (see step 6). The application is tested, compiled and deployed. Administrators use Profile Manager to create profiles and grant them permissions from among those defined in the permission catalog. Then those profiles are associated with users. No technical skill is required: Administrators can be super-users, heads of departments, etc... Note: If you already have a permission system, you should disable it before using Visual Guard. More info => Getting started Previous: How does it work? Take the tour... Try Visual Guard now!   Resources: See a demo for PowerBuilder Getting started Visual Guard Architecture How does it work? Receive an evaluation version Visual Guard for .NET       Index   What is Visual Guard? Authentication Permissions How does it work? Examples of Modifications Technical specifications       Active Directory   Re-use AD accounts for authentication   more information   Trial Version   Try Visual Guard! : - For PowerBuilder - For .NET