Preventing Clients from Saving Documents Locally in WPS on Windows FAQ

This FAQ focuses on policy activation, temporary exceptions, and control boundaries for preventing clients from saving documents locally in WPS on Windows, with 3 common questions and a glossary.

FAQ

What happens when a user clicks Save As after the policy is enabled?

1. After the administrator turns on the policy, the user opens a cloud document in the WPS client.
2. When the user tries to use Save As, the related button becomes unavailable.
3. If you need to confirm whether the policy is active, ask the administrator to check whether the user is within the current control scope.

How can I allow a temporary exception in an urgent case?

1. The administrator opens the admin console.
2. Go to Security Control → Document Security → Prevent Clients from Saving Documents Locally in WPS365.
3. Temporarily turn off the policy, or add the specified user to the control whitelist.
4. After the task is completed, restore the original policy as needed.

Why can some members still save documents locally?

1. Check whether the member is outside the current control scope.
2. Check whether the member has been added to the control whitelist.
3. Confirm that the administrator saved the policy and that the client stayed online to sync the latest settings.

Glossary