The DSGVO contains rules on the protection of individuals with regard to the processing of personal data.
CADENAS processes user-related data such as name, computer name, time, etc. according to the used software processes and functions.
In the following, detailed information is subdivided into singe use cases.
In general, all Windows users and groups can be displayed under PARTadmin -> Rights management [Rights administration] category -> User databases tab page on the Windows tab page. As a rule, the PARTadmin module is only available to the administration and access to GDPR-relevant files is regulated via the Windows rights management.
Other AD attributes can also be queried in PARTadmin -> Rights management [Rights administration] category -> User databases tab -> LDAP tab. However, filters must be configured accordingly.
For AppServer administration, the PARTapplicationServer dashboard can be opened via PARTadmin -> AppServer Client [AppServer client] category -> Diagnostics [Diagnostic] dialog area by clicking on .
You will find the following subcategories on the System information tab page:
![[Note]](https://webapi.partcommunity.com/service/help/latest/pages/cn/3dfindit/doc/images/note.png)
Data is saved according to the configuration under PARTadmin -> Rights management [Rights administration] category -> Rights assignment [Assign rights] tab page:
![ERP -> Roll set [Role set]](https://webapi.partcommunity.com/service/help/latest/pages/cn/3dfindit/doc/resources/img/img_a66f93c164b343118e4488605e722d37.png)
Neither if users have different roles and profiles (see example below)
In the following you can see an example how a user-related and a neutral login may look like.
As soon as the Active option is activated on the Windows tab page under PARTadmin -> Rights management [Rights administration] category -> User databases tab page, a user-related login can be carried out.
-> When logging in with the Windows user, user ID, group, group membership and domain are registered.
-> The Windows username is displayed at different places of the software, for example in the status line.
The user-related login may happen manually or automatically.
The following scenario will exemplarily show how to set up a neutral, meaning not user-related login:
Deactivate the Windows option in PARTadmin -> Rights management [Rights administration] category -> User databases tab page
Activate the ERP (plinkusers) option in PARTadmin -> Rights management [Rights administration] category -> User databases tab page and create users.
These users you have to get assigned a role set.
-> Now when calling an application (e.g. PARTdataManager) the user authentication with a created ERP user and password can happen.
With an incorrect entry a respective message is displayed.
-> In PARTdataManager, role set (and role) is displayed in the status line (no Windows user).
An alternative solution for working with a neutral database login is to use a group name as the Windows login. (This solution is only GDPR-compliant if the group has more than one user)
Another alternative besides the group name is to assign the configuration "Default/Logged in". This then applies for all users, which are not assigned in any other way.
A database password must be saved to access the ERP database.
The entry is made under PARTadmin -> Category ERP environment -> Database connection.
DB [DB User] user/DB [DB Password] password [DB User] or DBO [DBO user] user/DBO [DBO Password] password [DBO user] are stored in encrypted form.
The password is saved in the configuration file plinkusers.cfg.
!["Database connection [Database connection] " category -> " Available database connections " dialog area](https://webapi.partcommunity.com/service/help/latest/pages/cn/3dfindit/doc/resources/img/img_38a68360136b4473a16b5f86c6de8c69.png)
"Database connection [Database connection] " category -> " Available database connections " dialog area
User-related data can also be saved during data processing, such as the creation of an ERP number or changes to roles and rights.
When adding an ERP number the following entries are set in the LOGTABLE, among others:
Call via PARTlinkManager -> tab page "Extras [Extras] " -> "Database [Database] " -> "Edit additional tables [Edit additional tables] "
CAD environment: Date creation in the CAD environment (CAD attributes)
Concerning the attributes transferred to the CAD only the ones written in the LOGTABLE are stored on the part of CADENAS.
![Call via PARTlinkManager -> tab page "Extras [Extras] " -> "Database [Database] " -> "Edit additional tables [Edit additional tables] "](https://webapi.partcommunity.com/service/help/latest/pages/cn/3dfindit/doc/resources/img/img_c69d3c52c7394c6d82beaa648d39b253.png)
PARTadmin -> Category Catalog update -> Online
Email and password are stored in partupdate.cfg.
Each CIP download is allocated to a user. Username and also IP are stored.
Logging can be used for analysis purposes.
In the Logging settings [Log settings] dialog, part of the Settings dialog page, which you can open from PARTsolutions and eCATALOGsolutions modules via Tools [Extras] menu -> Settings [Preferences], you can define the log level. The user name, for example, is also logged during the login process in modules.
The logging data is output in the output file at $Temp\psol_logs\cadenas_error.log.
The display in the GUI takes place in the log window [Log window] of the respective module.
GDPR-relevant information regarding license servers can be found on the Section 1.4.4.4, “ Security " tab page ”. This point is also relevant without ERP.