VG Console is the entry point to manage
access control in the application. This is where you create
repositories, where you declare application, where you define
roles, organize permission set and create permissions.
Additionally, VG console offers some useful tools to make
developers’ life easier:
Permission Editor: Create and modify permissions in just
a few clicks
Deployment wizard: Deploy new versions of a repository
along with a new version of the application
Versioning wizard: Manage several versions of a repository
when deploying the application
Most permissions consist in changing the value of a property
depending on the role of the user connected. The Permission
Editor allows creating such property permissions in just
a few clicks, without adding code in your application.
These permissions are dynamic; No need to rebuild your
The Permission Editor offers detailed options to implement
permissions that fit your ever-changing business environment
as perfectly as possible with increased responsiveness.
Each new version of an application may come with new permissions
and a new repository. You need to deploy this repository
without disturbing the data already entered by administrators
in the previous repository.
Visual Guard .Net provides a Wizard to deploy new permissions
in a production repository. Visual Guard will merge the
new and previous permission sets automatically, without
losing existing user accounts, roles or permissions.
Security Rules Versioning
When a new version of an application is deployed, some
users will be using the new version while others are still
using the old one. Both the existing and new permission
repositories need to be available during the migration
Visual Guard .Net can manage several versions of the permission
repository simultaneously. It allows progressive deployment
of the new application and its repository. This means
users can access the existing permission repository or
the new one, depending on which version of application
they use. You can switch smoothly from one version to
another without blocking end users or rushing the deployment
When a permission is related to a component, any change
in this component may affect the permission and generate
regression bugs. Therefore, each new version of an application
requires full verification of all permissions.
Visual Guard .NET can verify automatically that permissions
and application code match perfectly.
When maintaining the permissions, you may need to find
permissions related to a specific user or business keyword.
For example, if you modify a control in your project,
you need to list all permissions related to this control
in order to adapt them.
Visual Guard .Net provides a global search feature to
browse the repository and find all items related to a
given keyword. You save time while maintaining the permissions
by immediately getting a comprehensive and reliable result.
Creating new user accounts, giving
a new employee the appropriate rights in the application,
unlocking an account… VG Console offers ready-to-use
and user-friendly features.
2 roles allow using Identity Management features: User Administrator,
and Restricted User Administrator.
It lets them see and manage only user accounts and roles,
either for the whole repository or for a particular application.
Visual Guard API
Identity management features are available through Visual Guard
You can develop your own administration form and call the Visual
Guard API. This form will be integrated in your application,
with your own look and feel, so that user with an administrator
role can use it easily. Visual Guard API supports both Winforms
and ASP.NET administration forms.
VG WEB Console:
The VG WEB Console is dedicated to User Administrators.
They do not need a direct access to the database or a connection
to the organization network to perform identity management tasks.
All they need is access to the Internet.
Shifting identity management to non-technical administrators
Visual Guard Identity management tools (Console or API) have
been designed for non-technical people. This means whoever is
in the best position to manage end-users can do it, depending
on the security policy of your organization: Administrators,
security people, system administrators, managers in charge of
a department or a remote site, etc.
The Administrator roles leave you free to adapt to the existing
structure of your company.
For example, you can have a central, super-administrator who
can create permissions and roles, and local (for instance, remote
sites) administrators who can only create user accounts and
grant them existing roles, but have no permission to change
As a result, you get more flexibility: Administrators are totally
independent. They can change permissions, roles and user accounts
at any time, and these changes are immediately effective. At
the same time, you free up the development team from daily user
You may need to define roles that should be available across
your entire organization, no matter how many applications you
have (exisiting or future).
Visual Guard .Net provides Shared Roles that group permissions
for several applications. This means that you no longer need
to manage a separate role for each application any more.