Sysero can be integrated with many of the market leading document management systems.  In order for the integration to work, security credentials need to be matched between Sysero and the DMS.  The security credentials need to identify:

• The source servers of both systems
• The access level of the user within both systems.  For example, Sysero uses the concept of "Sites" where a user may have access to data in 1 or more sites within a single server. 
• The role of the user.  This will define the access rights within the access level
• The identity of the user including name and the email address which is the primary user identifier within Sysero.

Types of Integration

The configuration of the integration deployed is dependent on the business use:

Login from Third Party

Please see this article Sysero Setting up OAuth Login from External Systems

Sysero to DMS

This feature is used in two scenarios:

• Sysero is running a data collection workflow, such as AML/KYC, and collects documents as part of the workflow. If the client/matter is accepted, the documents need to be filed into the DMS.
• Where documents are created by Sysero as part of a workflow.

In order to file documents into the DMS, Sysero needs to be supplied with the target container information such as the workspace and folder.   This can be done by querying the DMS database using either SQL or via an API to present a searchable list to the user.  Once the target has been identified, Sysero uses the user’s identity, or an impersonation identity, to file the documents.

DMS to Sysero

Sysero can take copies of DMS documents and route them into workflows and knowledge databases.  This requires that an API be available from the DMS vendor to allow “Send To” functionality that passes the document, and available metadata to Sysero using the identity of the current user to assign correct privileges. 

Create from DMS

This feature provides the ability to start a Sysero Workflow from a folder within the DMS with the subsequent files saved back into the folder.  It requires the integration features described in the previous 2 scenarios.

User Synchronisation

The process of synchronising users can be mostly automatic or may require that lists of users, access levels and roles are maintained separately.