-
-
- Search Engine Optimization
- User Interface migration guide
- User account management
- Instructies voor implementatie van visueel editen van nieuwsbrieven
- Login as another user
- Support
- More information about moving to User Interface Version 4.0
- Standaard page layout
- Sections moved to layout
- Aanpassingen in release 2024-7
- Media library
- Aanpassingen in release 2024-10
- Analytics and Matomo
- Registration forms
- How to change names of classes and fields?
- Responsible Disclosure Policy
- How to upload a blob in Velocity?
- Aanpassingen in release 2024-2
- Google Analytics
- Street and City helper (postcodecheck)
- Responsible disclosure-beleid
- Postcode check service (straat en huisnummer) kosten
Login as another user
In certain situations a user can login as another user, without having to know a password or other login credentials. All that is needed is the email address (or alternative login name).
Who can use this?
This option can be used by two types of users:
- Application manager
The application manager is always allowed to use this function for all users in the application. - Other users
Other users can also be authorized in the user group settings in the blueprint. For each user group in your application you can define as what other user group a user is allowed to log in.
It is also possible to login as an unspecified user of a certain user group. In this case no specific account is selected to login in. Please note: by using this option, certain functionality of your application might not run properly because a user record is missing.
Two modes
An application manager has two options while being logged in as another user (the other users are always in simulation mode).
- simulate user experience
In this mode you see the application exactly as how the other user would see the application. The only exception is the "go backstage" button in the upper right corner. - with developers tools
Same as simulation with tools added that can be used to debug or improve the application.
Tools in developer mode
Here is a list of some tools in the developer mode. The list is not complete and can be changed by CrossmarX without notice.
- Errors will be displayed as one time messages at the top of the document. Notifiers are not send.
- Velocity errors are shown as a popup providing more information about the location of the error
- Other error pages provide more information about the error situation and/or context
- When a template is missing in a record manager, the data is displayed without a template
- In the login/logout-menu other login-options are added
- In the backstage all permissions are granted as the original user
- All queries can be opened (with same permissions as the original user)
- Velocity scripts are allowed
- In a layout with steps, all steps are directly accesible.
In velocity you can also create your own behavioral changes between developer mode and simulation mode by calling the method Session.isInDevelopmentMode().
Example:
#if($session.isInDevelopmentMode())
Now we print some more information
#end