This site is trying to open Draftable. http://localhost:4764 wants to open this application.This is standard browser security behaviour for any application launched from a web page, and it is not a fault in Draftable Legal. Selecting Open proceeds normally, and ticking Always allow suppresses the prompt, but only for that one user in that one browser profile. This article covers how to pre-approve the launch centrally, so the prompt never appears for your users. It is intended for administrators who can deploy browser policy through Group Policy, Microsoft Intune, or another management tool.
This is browser and iManage configuration, not Draftable configuration. The settings below belong to Microsoft Edge, Google Chrome, Microsoft’s WebView2 component and iManage. They cannot be applied from inside Draftable Legal or from the Draftable installer. Microsoft and iManage remain the authority on their own settings, so use their documentation if you need to confirm behaviour for a specific version.
Choosing which settings you need
Which setting applies depends on where your users start comparisons, because the embedded iManage Work Panel in Outlook is not the same browser as Microsoft Edge, even though it uses Microsoft’s browser engine.
If your users work in more than one of these, deploy each of the relevant settings. The Work Panel settings are commonly needed alongside the browser setting, and organisations that standardise on Chrome still need the WebView2 setting for the Work Panel.
Microsoft Edge
Deploy theAutoLaunchProtocolsFromOrigins policy.
Google Chrome
Chrome uses the same policy name and the same value, under its own key.If you changed the communication port. The origin must match the port Draftable actually uses.
4764 is the default. If your deployment uses a different port, substitute it here as well as in your iManage configuration.The iManage Work Panel in Outlook
The iManage Work Panel embedded in Outlook is rendered with Microsoft’s WebView2 component rather than the Edge browser. WebView2 does not inherit the full set of Microsoft Edge browser policies, so the Edge setting above cannot be relied on to cover the Work Panel by itself. In practice, configure the Edge setting as well as both of the settings below, even if Google Chrome is your organisation’s standard browser.WebView2
As documented by iManage for launching custom protocols from the Work Panel, create aURLAllowlist key and add the protocol as a value name.
This one is defined by iManage, so confirm it against their documentation for your version. The key sits under Microsoft’s WebView2 policy path but the instruction to populate it this way comes from iManage’s own guidance for launching custom protocols from the Work Panel, and the expected format has differed between client versions. If the prompt persists after applying it, ask iManage support to confirm the exact key, value name and data for your iManage Work Desktop version.
iManage Work Panel
iManage also maintains its own list of protocols the Work Panel is permitted to launch.Which hive to use depends on how iManage was installed. iManage stores Work Panel configuration per user, so for a per-user iManage installation this key is found under the user’s hive rather than under
HKEY_LOCAL_MACHINE. To deploy it across a fleet, target the user hive through Group Policy Preferences under User Configuration, Intune, or a sign-in script, so it applies to each profile including new ones. For a machine-wide iManage installation, use HKEY_LOCAL_MACHINE.This key belongs to iManage, and it requires iManage Work Desktop 10.9 or later. The expected data format has varied between client versions, and some versions expect the scheme written with a trailing wildcard, such as draftable:*, or expect a numbered list of values rather than a single one. If draftable on its own does not take effect, confirm the exact format with iManage support for your client version before experimenting further.Applying and confirming the settings
1
Deploy the settings
Apply the settings relevant to your environment through Group Policy, Intune or your management tool.
2
Restart the affected applications
Close and reopen the browser completely. For the Work Panel, close and reopen both Outlook and iManage Work Desktop. Restarting the machine is the most reliable way to be certain the policy has been reloaded.
3
Confirm the browser policy applied
In Microsoft Edge, open
edge://policy. Confirm that AutoLaunchProtocolsFromOrigins is listed and shows no error. In Google Chrome, use chrome://policy. If the policy is absent, the browser has not picked it up. If it is listed with an error, the value data is not valid JSON: check the quotation marks.4
Test as a standard user
Start a comparison from your document management system using a normal user account. Draftable Legal should open without a prompt.

