Installing Excel Add-in (Admin/IT)

For many organizations, this requires individual users to install the CurinosConnect app from the Microsoft App Store. Please refer to Activating the Excel Add-in for details. However, not all organizations allow users to access the App Store. In such cases, a manifest file installation is required. Details regarding the manifest file are provided below.

Note: If you experience installation issues or have any questions, please don't hesitate to reach out to Curinos for help figuring out the easiest method at your organization: clientservices@curinos.com.

A manifest file is required for all Microsoft Office product Add-ins (like the CurinosConnect Excel Add-in) who do not have access to the Microsoft App Store. While all data as well as the CurinosConnect UI are hosted and secured at Curinos, each organization without user access to the Microsoft App Store will need to place a small, non-executable file on a team shared network folder so that each user can install the Excel Add-in.

Microsoft refers to the small file as a 'manifest' file. For those interested in more information about the purpose and contents of the manifest file, see some excerpts from Microsoft's help documentation below (edited in some cases for clarity).

The XML manifest file of an Office Add-in details the mechanisms that allow your add-in to be activated when a user installs and uses it with Office documents and applications. An XML manifest file enables an Office Add-in to do the following:

• Describe itself by providing a name, description, version number, etc.
• Link to the URL for the image used in the Office app ribbon.
• Specify how the add-in integrates with Office, including the URL for any custom UI.
• Specify the default on-screen size of the add-in.
• Declare permissions that the Office Add-in requires, such as reading or writing to the document.

To review the full text of Microsoft's details on the manifest file: https://docs.microsoft.com/en-us/office/dev/add-ins/develop/add-in-manifests?tabs=tabid-1

Choosing one of three options: Network drive/Sharepoint/Admin managed

Installing the manifest file on a Network drive This is perhaps the most straight-forward and easiest options because this is a one-time process for your organization. However, it only works if access is universal and your IT Team allows Excel Add-in by default.   Installing the manifest file in a Sharepoint folder This is perhaps the most efficient option for organizations in which not all intended users have access to one network drive. However, it does require Admin rights, which will likely require your organization's IT Team. Additionally, Curinos has not been able to internally test this method due to our internal restrictions. If your organization requires Admin rights to allow Excel Add-ins, refer to the Deploy an Office Add-in using the admin center instructions that Microsoft provides.   Using an Admin-managed approach to the manifest file This is perhaps the most logical approach if your IT Team blocks Excel Add-ins for security reasons. 1.    If the Admin lead for LendersBenchmarkers Analyzer has not already received the manifest file: Email clientservices@curinos.com and request the manifest file from Curinos. 2.    Forward the manifest file to your IT Team. 3.    Request the IT Team to allow Excel Add-ins - refer to the Deploy an Office Add-in using the admin center instructions that Microsoft provides. The Office Add-in pane should be displayed on the Insert tab in Excel:   Setup FAQs for Admin/IT Team Your IT Team may have questions. Some of these might be:   How does this work? What is in the manifest file on the shared network folder?   While all data as well as the CurinosConnect UI are hosted and secured at Curinos, each organization will need to place a small, non-executable file on a team shared network folder and each user will need to install the Excel Add-in. Microsoft refers to the small file as a 'manifest' file. For those interested in more information about the purpose and contents of the manifest file, see some excerpts from Microsoft's help documentation below (edited in some cases for clarity). The XML manifest file of an Office Add-in details the mechanisms that allow your add-in to be activated when a user installs and uses it with Office documents and applications. An XML manifest file enables an Office Add-in to do the following: Describe itself by providing a name, description, version number, etc. Link to the URL for the image used in the Office app ribbon. Specify how the add-in integrates with Office, including the URL for any custom UI. Specify the default on-screen size of the add-in. Declare permissions that the Office Add-in requires, such as reading or writing to the document. To review the full text of Microsoft's details on the manifest file: https://docs.microsoft.com/en-us/office/dev/add-ins/develop/add-in-manifests?tabs=tabid-1

Your IT Team may have questions. Some of these might be:

Is this add-in developed by an internal team/developer or a third party vendor?

This Add-in (CurinosConnect) is developed internally by an approved vendor (Curinos).

How is the add-in updated?

The Add-in just provides access to a web app which is hosted on the Curinos.com domain. When we make updates to the web app, the add-in is updated automatically.

Who is responsible for add-in updates?

Curinos. Specifically, Bharat Nallamothu, Systems Architect at Curinos.

Who is responsible for support of the custom add-in (vendor/internal team/etc.)?

Curinos’ Client Services team.

What permissions, if any, does the add-in require?

The add-in displays a web app which is password protected. Only users that have accounts on your Cuirinos application can access the add-in.

Does the add-in handle Personal Identifiable Information for European colleagues?

No

Has the add-in been tested for weaknesses in code?

Yes!

Once the Bank’s IT Team has made the changes below, you should see it when you go to Excel > Insert > Get Add-ins > Admin Managed