-
-
-
- Building blocks of the data model
- Basic concepts
- Classes
- Key fields
- Local lookup lists
- Fields and data types
- Defining the columns of a table
- Relations between classes
- Global lookup lists
- Filters
- Universal connected classes
- Deleting foreign records
- Class inheritance
- Storage of personal data on test and develop environment (scrambling)
-
- 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
-
Permission packages
In addition to regular user groups, Permission packages can be used to organize permissions. Permission packages are a type of user group that only describe permissions to classes, fields and actions. In order to use permission packages, the improvement step 'Use multiple inheritance of user groups' must be active.
Regular user groups can be granted multiple permission packages, effectively inheriting a combination of all their permissions (for more information about multiple inheritance of user groups see this page). This allows the developer to organize their permissions in a more inspect-able way. For instance, a user group Admin may have the package Financial, which allows it to search and read invoices. Another user group Manager, may also be given the package Financial. Now, when inspecting which user groups have permission to search and read invoices, simply check which user groups have been given the package Financial.
Permission packages can also be granted to accounts. This makes it possible to grant specific users extra permissions, in addition to the permissions of their user group. For instance, the Employee user group may normally have no permissions on invoices. A single employee can be given the package Financial, so that they can also search and read invoices.
Multiple inheritance of permission packages is also possible on account level.