Administration login
Portal access permissions
User Manager
Application permissions
Menu structure
FileWalker Office Integration

Administration login

With an administration login, central, super-ordinate access permissions will be granted. These permissions apply to all portals. A user with this permission may:
In the default install of Intrexx, in order to facilitate a quick setup of basic settings, the administrator user will be created without a password. As long as no password has been entered here, no login information will be requested when creating and deleting portals, when accessing the License Manager, and when managing administrator logins. Enter a password for the administrator user in order to eliminate access without a password.

Administration logins will be set up in the menu Extras / Manage administration logins.

Portal access permissions

Portal permissions will be controlled from the Extras / Portal Access Permissions menu. This menu item is only available after logging in to a portal. All permissions set here are valid for the current portal.

User Manager

In the User Manager module, permissions are managed on two different levels: the global permissions to administrate the object classes and object instances and the individual right to administrate the properties of the several object instances. With global permissions you can e.g. grant permissions to access the scheme manager, to add, edit and delete classes or attributes or to change the tree structure of the organization. With the individual permission to edit the properties of single object instances you'll permit to edit values, that are also stored physically on the database, e.g. the name of the instance, or address and contact data of a user object instance.

Global permissions

You will find the global settings for permissions to classes and objects in the menu item User / Permissions.

Individual permissions

The context menu Permissions, which can be accessed for every object in the User Manager, opens a dialog to manage the individual permissions for individual objects.

Application permissions

Access permissions for applications are defined in the Applications module. In addition, the administration permission which allows the application to be edited technically can be assigned here. Via the main menu Application / Access Permissions or the Application node , these permissions can be defined on the Access permissions tab in the properties dialog.

For each individual menu item, permissions can be assigned. Menu items that a user cannot select will be hidden in the browser. Select the menu item, for which you wish to control access permissions, and then click in the lower right on Permission.

The permission to Administer menu item (CMS) makes it possible for the CMS application to publish articles under this menu item. The publication of the articles will then be directly applied to the CMS application.

For menu items that originate from the CMS, the permissions cannot be administered via the Menu Designer. Deleting a CMS 2 menu item is also only possible using CMS 2. The administration of menu items that refer to CMS contents can be accomplished exclusively via the CMS 2 application.


For access to files in the network, permissions will be controlled in two places: in the properties of the Connection and in the properties of the FileWalker view element.

For the FileWalker application element, the permissions are assigned on the tab Access permissions in the properties dialog.

Office Integration

Provide the Office Integration users with at least the data group permission Read, Insert and Modify for the data group where the edit page is located. These permissions are required to edit documents. The permissions for the edit page, which you can defined on the Pages tab, are also required.