# Members

### General

With the help of the membership module, it is possible to make certain types of participation – and thus offers, prices, information, etc. – accessible to members only during the registration process.

To do this, a comparison is made with previously defined test criteria when selecting the type of participation, such as the query of:

* Membership number,
* e-mail address,
* postal code,
* ...

A combination of test criteria is also possible.

### Import of members

In principle, the same guidelines apply to importing member data using CSV template files as to [person import](https://manual.converia.de/teilnehmende/personen-und-teilnehmende-verwalten/personen-in-converia-importieren). Here, we provide additional information that specifically concerns member import.

Member import is list-based. This means that at least one member list must first be created using the *Add list* button (Fig. 1). If there are different types of members or verification criteria, multiple lists must be created.

{% hint style="warning" %}
To make sure attendee data is processed correctly, it's important that member numbers (MEMBER\_ID) are unique and consistent within a list. Converia assumes that these lists come from external databases where each person has a unique ID number.&#x20;

It is generally possible to assign member numbers for use in Converia only, but in this case, special care must be taken to ensure that there are no discrepancies between the member numbers and the associated (possibly already linked) personal data within an event and, in particular, within individual lists. This applies in particular when updating or reimporting lists.
{% endhint %}

{% hint style="success" %}
We recommend maintaining a separate, external member database for each event, in which each person is assigned a unique member number. This reliably prevents incorrect links and data conflicts when using Converia.
{% endhint %}

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FcyfzWSPaDrFpACSnkJXX%2Fimage.png?alt=media&#x26;token=a754e071-942b-4abe-840f-1f30afa27082" alt=""><figcaption><p>Fig. 1: Creating a new member list</p></figcaption></figure>

### Add members individually

A member can be added manually under *Management -> Person Administration -> Members*.

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FufeKsYdy9uOHXC30gBFs%2Fimage.png?alt=media&#x26;token=362257fa-7576-489f-8266-e21a46784b33" alt=""><figcaption><p>Fig. 2: Add member</p></figcaption></figure>

* Fill in the mandatory information and save
* In order to select a *list* in the member data, a list must first be created under *Configuration -> Basic settings -> Member lists*.
* No selection is to be made in the *linked person* field. As soon as the member has successfully registered, a personal account is created and stored as a linked person.

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2F9skq9UUSRaiATrsfFGrG%2Fimage.png?alt=media&#x26;token=ce59e34c-3591-4c21-b72a-f0e069ce5ce4" alt="" width="563"><figcaption><p>Fig. 3: Add list</p></figcaption></figure>

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FZuHz5qQBDhgxfWC0rRJQ%2Fimage.png?alt=media&#x26;token=ed4af51a-2d93-4e6a-9cb4-569b168dedf0" alt="" width="563"><figcaption><p>Fig. 4: List / Linked Person</p></figcaption></figure>

### Configuring the member list

The template file can only be downloaded by clicking on the *“Download CSV import template”* button once a list of members has been created and saved (Fig. 2).<br>

The following configuration options are available:

* *List name* for internal use
* Define the price group to which the member barrier in the participant registration applies.
* If required, a predefined *shopping cart* can be assigned to each member list. The member then has the corresponding booking option(s) already in the shopping cart during the registration process.
* Define the XML *matching criteria* that a member must provide for verification. By default, the member number and the postal code (where only the first 3 digits are compared) are requested (Fig. 5). Without correct information in the registration process, it cannot be continued as a member.
* Other possible criteria for verification include: email address, name, date of birth, company, street or city. **The information to be verified must be stored in Converia in advance so that a comparison can be made.**

{% hint style="info" %}
The configuration of the matching criteria XML (check criteria) is usually done by the Converia support at <support@converia.de>.
{% endhint %}

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FfeQM9lgPTgKdLUdklcjH%2Fimage.png?alt=media&#x26;token=8af64138-cfe9-456c-9d5b-82de22848211" alt=""><figcaption><p>Fig. 5: Configure and import the member list</p></figcaption></figure>

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2F4BbvVqHHeSC1nP23SNfL%2Fimage.png?alt=media&#x26;token=41bdbc85-0ee9-4f76-9e2e-7a37c6707278" alt=""><figcaption><p>Fig. 6: Query of the test criteria for members in the registration process</p></figcaption></figure>

### Create import file and upload

Download the CSV import template, open it as a data import in Excel and fill it in.

* Mandatory information includes:
  * Surname
  * E-mail address
  * Membership number
  * Country
  * Status (1 = active; 0 = inactive)
    * Since all members of an import list should generally be imported as active, a “1” must be entered in the *IS\_ACTIVE* column for all personal data records.
* It is not absolutely necessary to specify a *OPENFEE.* If the member still has an outstanding balance, this can be collected via the registration.
* Store *EXT\_REFERENCE* if a separate number is desired for the member account, e.g. for better data synchronization with your own database.
* Importing the member list
  * To import the data into Converia, save the CSV file with *UTF-8 encoding.* To do this in Excel, please save the file as “CSV UTF-8 (separated by commas) (\*.csv)”.

<figure><img src="https://3664324957-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FFHhRMg6uphOg3wLL7zym%2Fuploads%2FCjKN5NyvRSouyKFILzyw%2Fimage.png?alt=media&#x26;token=5b8dca59-4ce2-4a3a-892c-5b82f4b4ebe3" alt=""><figcaption><p>Fig. 7: Importing the previously edited CSV import template</p></figcaption></figure>

{% hint style="danger" %}
Each time member data is imported (for the first time), the existing data records in Converia are completely overwritten. Changes should therefore ideally be made exclusively in the central member database. Converia should only be updated via regular imports from this database.

If changes are made directly in Converia, they will be lost during the next import unless they have also been recorded in parallel in the member database.

Members who are in Converia but are not included in the current import file are automatically given the status “deleted” in Converia.
{% endhint %}
