|
This feature allows to assign table level permissions on
database tables and views. I.e. user A can add data into table1 and
edit data in table2, user B can edit and search data in table1 and
can delete data in table2 etc.
To use this feature proceed to the Security page in ASPRunnerPro, click
the Permissions button.
There are ways to define user group permissions:
|
·
|
in the ASPRunnerPro directly before building project
(Static permissions
option). In this case if you want to change some security settings
you'll need to open ASPRunnerPro project, make some changes on the
User Group Permissions
dialog and rebuild project. |
|
·
|
on the generated pages (Dynamic permissions option).
ASPRunnerPro create new tables for user group permissions settings
in the database and build admin area in the application.
Administrators can update permissions online. |
Static
permissions
On this screen, you can create user groups with assigned set of
permissions.
First of all choose GroupID field that stores group name or
id (see screenshot).
To add a new group, click the Add group button. A dialog box will
appear where you can choose username which defines this group and
define initial set of permissions. Afterwards, you can change
permissions for certain tables.
You can create a user group based on non-existing GroupID field value (if you plan to add
users to this group later).
Apart from this, you can create a default group with a default
set of permissions. When a user not belonging to any of specified
groups is logged in, the default set of permissions mentioned above
is assigned to him. For example, as shown on the screenshot above,
the user not belonging to any of the groups, is able to edit and
delete data, but is not able to add or search records in any
table.
To delete selected group, click Del group.
To overwrite existing group, click Add group and choose the same group id
value.
You can set any group to be an admin group. This option is
available to you when one of Advanced Security options are in
use.
|
