Expanding the user database
 | Allow operating system access for authorized users only The content of the user database is protected against manipulation with a signature. The names of groups, object protection levels and users are not encrypted and could be read. Access to the IPC should be restricted to authorized users via the operating system. |
| Changes in the database must be signed when saving The changes in the database must be signed by the signing administrator, otherwise the database will be invalid. Signing is automatically queried during the saving process. |
Database template "TemplateOEM"
The "TemplateOEM" database template is designed to cover the most common (simple) use cases without having to define your own group rights. These are:
- Two users: One may do everything, the other nothing.
- Adding/changing database administrators
- Separating the database administrator and developer functions
- Adding more users with the "Developer" group assignment
Separate group rights must be defined for further application cases.
| Download link: Planning table for group rights and Object Protection Level An Excel table for the simple planning of group rights and access rights group sets (Object Protection Level) can be downloaded here. |