The list of administrator users can be managed via the Extras menu / Administration logins. Central, overriding permissions are provided here. These permissions apply to every portal. A permission holder can
Change licensing details
Manage administration logins
Use the tool SystemCare
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 prevent access without a password.
In Intrexx, permissions can be provided in the permissions dialog which generally always has the same structure.
Displays an image that represents the type of permission holder.
Displays the name of the permission holder.
Displays the path to the user object in the User Manager.
Opens a dialog where a user object can be selected.
Removes the user object from the list. This does not mean that all of their permissions are automatically removed. The permission holder could still possess permissions by being a member of other objects, e.g. by being a member of the Users group.
When you select a permission holder at the top of the dialog, the individual permissions are displayed at the bottom.
Activate the respective checkbox to provide the user object with the desired permissions.
Portal access permissions
Portal permissions will be controlled from the Extras menu / Portal access permissions. This menu item is only available after logging in to a portal. All permissions defined here are valid for the current portal.
In the Users module, permissions are managed on two different levels:
These are managed via the User menu / Permissions. Permission holders can edit object classes and object instances, have access to the Schema manager, can add, edit and delete classes or attributes or edit the organigram.
These are managed via the User menu / Permissions. This menu is available if a user object has been selected. With the individual permission to edit the properties of individual object instances, you permit the changing of values that are also stored physically in the database for each instance, such as the name of the instance or address or contact data for an instance of the user object.
Application permissions are defined in the Applications module. Furthermore, the administration permission, which allows the user to edit the application technically, can be provided. The application permissions can be edited via the Application menu / Permissions or the Edit menu / Properties, when the application node is selected. Click here for more information.
Permissions can be assigned for each menu item. Menu items that a user may not select will be hidden in the browser. These permissions can be edited via the Portal menu / Edit menu structure. Click here for more information.
The permission "Administer menu item (CMS)" allows the CMS application to publish articles under this menu item. Articles are published directly in the CMS application. For menu items that originate from the CMS, the permissions cannot be managed via the menu designer. Deleting a CMS menu item is also only possible via the CMS application Menuu items that refer to CMS content can only be managed in the CMS application.
The access to files on the network are managed at two points. The permissions for the FileWalker connection are provided in the properties of the connection in the Integration module. The permissions for the FileWalker application element are provided on the Permissions tab in the properties dialog.
The users of Office integration must at least have the data group permissions "Read", "Add", and "Change" for the data group that contains the edit page. These permissions are required to edit documents. Permissions for the edit page are also required.
To be able to configure web services, the user requires the portal permission Register web services and permission for the Tools module.
Implement a login module
Click here for more information.