> ## Documentation Index
> Fetch the complete documentation index at: https://help.draftable.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Allowing Draftable to launch from your browser and the iManage Work Panel

> How to stop the browser confirmation prompt that appears each time a comparison is started from a web-based document management system, using Microsoft Edge, Google Chrome, WebView2 and iManage policy settings.

When a user starts a comparison from a web interface such as iManage, SharePoint Online or NetDocuments, the browser asks for confirmation before opening Draftable Legal:

> **This site is trying to open Draftable.** [http://localhost:4764](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.

<Note>
  **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.
</Note>

<Warning>
  **These settings only suppress the prompt.** They cannot make a comparison work if the `draftable://` URL scheme is not registered on the machine in the first place. If your users see nothing at all when they select a compare action, rather than a prompt they can accept, the cause is different: see [Draftable does not launch from iManage, SharePoint or File Explorer](/hc/en-us/articles/Draftable-does-not-launch-from-iManage-SharePoint-or-File-Explorer).
</Warning>

## 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.

| Where users start comparisons                                     | Setting to deploy                      |
| :---------------------------------------------------------------- | :------------------------------------- |
| iManage, SharePoint or NetDocuments in the Microsoft Edge browser | Edge, below                            |
| The same, in Google Chrome                                        | Chrome, below                          |
| The iManage Work Panel embedded in Outlook                        | WebView2 and iManage Work Panel, below |

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 the `AutoLaunchProtocolsFromOrigins` policy.

```bash theme={null}
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge
Value name: AutoLaunchProtocolsFromOrigins
Value type: REG_SZ
Value data: [{"allowed_origins":["http://localhost:4764"],"protocol":"draftable"}]
```

If you manage browsers with the Edge administrative templates, the same setting is available as **Define a list of protocols that can launch an external application from listed origins without prompting the user**, under **Administrative Templates** > **Microsoft Edge**. Using the template is usually tidier than deploying the raw registry value.

## Google Chrome

Chrome uses the same policy name and the same value, under its own key.

```bash theme={null}
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome
Value name: AutoLaunchProtocolsFromOrigins
Value type: REG_SZ
Value data: [{"allowed_origins":["http://localhost:4764"],"protocol":"draftable"}]
```

<Warning>
  **The value is read as JSON, so the punctuation matters.** The origin must be wrapped in double quotes exactly as shown. If the quotation marks around `"http://localhost:4764"` are missing, the whole entry is invalid, the browser discards the policy without reporting an error, and the prompt continues to appear as though nothing had been configured.

  Use `http://`, not `https://`. Draftable's local listener is reached over `http` on the loopback address.
</Warning>

<Note>
  **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.
</Note>

## 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 a `URLAllowlist` key and add the protocol as a value name.

```bash theme={null}
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Edge\WebView2\URLAllowlist
Value name: draftable
Value type: REG_SZ
Value data: (leave empty)
```

The value name is the protocol prefix on its own, without a colon or slashes.

<Note>
  **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.
</Note>

### iManage Work Panel

iManage also maintains its own list of protocols the Work Panel is permitted to launch.

```bash theme={null}
Key: Software\iManage\Work\10.0\EMM\WorkPane
Value name: AllowedCustomProtocols
Value type: REG_SZ
Value data: draftable
```

<Note>
  **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.
</Note>

## Applying and confirming the settings

<Steps>
  <Step title="Deploy the settings">
    Apply the settings relevant to your environment through Group Policy, Intune or your management tool.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>

  <Step title="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.
  </Step>
</Steps>

## Troubleshooting

| Symptom                                                 | What to check                                                                                                                                                                                                                                                                                                        |
| :------------------------------------------------------ | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The prompt still appears in the browser                 | Confirm the policy is listed without error at `edge://policy` or `chrome://policy`, and that the value data quotes the origin exactly as shown                                                                                                                                                                       |
| The prompt still appears only in the iManage Work Panel | The Edge browser setting alone does not cover the Work Panel. Confirm both the WebView2 and iManage Work Panel settings are present, and that iManage Work Desktop is version 10.9 or later. Because the Work Panel is an iManage component, iManage support can confirm the expected values for your client version |
| The policy is not listed in `edge://policy` at all      | The browser has not been fully restarted, or the value was written to the wrong hive. Machine-wide policy belongs under `HKEY_LOCAL_MACHINE`                                                                                                                                                                         |
| Nothing happens instead of a prompt                     | The URL scheme is not registered. See [Draftable does not launch from iManage, SharePoint or File Explorer](/hc/en-us/articles/Draftable-does-not-launch-from-iManage-SharePoint-or-File-Explorer)                                                                                                                   |
| Comparisons launch but documents fail to load           | The launch is working. This is a document management system connection problem, not a browser one                                                                                                                                                                                                                    |

## Related articles

* [Draftable does not launch from iManage, SharePoint or File Explorer](/hc/en-us/articles/Draftable-does-not-launch-from-iManage-SharePoint-or-File-Explorer)
* [Configuring iManage to be able to launch comparisons directly from within iManage](/hc/en-us/articles/22860371094681-Configuring-iManage-to-be-able-to-launch-comparisons-directly-from-within-iManage)
* [Launching comparisons from within iManage](/hc/en-us/articles/22873285776409-Launching-comparisons-from-within-iManage)
* [Deploying Draftable Legal with Microsoft Configuration Manager (SCCM)](/hc/en-us/articles/Deploying-Draftable-Legal-with-Microsoft-Configuration-Manager-SCCM)