-
-
-
- User interface versions
- Building blocks for user interface design
- Adding styles with a css
- Surrounding page
- Changing snippets
- Creating a custom login page (pre 3.4)
- Creating a custom login page
- Using velocity templates within the blueprint
- Create your own web pages
- HTML delivery requirements
- How to customize system mails
-
- Resource files
- Velocity - How does it work?
- Quick Velocity Tutorial
- Debugging velocity scripts
- Velocity Command Reference
- Script Editor Tutorial
- Using velocity for calculations
- Using predefined forms in a html design
- Velocity forms
- Data field identifiers
- Macros and methods
- Velocity library
- Velocity: using the #macro command
- velocity and xml
- Using AJAX in your velocity scripts
-
-
- Argon2 password conversion
- Introduction to security
- Secure development
- Security certification
- Security Exam
- Field properties concerning security
- Developing user groups securely
- Security considerations for user interface
- Secure file organization
- Securely using the request
- Cross Site Scripting (XSS)
- Other options concerning secure development
- Security analysis
- Secure deployment
- Secure application management
- Scrambling of testdata
- Anonymization of personal data
- Using robots.txt
- Permission settings
- Security measures
- Data encryption
-
- Search Engine Optimization
- OTP
- 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
- Instances
- Componenten in onze technologie
- Google Analytics
- Street and City helper (postcodecheck)
- Responsible disclosure-beleid
- Postcode check service (straat en huisnummer) kosten
- Expressions
- Regular Expression Reference
-
User accounts
Every person who wants to login to the application needs a user account. A user account is used to identify a person. In the account the following is registered:
- means of identification (and communication), like email addresses and phone numbers,
- ways of authentication, like passwords,
- a login name (optional),
- the user group.
An account is always related to a record of a blueprint class containing other information about the user, like name and address.
How to start?
For using accounts, follow these steps:
- Define user groups. See Permissions /authorizations.
- Define the classes in the blueprint that contain data about users, like a class 'person'. This class should at least have a field with data type 'Email address'. On the tab "Relevances" set the property "Email field for account" to the email field that is used to communicate about the account.
- Reload the blueprint.
Account can be created in two ways:
- Accounts can be created by the application manager or other authorized users.
Learn more - Accounts can be a created by the current (anonymous) user, using a registration form to create an account for him/herself.
Learn more
User accounts can be created (and managed) by the application manager or by users of an authorized user group.
Two factor authentication
An account can be protected by two-factor authentication methods. Two-factor authentication is a security process in which users provide two different authentication factors. Two-factor authentication provides a higher level of security than authentication methods in which the user provides only one factor, typically a password.
The following second-factor methods are available:
- Email
The user receives a login code by email. - One-time password (OTP) app
The user generates a login code with an OTP app. See https://studio.crossmarx.nl/page/1094/otp. - SMS
The user receives a login code by SMS. Extra costs are involved for sending SMS messages. - Service desk
When everyting else fails, a code can be generated by another user with suffiicient authorization.
To activate two-factor authentication, the developer can set the properties 'Two factor frequency' and 'Two factor methods' at the usergroup in the blueprint.
Note on security
From a security perspective, it is strongly recommended to add two-factor authentication to user groups that have broad permissions. Consider using something other than e-mail as second-factor method if you expect users of your application to use the same password for their email and your application. Losing this password to a third party will immediately grant them access to the application.
Account info
With this calculation helper you can add a field to a user record with information about the account of this user. It's also possible to search on this information. Learn more
Mail settings
The process heavily relies on emails. For example when resetting a password, verfication, two-factor login etc... Therefore it is important to ensure email is sent properly by your application.
Learn about email settings.