FileConnect is the RecordPoint connector for File Shares and networked drives, allowing you to manage on-premises content as records in Records365.
Learn how to install, configure, activate and import records with FileConnect!
Records365 FileConnect requires an additional subscription. If you would like to inquire about subscribing, or you believe your organization has subscribed and the connector is missing from the Gallery please contact support.
FileConnect runs as a Windows service in your on-premises corporate network. The diagram below shows the components in the FileConnect connector and how they interact.
FileConnect polls Records365 to determine whether any disposal actions need to be performed on your file share content, so Records365 requires no changes inbound to your corporate network. The only requirement is that the machine where FileConnect is running must be able to access the Internet.
FileConnect communicates with Records365 strictly over HTTPS on port 443 using TLS 1.2. FileConnect uses a polling mechanism over HTTPS to send record submissions & retrieve disposal information from Records365.
To configure Azure Active Directory for FileConnect you need to be an Azure AD Global Administrator or Application Administrator.
Records365 delegates authorization and authentication to your Azure AD environment, and extends this model to the FileConnect on-premises connector with an Azure AD App that is registered in your tenant.
FileConnect uses the OAuth 2.0 protocol to authenticate and authorize the connector against your Azure AD, and then securely submit information to Records365. No keys, secrets, or inbound network ports are required to communicate with Records365. To read more about Azure AD and how it is used for application authentication see Azure Active Directory for developers.
Connectors are Disabled by default. This means no content will be submitted from the connector until the connector is Enabled. Before enabling a Connector, ensure that all rules have been set up first otherwise your records will be uncategorized. To complete the rules setup refer to Rules.
FileConnect does not need to be installed on the same server as the file share and documents you plan to manage.
We recommend that FileConnect is installed on a dedicated virtual or physical server.
Minimum software requirements:
FileConnect supports managing content in networked File Shares that are visible to the Windows filesystem of the host machine (NTFS only). If you can open a file in a Network Share in Windows Explorer from the server where FileConnect is installed, then FileConnect should be able to manage it.
FileConnect communicates with Records365 over HTTPS and will require access to the Internet. FileConnect leverages the underlying Windows proxy settings and no additional proxy configuration should be required.
If your organization has purchased FileConnect, you can download the installation package from the Connector Gallery by clicking on the FileConnect tile in the Gallery and clicking the Server Component Installer button in the configuration tab.
The FileConnect application installs a Windows service and a simple configuration executable. Once the installation is complete, open the RecordPoint FileConnect configuration application from the start menu or by running RecordPoint.Active.Configuration.exe from your installation directory (by default, C:\Program Files\RecordPointFileConnect).
FileConnect is now succesfully installed.
Now we are ready to begin creating Watched Folders in FileConnect and importing existing content! See Administration for FileConnect to continue.