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.
2. Permissions dialog
In Intrexx, permissions can be provided in the permissions dialog
which generally always has the same structure.
First column
Displays an image that represents the type of permission holder.
Name column
Displays the name of the permission holder.
Path column
Displays the path to the user object in the User Manager.
Add button
Opens a dialog
where a user object can be selected.
Remove button
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.
Permissions column
When you select a permission holder at the top of the dialog, the
individual permissions are displayed at the bottom.
Permit
Activate the respective checkbox to provide the user object with the
desired permissions.
In the Users module,
permissions are managed on two different levels:
Global permissions
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.
Individual permissions
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.
5. Application permissions
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.
Clickhere
for more information.
6. Menu structure
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. Menu items that refer to CMS content
can only be managed in the CMS application.