Client

Select the target client into which the users are to be imported.

CSV Settings

• Separator: Use a semicolon (“;”) to avoid conflicts caused by commas in the fields.
• Set minimum data quantity: Functions as a security mechanism to ensure that only complete files are imported.
  • Specify a threshold for the import to prevent incomplete files.
  • Example: For 5000 data records, approximately 90% can be specified as the threshold (e.g., 4500).

User Profile Configuration

Describes the target of an import.

• Define the mandatory data for the import:
  • System: Target system of the import.
  • Client: Client to be imported.
  • Profile: Specific user profile to separate imports from each other.
• Note:
  • If multiple imports are to be performed on one client, they are separated by the user profile.

Notifications

Welcome notification: Enable or disable email notifications for the import status. The message is sent directly and cannot be delayed.

User Settings

• Login mechanism: Define how users are allowed to log in (e.g., username, personnel number). This is a default value that takes effect if no other value is provided in the data itself (login_Type column).
• Change password: Specify whether the password must be changed upon first login.
• Generate password: Specify which method should be used to create the password. You can choose between creating it according to the password policy and using the login.

Deletion Concept

• Delete user: Specify which status users who are not included in the import should receive: Inactive, Deleted, or Permanent deletion. Recommendation: “Deactivate” users when they are inactive instead of deleting them completely.
• Anonymize: Decide whether anonymization should take place and specify after how many days users who are not included in the import should be anonymized after receiving the Inactive status.
• Permanent deletion: Decide whether users should be permanently deleted and specify after how many days users who are not included in the import should be permanently removed after receiving the status Inactive or Deleted.

Role Settings

Role import: Specify whether roles should be imported based on the title or the external reference.

Author Settings (optional)

This is an optional additional function. You should ensure that the authorization groups of the authors can be managed externally (e.g., external references of the authorization groups are additionally passed on to the users).

• Determine what the newly created author should be called. Assign a suffix here, which is added to the login.
• Note: Authorization management is required for the author import.

Authorization Group Settings

1. Select the default authorization group: Here you assign an authorization group to all users when they are created. You can then adjust settings for all users later. A later automatic assignment of authorization groups is not possible.
   • Recommended: Standard user, team leader, authors.
2. Optional: Add more authorization groups if required. These must be defined in the data record.

Identification: Specify how users should be uniquely identified. By default, the user in Avendoo is identified via the username during an import. However, it is also possible to define another attribute for this comparison. This enables the username to be changed if, for example, it contains a name.

OE Configuration: Here you can link several data fields of the import to populate the OE field in Avendoo. This can be advantageous for a more precise team leader assignment.

Attribute Assignment

• Assignment of external fields (CSV) to Avendoo fields:
  • Left column: Fields from Avendoo (e.g., last name).
  • Right column: Column names from the CSV file (e.g., Lastname).
• Target: A kind of “translation” to correctly assign data.