M-Files Connector Prerequisites

Before you begin the M-Files connector deployment, ensure an M-Files  Administrator can participate in the deployment process to assign the M-Files specific tasks.

User Accounts and Application Permissions

Required Permission	Description
M-Files Account	A crawling account must be created in M-Files.  Account must have READ access to all objects to crawl. Account must have permission to get user, groups, permissions, and definitions of: object types classes properties

Network and Connectivity

Port	Requirement
HTTP/HTTPS	The M-Files site must be accessible via HTTP/HTTPS from the server where the connector is deployed

Connector Features and Requirements

Features	Supported	Additional Information
M-Files version support	Version 2015 and above	Connector can be used even if M-Files is hosted on the local network or on the cloud.
Searchable content types	All type of objects.
Content Update	Full and Incremental	All BA Insight Connectors support both Full and Incremental crawls, unless noted.
Permission Types	Yes	All BA Insight Connectors support fetch ACLs from the source system Your Source System is the repository where your data is stored (data to be indexed). This repository is managed by applications such as: - SharePoint O365 - SharePoint 2013/16/19 - Documentum - File Share - OpenText - Lotus Notes - etc. Your Source System repository can also be a database such as SQL or Oracle.. To make items public or restricted to a single user/set of users, use Connectivity Hub. To support permissions, Advanced Security module is required.
Required Software	BA Insight Advanced Security Module	The M-Files Connector requires the BA Insight Advanced Security Module to honor the full security model defined in Jira.