<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>FTP: Published Ordered Knowledge Base: : General | WorkRite Support</title>
    <description>Published Ordered Knowledge Base: FTP</description>
    <generator>Helprace RSS</generator>
    <link>https://support.workrite.co.uk/s1-general/knowledgebase/top/c12-ftp?format=rss</link>
    <item>
      <title>Additonal Information</title>
      <description><![CDATA[<ul>
<li>Once logged in to your FTP location, the data file should be places in the root directory. The deactivation sheet should be placed in the Deactivation folder. </li>
<li>When a successful import has taken place, the FTP section within the company details page will be updated with the date, status and name of the uploaded file. Only the last 5 successful imports will be recorded.</li>
<li>The import is triggered immediately when the upload is completed. Imports are limited to run once per day.</li>
</ul>
<ul>
<li>Multiple file uploads are not supported and only the first file will get processed. The others are ignored[_cuted_]</li></ul>]]></description>
      <pubDate>Fri, 28 Jun 2019 10:06:24 +0000</pubDate>
      <link>https://support.workrite.co.uk/i76-additonal-information</link>
      <guid>https://support.workrite.co.uk/i76-additonal-information</guid>
      <author>WorkRite Support</author>
      <dc:creator>WorkRite Support</dc:creator>
      <content:encoded><![CDATA[<ul>
<li>Once logged in to your FTP location, the data file should be places in the root directory. The deactivation sheet should be placed in the <b>Deactivation</b> folder. </li>
<li>When a successful import has taken place, the FTP section within the company details page will be updated with the date, status and name of the uploaded file. Only the last 5 successful imports will be recorded.</li>
<li>The import is triggered immediately when the upload is completed. Imports are limited to run once per day.</li>
</ul>
<ul>
<li>Multiple file uploads are not supported and only the first file will get processed. The others are ignored and removed to the "Archive" folder, and deleted after 30 days.</li>
<li>It is possible that the import will fail. This can be caused by an error in the file formatting, or a specific entry (e.g. user details missing mandatory information).</li>
<li>Failed reports trigger an email to WorkRite Support and any email addresses specified in your FTP configuration.</li>
<li>The User Upload document can be appended to add a Unique User ID column. This can be used as a method of preventing duplicate accounts being made for users. </li>
<li>When naming the upload documents please do not user multiple “.” in the name, for example “file.upload.name.csv” </li></ul>]]></content:encoded>
    </item>
    <item>
      <title>File format requirements</title>
      <description><![CDATA[<p>The user data file can be in .XLSX or .CSV format but must confirm to the WorkRite user data file format requirements. If .XLSX is used, ensure only 1 sheet is in the document, named "Sheet1". If you have not been supplied with the template(s), please contact support@workrite.co.uk. </p> <p>Please note: Do not remove non-mandatory field columns from the spreadsheet. The field can be left blank, where applicable, but the column must remain in the file. </p>]]></description>
      <pubDate>Thu, 27 Jun 2019 14:41:06 +0000</pubDate>
      <link>https://support.workrite.co.uk/i75-file-format-requirements</link>
      <guid>https://support.workrite.co.uk/i75-file-format-requirements</guid>
      <author>WorkRite Support</author>
      <dc:creator>WorkRite Support</dc:creator>
      <content:encoded><![CDATA[<p>The user data file can be in .XLSX or .CSV format but must confirm to the WorkRite user data file format requirements. If .XLSX is used, ensure only 1 sheet is in the document, named "<b>Sheet1</b>". If you have not been supplied with the template(s), please contact support@workrite.co.uk. </p>
<p><i>Please note: Do not remove non-mandatory field columns from the spreadsheet. The field can be left blank, where applicable, but the column must remain in the file.</i> </p>
<table style="width: 1006px;">
<tbody>
<tr>
<td style="width: 91px;">
<p><b>Field name</b> </p>
</td>
<td style="width: 308px;">
<p><b>Note</b> </p>
</td>
<td style="width: 87px;">
<p><b>Required?</b> </p>
</td>
<td style="width: 451px;">
<p><b>Description</b> </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Email</b> </p>
</td>
<td style="width: 308px;">
<p>Must be a valid email address and contain no spaces. </p>
</td>
<td style="width: 87px;">
<p>Yes </p>
</td>
<td style="width: 451px;">
<p>The email address of the user. This will be used as the username for the user. </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Job Title</b> </p>
</td>
<td style="width: 308px;">
<p> 
<br>
 </p>
</td>
<td style="width: 87px;">
<p>No </p>
</td>
<td style="width: 451px;">
<p>The job title of the user can be stored in the WorkRite system, if required. </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Phone no</b> </p>
</td>
<td style="width: 308px;">
<p> 
<br>
 </p>
</td>
<td style="width: 87px;">
<p>No </p>
</td>
<td style="width: 451px;">
<p>The phone number of the user can be stored in the WorkRite system, if required. </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Password</b> </p>
</td>
<td style="width: 308px;">
<p> 
<br>
 </p>
</td>
<td style="width: 87px;">
<p>No </p>
</td>
<td style="width: 451px;">
<p>The initial password of a new user can be specified, if required. </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Employee ID</b> </p>
</td>
<td style="width: 308px;">
<p> 
<br>
 </p>
</td>
<td style="width: 87px;">
<p>No </p>
</td>
<td style="width: 451px;">
<p>The employee ID of the user can be stored in the WorkRite system, if required. </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Firstname</b> </p>
</td>
<td style="width: 308px;">
<p> 
<br>
 </p>
</td>
<td style="width: 87px;">
<p>Yes </p>
</td>
<td style="width: 451px;">
<p>The first name of the user. </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>Surname</b> </p>
</td>
<td style="width: 308px;">
<p> 
<br>
 </p>
</td>
<td style="width: 87px;">
<p>Yes </p>
</td>
<td style="width: 451px;">
<p>The surname of the user </p>
</td>
</tr>
<tr>
<td style="width: 91px;">
<p><b>RoleName </b></p>
</td>
<td style="width: 308px;"> </td>
<td style="width: 87px;">
<p>Yes</p>
</td>
<td style="width: 451px;">
<p>The WorkRite system access role to be provided for the user. This field must contain either Student, Client Manager or Client Administrator. </p>
</td>
</tr>
<tr>
<td style="width: 91px;"><b>Facilitator</b> </td>
<td style="width: 308px;"> </td>
<td style="width: 87px;">No</td>
<td style="width: 451px;">"y" or "yes" to set the user as a facilitator </td>
</tr>
<tr>
<td style="width: 91px;"><b>Location</b> </td>
<td style="width: 308px;"><i>This is an example group type. The title of this column can be amended to suit.</i> </td>
<td style="width: 87px;">Recommended</td>
<td style="width: 451px;">The location of the user. Multiple groups may be listed in this field, separated by a semi-colon. For example, <i>London, Brighton, Manchester.</i> </td>
</tr>
<tr>
<td style="width: 91px;"><b>Department</b></td>
<td style="width: 308px;">This is an example group type. The title of this column can be amended to suit.<i> </i> </td>
<td style="width: 87px;">Recommended</td>
<td style="width: 451px;">The department of the user. Multiple groups may be listed in this field, separated by a semi-colon. For example, <i>IT, Business Systems.</i> </td>
</tr>
<tr>
<td style="width: 91px;"><b>Responsible</b> <b>For</b> <b>Location</b> </td>
<td style="width: 308px;">If Location columns are renamed then this column will require renaming also. For example, if Location has been renamed to 'Business Unit' then this column should be named 'Responsible For Business Unit'. </td>
<td style="width: 87px;"> </td>
<td style="width: 451px;">The location group that the user is responsible for. This applies only to users that are set to Client Manager in the RoleName column. Multiple groups may be listed in this field, separated by a semi-colon. For example, <i>IT, Business Systems.</i> Users with responsibility over other users will be treated as their manager in the WorkRite system. </td>
</tr>
<tr>
<td style="width: 91px;"><b>Responsible</b> <b>For</b> <b>Department</b> </td>
<td style="width: 308px;"> </td>
<td style="width: 87px;"> </td>
<td style="width: 451px;">The department group that the user is responsible for. This applies only to users that are set to Client Manager in the RoleName column. Multiple groups may be listed in this field, separated by a semi-colon. For example, <i>London, Berwick.</i> Users with responsibility over other users will be treated as their manager in the WorkRite system.</td>
</tr>
<tr>
<td style="width: 91px;"><b>Course Group</b> </td>
<td style="width: 308px;"> </td>
<td style="width: 87px;">No</td>
<td style="width: 451px;"> </td>
</tr>
<tr>
<td style="width: 91px;"><b>Additional columns</b> </td>
<td style="width: 308px;"> </td>
<td style="width: 87px;">No</td>
<td style="width: 451px;">Additional group and responsible for group columns may be added to the spreadsheet. All additional columns will be treated as a group type and all data within that column will be a group for the relevant user. </td></tr></tbody></table>]]></content:encoded>
    </item>
    <item>
      <title>Configuration options</title>
      <description><![CDATA[<p>The following options can be configured upon implementation. All of these configurations are optional. </p>
<ul>
<li>Deactivation of users - When enabled, users who are no longer present on the user data file will be deactivated in the WorkRite system. This configuration would normally only be disabled if the deactivation of leavers is to be handled as a manual task or using the bulk deactivation template. </li>
<li>Change user groups - When enabled, user groups (i.e. Locations, Departments etc) will be updated in the WorkRite system in line with the latest user data file. The user will be removed from any previous groups[_cuted_]</li></ul>]]></description>
      <pubDate>Thu, 27 Jun 2019 14:41:11 +0000</pubDate>
      <link>https://support.workrite.co.uk/i74-configuration-options</link>
      <guid>https://support.workrite.co.uk/i74-configuration-options</guid>
      <author>WorkRite Support</author>
      <dc:creator>WorkRite Support</dc:creator>
      <content:encoded><![CDATA[<p>The following options can be configured upon implementation. All of these configurations are optional. </p>
<ul>
<li><b>Deactivation of users</b> - When <b>enabled</b>, users who are no longer present on the user data file will be deactivated in the WorkRite system. This configuration would normally only be disabled if the deactivation of leavers is to be handled as a manual task or using the bulk deactivation template. </li>
<li><b>Change user groups</b> - When <b>enabled</b>, user groups (i.e. Locations, Departments etc) will be updated in the WorkRite system in line with the latest user data file. The user will be removed from any previous groups and added to any groups listed on the latest user data file. Additional configuration rules can be applied to updates to the user groups, see below for more information. When <b>disabled</b>, the users will get added to any groups but not removed from any. The following options only apply when this is enabled: </li>
</ul>
<ul>
<li><b>Course group change prevention</b> - When enabled, user's course groups will <b><i>not</i></b> be updated in the WorkRite system in line with the latest user data file. This is only applicable if the 'Change user groups' configuration is enabled. </li>
<li><b>Geographical group change prevention</b> - When enabled, user's geographical groups will <b><i>not</i></b> be updated in the WorkRite system in line with the latest user data file. Geographical groups are specified at Group Type level and normally represent a physical location attribute for the user, for example Location or Office. This is only applicable if the 'Change user groups' configuration is enabled. </li>
<li><b>Non-geographical group change prevention</b> - When enabled, user's non-geographical groups will <b><i>not</i></b> be updated in the WorkRite system in line with the latest user data file. This is only applicable if the 'Change user groups' configuration is enabled. </li>
<li><b>Change user role</b> - When enabled, user roles (i.e. Student, Client Manager, Client Administrator) will be updated in the WorkRite system in line with the latest user data file. </li>
</ul>
<ul>
<li><b>Rename deactivated users –</b> When enabled, if a user is deactivated, the user will have the string <b><i>"</i></b><b><i>deactivatedyyyymmdd</i></b><b><i>"</i></b> appended to their username, where <b><i>"</i></b><b><i>yyyymmdd</i></b><b><i>"</i></b> is replaced by the date the import is running. Useful if re-issuing email addresses is required. </li></ul>]]></content:encoded>
    </item>
    <item>
      <title>Managing users by FTP</title>
      <description><![CDATA[<p>WorkRite support the uploading of .CSV or .XLSX formatted documents which are processed to perform user management actions (create, update or remove users) The Importer runs overnight daily and can accept 1 file each time. </p>
<p>User data file import configuration options </p>
<p>There are two different methods of structuring user data files for processing by WorkRite, each of these has its own configuration options and file format requirements. </p>
<p>The appropriate method will depend on the data of the source system, the export capabilities and your business requirements. </p>
<ol>
<li>A single regular user data file</li>
</ol>
<p>WorkRite can accept a single file containing all[_cuted_]</p>]]></description>
      <pubDate>Thu, 27 Jun 2019 14:15:08 +0000</pubDate>
      <link>https://support.workrite.co.uk/i73-managing-users-by-ftp</link>
      <guid>https://support.workrite.co.uk/i73-managing-users-by-ftp</guid>
      <author>WorkRite Support</author>
      <dc:creator>WorkRite Support</dc:creator>
      <content:encoded><![CDATA[<p><span>WorkRite support the uploading of .CSV or .XLSX formatted documents which are processed to perform user management actions (create, update or remove users) The Importer runs overnight daily and can accept 1 file each time.</span><span> </span></p>
<p><b><span>User data file import configuration options</span></b><span> </span></p>
<p><span>There are two different methods of structuring user data files for processing by WorkRite, each of these has its own configuration options and file format requirements.</span><span> </span></p>
<p><span>The appropriate method will depend on the data of the source system, the export capabilities and your business requirements.</span><span> </span></p>
<ol>
<li><b><span>A single regular user data file</span></b></li>
</ol>
<p><span>WorkRite can accept a single file containing all current user data. This is the most appropriate method where the data being sent consists of a full snapshot of all users that should currently have access to the WorkRite system.</span><span> </span></p>
<ol>
<li><b><span>Separate Starters and Leavers data files</span></b></li>
</ol>
<p><span>Separate files, one containing the users to be updated or added, and another containing a list of users to deactivate. </span><span> </span></p>]]></content:encoded>
    </item>
  </channel>
</rss>
