Skip to main content
Skip table of contents

Launching local applications from Workspace 365

Launching local applications from Workspace 365

In order to enable local applications from the Workspace, please follow these steps:

  1. A protocol must be created in the Windows registry for every application. In this case,   Notepad will be the example application. We start with a .txt file named “Notepad protocol.txt”.


Windows Registry Editor Version 5.00
"URL Protocol"=""


Note: Notepad is an example application. If another application is desired, the name “Notepad” should be changed to the name of the desired application. The path of the .exe file should match the exact path of that application (see the last line in the example above) on your local disk.

In case the local application is going to be an Office application, the name of the Office application in the Registry Key has to differ from the original Office application name. For example:

Windows Registry Editor Version 5.00
"URL Protocol"=""
@="\"C:\\Program Files (x86)\\Microsoft Office\\Office15\\EXCEL.exe\""

Use this application name also at step 11! For example: ExcelApp:open

Tip: If you need to start an application with agruments try using a .bat file. It might be required to link to the .bat file through a shortcut.


  1. The .txt extension of the file must be changed to .reg

  2. Open regedit.exe and import the .reg file in the register

  3. Now login to Workspace 365 with your credentials

  4. Click “ Add new apps”

  5. Select the “Shortcut” app and click “Add to workspace”

  6. The selected app is added to the overview. Now click “Edit your workspace”

  7. Select the “Shortcut” app

  8. Click “Edit app”

  9. Fill in the app name of your choice

  10. Fill in the following at the Webpage field: ”[Applicationname]:open”*[Applicationname]: the actual name of the application, in this case:Notepad:open

  11. Click “Done”

  12. The local application will now be opened by clicking the created “Shortcut” app

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.