Can I add a plugin to HIFIS?

Some communities may be interested in adding a plugin to their HIFIS instance. For example, we use Help Scout! Is this allowed?

The answer isn't super straightforward. According to the End-User License Agreement (EULA), HIFIS License holders assume all risks when configuring their HIFIS instance and installing plugins:

• License holders can install third-party software, APIs, and plug-ins within HIFIS where allowable. Third-party software, APIs, and Plug-ins will be governed by the third-party licence agreement and must not exceed the scope of HIFIS and this Agreement.
• The HIFIS Lead is responsible for any third-party services or software, APIs, and/or plug-ins that is adopted.
• The Department [INFC] will not be responsible nor liable for any third-party services or software, APIs and/or plug-ins that the HIFIS Lead adopts.
• The Department [INFC], its employees, and agents, shall not be liable for any claims, damages, injuries, and loss of any kind, whether direct or indirect, consequential or incidental, arising from the use or the inability to use HIFIS. This includes, but not restricted to, loss of revenue, profit or savings, lost, damaged or stolen data, or other commercial or economic loss.

Here's what INFC specifically has to say on the matter:

The implementation of any plugin is at the discretion of the community, and any community decision to implement a plugin should be done after careful consideration of how to protect the quality of the data, application function, application security, and privacy of the clients.

Specifically, we recommend that a community consider the following questions when exploring the possibility of a plugin. If they answer ‘Yes’ to any of them, they should reconsider or investigate further to determine the impact.

• Does the plugin add, edit, delete, view, or have any access to data in the HIFIS database?
• Does the plugin impact the quarterly data export in any way?
• Does the plugin impact the proper, secure function of the HIFIS application (including, but not limited to, circumnavigating user rights)?
• Does the plugin capture and/or store any kind of data or information that will be shared, transferred, or sold to third-party party applications, organizations etc.?
• Does the plugin capture information from the application (images, session information, internet traffic information, etc.) and retain it?
• Could the plugin cause a HIFIS error and result in INFC spending significant time and resources trying to fix it?
• Does the plugin pose a risk to the public perception of the organizations using HIFIS, the Reaching Home Program and/or the Government of Canada?
• Will the plugin be implemented without clients being informed on the consent form (if necessary)?
• Will the plugin be implemented without all organizations that use HIFIS being informed?
• Will Reaching Home funding be used for the development and maintenance of the plugin?