To configure the Outlook Add-in for your environment, search for it on the Global Feature administration page of Modeller > Global features > All global features.
Outlook Add-in configuration checks
The Search Scope, Work Types, and Content Security Policy should be automatically configured, and checks should confirm that the configuration is correct. If issues are found for any of these checks, use the information below to correct them and click the revalidate button to check again.
Enable or disable the Outlook Add-in system-wide using the Enabled check box at the bottom of the feature card.

The Add-in itself verifies that the Global Feature is enabled and if not, shows an error message:

Click the gear icon to open the configuration blade.

Whenever you change the configuration, click the Revalidate button at the top of the blade for the blade to refresh. It may be necessary to clear the cache before revalidating for config changes to take effect.
Settings
This controls how the add-in behaves when users compose outgoing emails.
Tag-only mode for outgoing emails
- When this setting is On, users cannot file an email they are currently drafting. The add-in only allows them to insert a tag into the subject line. Use this setting where a monitored inbox files sent items automatically.
- When the setting is Off, users file a draft email directly from the compose window.
Search Scope
The system is preconfigured with the necessary search scope for work items that are available for email filing within the add-in. This aspect of the Outlook Feature checks whether the search scope configuration has any issues.
The default work types in the Work type search filter are:
- Client Contract
- Instruction
- Matter
- Proceedings
- Statement of Work
Work Types
The Outlook Add-in requires work type relationships to be in place to file inbound and outbound emails. If these relationships are not correctly configured, you will be notified in this aspect. To correct the relationship settings do the following:
Click View Type Relationships to open the Type Relationships page for the Inbound Email work type. Then use the buttons on the top right to configure a ‘related’ link between the Inbound Email work type in the Search Scope configuration:
- Client Contract
- Instruction
- Matter
- Proceedings
- Statement of Work
Content Security Policy
The Outlook Add-in requires that Office 365 URLs be added to the Allowed frame-ancestor origins text box. The help text from the Content Security Policy blade is shown here:
Frame ancestors and the Office add-ins: If you are using the official Clio Operate Office add-ins via the appropriate web-based online application, you will need to allow certain O365 URLs to iframe the Clio Operate identity server. Without doing so, the login form will not be allowed to render within the online interface.

Identity Client
The Outlook Add-in requires an Identity Client to be configured in the system. This may have already been configured, but if there are issues with the configuration, you will be notified here.
If the sharedo-outlook-addin client is not in the list of identity servers found at Admin > Integrations > Manage Identity Servers, perform the following steps. Use the information in these steps to correct the configuration if problems are reported for an existing client.
- Click Add App in the ribbon and select Add authorisation code flow application.
- For the Client display and Client authentication sections, specify:
- Client name: ShareDo Outlook Add-In
- Logo URL: <Leave blank>
- Client info URL: <Leave blank>
- Client Id: sharedo-outlook-addin
- Client secret: <Click the randomise button>
- For the Tokens section, specify:
- Access token lifetime (seconds): 900
- Use reference tokens: ON
- Refresh token lifetime (seconds): 2592000, which is 30 days. This sets how long a user goes without using the add-in before they sign in again. Each time the add-in refreshes, the expiry moves forward by this period from that moment. An empty field applies one day. The screen displays a warning below 604800 seconds, which is seven days.
- Absolute Refresh token lifetime (seconds): leave empty. This sets the point at which a user signs in again regardless of how often they use the add-in, counted from when they first sign in. An empty field applies the identity server's own limit of 2592000 seconds, which is 30 days. Enter a value to set a shorter or longer limit, up to 31536000 seconds, which is 365 days. The screen rejects zero. Keep any value you enter above the refresh token lifetime.
- Refresh Token Usage: Reuse. The add-in keeps the same refresh token each time it asks for a new access token. Leave this setting on Reuse for the add-in client. The alternative, One time only, issues a new refresh token on every refresh and stops the previous one working. The add-in sends several requests at once, and once access has run out each refused request asks for a new token on its own, so under One time only all but the first are rejected and the user returns to the add-in's start screen.
- For the Reply URLs, specify the reply URL for each add-in host your users load:
- Production: https://outlook-addin.sharedo.co.uk/#/auth-reply
- Preproduction: https://outlook-addin-vnext.sharedo.co.uk/#/auth-reply
- For the CORS origins, specify the origin for each add-in host your users load:
- Production: https://outlook-addin.sharedo.co.uk
- Preproduction: https://outlook-addin-vnext.sharedo.co.uk
The CORS origins let the add-in call the Clio Operate APIs. Enter the address in lowercase, with no path. A trailing slash here does no harm, but leave it off so the entry matches the reply URL. Remove any test entries, such as a localhost address, from a live client, because CORS origins apply across all enabled clients and a leftover entry stays allowed for every one of them.
See PKCE authentication to enable on this client after saving.
- For Identity providers: leave Require user consent on, and turn on all the options in use for authentication in Clio Operate under Allow login for this client from
- Click Save
Confirm the configuration is complete
Each aspect of the feature reports its own result. When an aspect validates successfully, the blade displays a confirmation message and the actions available for that aspect.

Where an aspect reports an issue, the blade displays the detail of the problem in place of the confirmation. Correct the configuration using the guidance in the sections above, then revalidate.