Access rights at page level

GAPTEQ applications can be publicly accessible or only accessible with a user login. Access restrictions can be set flexibly per page or globally for all pages of an application via Access Rights.

In this article you will read the following content:

1. Access rights at page level

• To define the access rights at page level, switch to “Access Rights” in the Page definition section of the GAPTEQ Designer and tick the “This page requires an authenticated user” checkbox.

• If the page should only be accessible to certain users or user groups, restrict access by selecting “Allow: Add User/Group” to further restrict access.
• If you want to exclude a user group or individual users completely, select “Deny: Add User/Group” and then select the relevant user or user group from the list.

2. Global settings at repository level

Before you set access restrictions for individual pages, define users and user groups at repository level that are authorized to access the frontend of your application.

We recommend creating at least one user group for frontend users in the user administration and storing it under “Users/groups allowed for usage in Web”.

• The settings can be found in the GAPTEQ Designer in the main menu under “Repository configuration” in the “Access rights” tab.

• Clicking on “Add” opens the following dialog to select the desired users and user groups.

3. User login for all pages with database queries

• If you tick the checkbox “This database requires an authenticated user” in the Database Connection settings under “Runtime Connection”, a user login is required for all pages with database access.

This allows you to specify that a user login is mandatory for database access, even if no access restriction has been specified for individual pages.