Drop system role from description

v1.7.0/setup/3.-installation/3.2-set-up-your-own-country-configuration/3.2.4-set-up-employees-for-testing-or-production/3.2.3.1-prepare-source-file-for-test-employees.md

@@ -30,7 +30,7 @@ In production, the National System Administrator user will use the OpenCRVS UI t
 
 Using our [default-employees.csv](https://github.com/opencrvs/opencrvs-countryconfig/blob/develop/src/data-seeding/employees/source/default-employees.csv) file as an example, you can create employees with all possible roles to quality assure your OpenCRVS instance, or just a single National System Admin role. Our deafult-employees.csv file looks like this:
 
-<table><thead><tr><th>primaryOfficeId</th><th width="225">givenNames</th><th>familyName</th><th>systemRole</th><th>role</th><th>mobile</th><th>username</th><th>email</th><th>password</th></tr></thead><tbody><tr><td>CRVS_OFFICE_JWMRGwDBXK</td><td>Kalusha</td><td>Bwalya</td><td>FIELD_AGENT</td><td>Social Worker</td><td>0911111111</td><td>k.bwalya</td><td>[email protected]</td><td>test</td></tr><tr><td>CRVS_OFFICE_JWMRGwDBXK</td><td>Felix</td><td>Katongo</td><td>REGISTRATION_AGENT</td><td>Registration Agent</td><td>0922222222</td><td>f.katongo</td><td>[email protected]</td><td>test</td></tr><tr><td>CRVS_OFFICE_JWMRGwDBXK</td><td>Kennedy</td><td>Mweene</td><td>LOCAL_REGISTRAR</td><td>Local Registrar</td><td>0933333333</td><td>k.mweene</td><td>[email protected]</td><td>test</td></tr></tbody></table>
+<table><thead><tr><th>primaryOfficeId</th><th width="225">givenNames</th><th>familyName</th><th>role</th><th>mobile</th><th>username</th><th>email</th><th>password</th></tr></thead><tbody><tr><td>CRVS_OFFICE_JWMRGwDBXK</td><td>Kalusha</td><td>Bwalya</td><td>FIELD_AGENT</td><td>0911111111</td><td>k.bwalya</td><td>[email protected]</td><td>test</td></tr><tr><td>CRVS_OFFICE_JWMRGwDBXK</td><td>Felix</td><td>Katongo</td><td>REGISTRATION_AGENT</td><td>0922222222</td><td>f.katongo</td><td>[email protected]</td><td>test</td></tr><tr><td>CRVS_OFFICE_JWMRGwDBXK</td><td>Kennedy</td><td>Mweene</td><td>LOCAL_REGISTRAR</td><td>0933333333</td><td>k.mweene</td><td>[email protected]</td><td>test</td></tr></tbody></table>
 
 {% hint style="danger" %}
 Do not change or re-format the header row as the code requires these names to be precise in order to parse the csv. Do not use commas in any cell and do not have any empty rows.
@@ -40,7 +40,7 @@ Do not change or re-format the header row as the code requires these names to be
 * The **primaryOfficeId** column is the identifier for the civil registration office where the user will be located. Notice that the format is "CRVS\_OFFICE\_\<office **id**>". For example, all of these users aove will be created in Ibombo District Office
 * The **givenNames** column must be the users' first names separated by using a space.
 * The **familyName** column must be the users' first names separated by using a space.
-* The **systemRole** column must be set to one of the following supported system roles only, and this defines user permissions:
+* The **role** column must be set to one of the following supported system roles only, and this defines user permissions:
 
 FIELD\_AGENT
 
@@ -56,7 +56,6 @@ NATIONAL\_REGISTRAR
 
 PERFORMANCE\_MANAGEMENT
 
-* The **role** column can be any text value to represent the public facing role title for this individual.  Role title configuration is explained in the next section.
 * The **mobile** column must contain a mobile number **without** your country code. Ensure that the mobile number validates using whatever phone number regular expression that you intend to use when configuring application settings later. You can ignore this if you are not using phone numbers as a method of communication.
 * The **username** column must be a unique username that the user will use to authenticate with when logging in.
 * The **email** column must contain a valid email address