| Also use FileCap for internal domains | If this option is enabled, FileCap will also be used for internal domains. |
| Use FileCap for all attachments | Send all files added to the email with FileCap |
| Automatically send with FileCap when attachment size exceeds (MB) | Specify the threshold value in MB when the FileCap Outlook plugin will start sending the email with FileCap. Example: 3 means that if all added attachments are collectively larger than 3MB the email will be automatically sent with FileCap. |
| Send upload notification to sender | If this option is enabled, the send will receive a notification that the files were successfully sent using the FileCap Outlook plugin. This notification will also contain a link to block the transer. |
| Restore original mail item after sending | If this option is enabled, the original email and attachments will be restored to the Outlook Sent Items folder. |
| Create folder for restored items | If this option is enabled, a folder will be created where the original emails will be placed. |
| Put restore folder inside sent items | The recovery folder will be placed in the sent items folder if this option is enabled. |
| Restore folder name | Determine the name of the folder to be created here. |
| Days to store cached files | Cached files are files that have been added to the FileCap Web plugin, but where the email has still been sent. The number of days set here is the maximum number that these files will be kept on the FileCap server until the original email is sent. When the email is sent these files will automatically be moved to the associated transfer and available for the set days belonging to the transfer. |
| Add the option to generate a FileCap link before sending the mail | This feature allows users to generate a link and paste it into their email messages, preserving the formatting of the message. This makes it easier to include links in emails while maintaining the visual representation of the content. |
You can download the manifest file from the FileCap management portal, as explained in the documentation. This manifest file is required for the rollout of the add-in in Exchange/Office365.
Select the correct application and enter the email address to which the FileCap App configuration should be sent. With the email received, the FileCap Apps can be configured automatically.
| API Key | The API key consists of a string of 30 characters consisting of uppercase letters and numbers. It usually does not need to be changed. Important: Do not change the API key if applications are already using the current API key. Changing the API key will prevent these applications from connecting to the FileCap server until they are reconfigured. |
| API registration required | If this option is enabled, the API key cannot be used until the user's email address is verified. This is done automatically by email when using the FileCap plugins. This prevents the user from using an email address of a person they do not have access to. |
| Explanation | What is registration of the add-in? When registering the Outlook add-in, a unique code is generated by the FileCap environment per user and is provided once to the user at his/her email address. This process is initiated by the user when they open the FileCap add-in for the first time. A "Register" button will appear and when the user clicks it, they will receive an email with a code. This code must be entered into the add-in to complete the registration. After this, the add-in can be used as usual. Outlook add-in registration By default, when rolling out and using the FileCap Outlook add-in, users do not need to register the add-in. This makes a rollout of add-ins easy and can be installed all at once, for example via Intune or SCCM, for the entire organization, and everyone can use FileCap immediately. However, it is important to know what registration of the add-in is desirable or even necessary for a number of scenarios. These scenarios are explained below. Security When registration is not enabled, a user can directly use FileCap without first authenticating themselves to the FileCap environment. This makes it possible, for technically savvy users, to send FileCap e-mail on behalf of other individuals within an organization. This is not easy and when done, it is willful and possibly even punishable or in violation of company rules. However, it is possible because the add-in is not associated with a specific user. Loss of use of the Outlook address book due to FileCap When no registration has taken place, it is not possible to use the Outlook address book in conjunction with FileCap. This is because the FileCap add-in is not linked to an e-mail account and therefore cannot retrieve and use contacts or retrieve cell phone numbers from the address book of recipients who have previously received a message. Specifically, this means that users without registration will have to manually enter e-mail addresses and, when using SMS authentication, cell phone numbers into the add-in each time, and these are not stored in the add-in or address book. Existing installations with or without registration When registration was first required within a FileCap environment and then disabled, some users whose registration was already done may be able to use the address book and new users without registration may not. Conversely, if registration was not required and is subsequently made mandatory, then users are faced with a registration request when opening FileCap within Outlook. In this type of exception situation, it is important to communicate clearly with users to avoid unexpected behavior and ambiguities. |
