With the MS Office Native variant, Disclosure Management opens chapter files directly in the locally installed applications MS Word, MS Excel, and MS PowerPoint. MS Office does not download the file to the computer first, but opens it over HTTPS directly from the Disclosure Management server and saves changes back to the same place. For MS Office to open these files in edit mode instead of Protected View, the IT administrator adds the domain *.wopi.lucanet.cloud to the Trusted sites zone of MS Windows on all affected computers.

For this entry, you need a single setting that you deploy via Microsoft Intune, a Group Policy, or the registry to every computer on which users work with MS Office Native.

The entry is only required for the MS Office Native variant. You do not need it for MS Office for the Web and MS Office for Desktop. For more information, see MS Office Variants.

Go directly to the instructions for your deployment method:

MS Windows assigns every URL to a security zone. A host that is not listed in any zone belongs to the Internet zone, and MS Office treats a document from this zone as potentially unsafe. Without the entry for *.wopi.lucanet.cloud, this has the following consequences for users of MS Office Native in Disclosure Management:

  • Protected View or read-only: MS Office opens the document in Protected View with a yellow message bar or as read-only. Users have to click Enable Editing every time, and some functions are blocked until they do.
  • No save-back: In Protected View, MS Office does not write any changes back to the Disclosure Management server. Users who overlook the message bar can lose their changes.
  • Additional sign-in prompts: MS Office may ask for credentials or display an error message, although the file comes from a trusted business application.

With the entry *.wopi.lucanet.cloud in the Trusted sites zone, MS Windows and MS Office classify the Disclosure Management files as an internal business source. MS Office then opens the files directly in edit mode, just like a file on a company network share.

The entry for Disclosure Management has the following scope and security impact:

  • The entry only applies to HTTPS hosts under wopi.lucanet.cloud. Other domains and unencrypted HTTP connections are not affected.
  • Disclosure Management transfers all data to these hosts with TLS encryption. Each time a file is opened, Disclosure Management generates a new short-lived token, so that an earlier link to the same file no longer works.
  • The entry does not deactivate macro protection, virus scanners, or Microsoft Defender SmartScreen. It only removes the classification as a file from the Internet that triggers Protected View.

For Disclosure Management, add the following value to the Site to Zone Assignment List policy of MS Windows:

Value name (URL pattern)ValueMeaning
https://*.wopi.lucanet.cloud2Trusted sites zone

Note the following points for the Disclosure Management entry:

  • Use the wildcard: Enter the domain with the wildcard *. The host of your Disclosure Management environment is a subdomain of wopi.lucanet.cloud, and the wildcard also covers further hosts that Lucanet may add in the future.
  • Keep the https:// prefix: The prefix restricts the trust to encrypted connections.
  • Use zone 2: The value 2 stands for the Trusted sites zone. Do not use the value 1 for the Local intranet zone, because this zone has different default settings that are less suitable for cloud hosts.

To set up the trusted site for Disclosure Management via the Microsoft Intune settings catalog:

1

Create a policy: In the Microsoft Intune admin center, open Devices | Manage devices | Configuration and click Create and then New policy. Select Windows 10 and later as the platform and Settings catalog as the profile type.

2

Search for the setting: Click Add settings and search for Site to Zone Assignment List. The setting is located under Administrative Templates | Windows Components | Internet Explorer | Internet Control Panel | Security Page.

3

Select the device setting: Select the setting for the device, not the setting marked (User) (see section Device or user scope for the Disclosure Management entry).

4

Add the entry: Set the setting to Enabled and add a row with the following values:

  • Value name: https://*.wopi.lucanet.cloud
  • Value: 2
5

Assign the profile: Assign the profile to the device groups that work with Disclosure Management and save the profile.

The devices apply the setting at their next synchronization with Microsoft Intune. It may take up to 8 hours until the setting is effective on all devices. A restart or a manual synchronization under Settings | Accounts | Access work or school speeds this up.

To set up the trusted site for Disclosure Management via a Group Policy in an on-premises Active Directory environment:

1

Edit a Group Policy Object: Open the Group Policy Management Console and edit a Group Policy Object that is linked to the organizational units of the affected computers, or create a new Group Policy Object.

2

Open the policy: Go to Computer Configuration | Policies | Administrative Templates | Windows Components | Internet Explorer | Internet Control Panel | Security Page and open the Site to Zone Assignment List policy.

3

Add the entry: Set the policy to Enabled, click Show, and add an entry with the following values:

  • Value name: https://*.wopi.lucanet.cloud
  • Value: 2
4

Apply the policy: Execute gpupdate /force on a test computer or wait for the regular Group Policy refresh interval.

If you use neither Microsoft Intune nor Group Policies, set the values for Disclosure Management directly in the MS Windows registry with your software distribution tool. This method is also suitable for a single test computer. The Site to Zone Assignment List policy writes the same values.

To set up the trusted site for Disclosure Management in the registry:

  1. Create the following value for the zone assignment:

    text
        
      
  2. Also create the following value so that MS Windows applies the zone assignment list:

    text
        
      

The Site to Zone Assignment List policy exists twice in MS Windows: under Computer Configuration, which writes to HKEY_LOCAL_MACHINE, and under User Configuration, which writes to HKEY_CURRENT_USER. For Disclosure Management, Lucanet recommends the entry at device scope.

Many organizations enable the Security Zones: Use only machine settings policy, which sets the registry value Security_HKLM_only = 1, for example as part of a security baseline. When this policy is active, MS Windows ignores all zone assignments at user scope. An entry at user scope is then present in the registry but has no effect, and MS Office keeps opening the Disclosure Management files in Protected View.

An entry at device or computer scope works in both cases. Therefore, deploy the entry at device scope, regardless of whether your organization uses this policy.

To check on a computer that has received the policy whether the Disclosure Management entry is effective:

  1. Execute the following command in Windows PowerShell:

    powershell
        
      

    If the entry is effective, the command returns Trusted. If the command returns Internet, the policy has not reached the computer yet, or the entry is at user scope while the Security Zones: Use only machine settings policy is active (see section Device or user scope for the Disclosure Management entry).

  2. Check the registry with the following command:

    powershell
        
      

    The output must contain https://*.wopi.lucanet.cloud : 2.

Entries created by a policy do not appear in the Internet Properties dialog under Security | Trusted sites | Sites. You open this dialog via the Internet Options item in the Control Panel. The list under Sites only displays entries that a user added manually. When a policy manages the zone assignment, the Add button is also deactivated there. An empty list in this dialog therefore does not mean that the Disclosure Management entry is missing.

To test whether MS Office opens the Disclosure Management files in edit mode:

1

Check the MS Office variant: In Disclosure Management, make sure that the document uses the MS Office Native variant. You set the variant under Configure document | General Settings in the MS Office variant drop-down list (see section Activating the MS Office variant in Disclosure Management).

2

Open a chapter: In the Cockpit, open a chapter in MS Word (see section Opening Word Files in Disclosure Management).

3

Check the edit mode: MS Word opens the chapter directly in edit mode, without the yellow Protected View message bar and without a read-only notice in the title bar.

4

Check saving: Make a small change and save with Ctrl+S. MS Word writes the change back to the Disclosure Management server without displaying the Save As dialog.

The following table describes common problems with the Disclosure Management entry, their causes, and the matching solution:

ProblemPossible causeSolution
MS Office still opens the file in Protected View after the synchronization.The computer has not applied the policy yet.Restart the computer and execute the PowerShell check (see section Checking the Disclosure Management entry on a computer).
PowerShell returns Internet, the key under HKLM is empty, but HKCU\...\ZoneMapKey contains the entry.The entry is at user scope while the Security Zones: Use only machine settings policy is active.Deploy the entry again at device or computer scope.
The entry is present in the registry, but MS Word still opens the file in Protected View.MS Office was still running when the policy reached the computer.Close all MS Office applications, check in the Task Manager whether a WINWORD.EXE process is still running in the background, and open the file again.
The entry works for one user but not for another user on the same computer.The IT administrator deployed the entry only for individual users at user scope.Deploy the entry for all users at device scope.

If the problem persists after these checks, contact Lucanet Support or your Lucanet contact person and include the output of the two PowerShell commands.

This content was generated using AI and reviewed by Lucanet subject matter experts before publication.