When using Screen Capture Protection, common questions usually focus on scope, usage impact, and policy combinations; the following section includes 3 common Q&As and a glossary.
FAQ
Does enabling screen capture control block screenshots for all documents?
- Check the member scope in the current screen capture control policy.
- Confirm whether the relevant members are included in that policy.
- If members are outside the policy scope, they are generally not affected. Members outside the policy and admins are not restricted by that policy.
Will enabling screen capture control affect normal use?
- In controlled documents, system screenshot shortcuts and screenshot tools are disabled.
- Normal document viewing and processing can continue, but screenshot-related actions are restricted.
- Keep in mind that methods such as taking a photo with a phone cannot be fully prevented through technical controls.
Why is it recommended to use screen capture control together with other security policies?
- Screen capture control mainly reduces the risk of content being shared through screenshots.
- If you also need to limit other outbound paths such as copying or downloading, enable the related security policies at the same time.
- A combined setup is more suitable for covering multiple data leakage scenarios.
Glossary
| Term | Definition |
|---|---|
| Screen capture control policy | A rule that defines which members, product conditions, and platform types are affected by screenshot restrictions. |
| Member scope | The target range of members to whom a policy applies. |
| Screenshot permission | Whether members are allowed to take screenshots when a policy is matched. |