> ## Knowledge Base Index
> Fetch the complete knowledge base index at: https://helpdesk.pluvo.com/sitemap.xml
> Use this file to discover available pages before exploring further.
> Pure-Markdown content can be obtained by appending a '.md' suffix to the content URLs listed in the sitemap (without the trailing slash).

# AFAS GetConnector: Course Management (Manual)

# Configuring the GetConnector for Course Management

It's important to have a user group with the appropriate permissions. If not set up yet, here's how to configure it: [AFAS User Group Configuration](/en/article/afas-getconnector-user-synchronization-ytlpv2/)

# Setting up the GetConnector for Course Management

![](https://storage.crisp.chat/users/helpdesk/website/efb20d00b64eb000/cursusbeheer-handmatig-1_48ap8a.png)

1. Within the menu **General** under **Output**, select **Administration** and then choose **GetConnector**. You'll see the following screen. Open the **GetConnector** used for course participants within your organization. In our example, this is _Participant_per_course_event_. As shown below, you can filter by name to ease finding your **GetConnector**.

![](https://storage.crisp.chat/users/helpdesk/website/efb20d00b64eb000/cursusbeheer-handmatig-2_g7hvt7.png)

2. Upon opening, a new window appears. First, click **Next**, then **Data**, which will take you to the next screen.

![](https://storage.crisp.chat/users/helpdesk/website/efb20d00b64eb000/cursusbeheer-handmatig-3_vyc0uv.png)

Here, you can configure the fields of the **GetConnector**. The left menu contains all available fields, while the right side displays the fields linked to the **GetConnector**.

## Mandatory Fields:

For proper functionality, the following fields are necessary:

  - A name field.
  - A primary email field.
  - A secondary email field.
  - A field for the Contact ID of the user.
  - A field for the Person ID of the user.

Using primary and secondary fields enables different email fields for various user groups (e.g., _Email_Priv_ for _Individuals_, while _Individuals within an Organization_ have an additional _Email_Work_). Pluvo always checks the _primary email field_ first and then the _secondary email field_ if the primary is empty. If your organization uses only one email field, there's no need to configure a _secondary email field_.

## Adding Contact / Person ID Fields

Both ID fields are somewhat hidden in AFAS.

You can find the **Contact ID** in **Participant per event -> Participant -> Participant -> General -> Contact**.

![](https://storage.crisp.chat/users/helpdesk/website/efb20d00b64eb000/cursusbeheer-handmatig-4_49v82z.png)

The **Person ID** is located in **Participant per event -> Participant -> Participant -> Organization/Person -> Organization/Person**.

![](https://storage.crisp.chat/users/helpdesk/website/efb20d00b64eb000/cursusbeheer-handmatig-5_86urec.png)

## Field and Connector Names

The field names in the example above (_primary email, secondary email, etc._) are mere examples. You can name these fields and even the connectors as you wish - however, you must provide us with these names.

## Information for your GetConnector

For your GetConnector, we need the following information:

  - The name of the GetConnector.
  - The name of the name field.
  - The name of the primary email field.
  - The name of the secondary email field.
  - The name of the Contact ID field.
  - The name of the Person ID field.

## Additional Option: Filter Users from the List After a Specific Date

If you don't want to send users after a specific date to Pluvo, you'll need to include an extra field with a date. Add this field to the events in your AFAS course management and then to the GetConnector. This should be a 'dateTime' field type.

## Place AFAS Course ID in Pluvo Learning Path

More information about placing the AFAS course ID in the Pluvo learning path: [AFAS Get/Updateconnector: Linking Course Management Course to Learning ](/en/article/afas-updateconnector-course-management-176vagt/)