What can be expected?

The user registration via FTP will register every new user, and update any existing user in MobieTrain, based on information coming from the CSV file.
Every 24 hours, this sync process is run.
New users will receive an email to finish the registration. They will have to click the button in the email, and define their password to finish the registration.
New users will have to log in via MobieTrain, to access the app.
Any user that already exists, will be updated with the file information.
If a user has an end date, the user will be deleted (see conditions below).

How Does It Work?

MobieTrain creates a folder in an FTP server, so that the client is able to upload CSV files with the users’ information. The credentials are sent to the client:
Protocol: SFTP Host: 34.77.100.54 User: client-user Password: client-password
The client can then start to leave the CSV Users file in the folder.
Every day, the update process is run at 4:00 UTC.
Any new user will be registered, and they will receive an email to finish their registration.
Any data change in existing users will be updated.
If a contract end date of an employee is sent, the user will be deleted on processing. Only if the date is on or before today. Users with contract dates in the future will not be deleted.
After the file is processed, both the original file and an additional file with a list of results (both in CSV format), are sent to a processed folder, so that they can be checked for errors.

If any errors occur in this integration, the employee data should be corrected in the client’s source system and placed in the FTP folder again. It is the client’s responsibility to monitor and correct any errors.
The CSV files have to be comma (,) separated, encoded as UTF-8, and without a header line. User groups need to be seperated by a semicolon (;).
The CSV should always follow the format and field order stipulated.

The client should be able to drop a file in the FTP folder of their account.
Before going live, a test file with a few users should be left in the FTP server, in order to be processed and check if the process goes through.

It is the responsibility of the client to control the integration results.
Every day, when a file is processed, a results file is generated - also available in the client’s FTP area - where success and/or errors can be found for each line.
The client should go through this file and correct and re-submit any users that didn’t go through. At this moment, there’s no way to automate the erroneous submissions report.

Can I assign Users to User Groups manually?
You shouldn’t. That information will be overwritten. The CSV files are considered the source of truth, so every day, when we sync the users’ information, the user groups existing in the file will be the ones that will be assigned to the users.
What is causing “ERR-40141: Invalid data format” in some of my users?
This can be caused by: Invalid CSV line (we expect a line with 13 columns) and/or the data inside columns doesn't match the defined schema. Take into consideration that emails should be valid and TLDs are checked according to https://data.iana.org/TLD/tlds-alpha-by-domain.txt.
Can I use the CSV User Update just to delete users?
Yes. This process can be used only to delete users, as long as the file only contains existing users and have contract end dates for them.
My file was not picked up. What might be the cause?
One of the reasons might be because the process is case-sensitive, and the file extension should be all lower-case (.csv).