Skip to main content

Conditional Policy - Recipient Menu Guide

※ Last updated: 2025-09-08

The conditional policies of SHIELD Mail are managed by distinguishing between sender policies and recipient policies based on the direction of mail flow (routing).

This is to clearly distinguish the document distribution paths before the conditional policy is applied, enabling more precise and predictable security controls.

Reason for Policy Separation

  • Separate processing logic based on the direction of mail flow before applying conditional policy.
  • Easily manage policy conflicts and policy priority through sender/receiver distinction.

Mail Routing Criteria

  • Transmission: SOFTCAMP Mail Server → SHIELD Mail → External Mail Server
  • Receiving: External Mail Server → SHIELD Mail → SOFTCAMP Mail Server

This guide explains how to configure sender policies and recipient policies separately in the conditional policy management menu within the admin page.

1. Entering the Conditional Policy Menu​

Settings > Conditional Policies > RecipientsYou can access the policy management screen from the menu.

sender

Policy List Table Structure​

  • **Priority:**It indicates the order of execution of the policy.
  • **Policy Name:**This is the unique name of the policy.
  • **Description:**The purpose of the policy or a brief description.
  • **Members:**Specifies the users, groups, or policy groups to which the policy applies.
  • **Target document:**Types of documents to which the policy applies (General Documents, DRM, AIP)
  • **Condition:**Sender/Receiver conditions. (e.g:softcamp.co.kr, user@softcamp.co.kr)
  • **Approval Process:**Specifies whether approval is granted.
  • **Document Execution Policy:**This is the document processing method applied in the policy.
  • **Last modified date:**This is the date when the policy was last modified.

2. How to Register Recipient Conditional Policies​

policy

1. Policy Registration​

Click the [Register Policy] button to enter the policy creation screen.

2. Enter Basic Policy Information​

  • Policy Name *(required)*Enter the unique name of the policy.
  • Policy DescriptionYou can enter the purpose of the policy or a brief description.
  • Member Designation (required) :
    • Select the user or group to which the policy will be applied.
    • Can be specified as [All Users], specific users, groups, or policy groups.
  • Specify attached file (target document type) (required) :
    • Select the document type to which the conditional policy will be applied.
    • Multiple selection available(e.g., general document + DRM document)
    • The selectable document types and supported extensions are as follows:
Document TypeDescriptionSupported Extensions
General DocumentUnencrypted plaintext documentdoc,docx,docm,xls,xlsx,xlsb,xlsm,ppt,pptx,pps,ppsx,pptm,pdf,hwp,hwpx
DRM DocumentDocument Security (DS) based DRM applied documentdoc,docx,docm,xls,xlsx,xlsb,xlsm,ppt,pptx,pps,ppsx,pptm,pdf,hwp,hwpx
AIP DocumentDocuments based on Microsoft Azure Information Protectiondoc,docx,docm,xls,xlsx,xlsb,xlsm,ppt,pptx,pps,ppsx,pptm,pdf

hwp, hwpxin AIP,Not supportedBe careful.

3. Setting Conditions​

  • Condition items areSender Conditions, Receiver Conditions, Approval Processis composed of.
  • Sender Conditions
    • No Limit
    • Specify a specific domain (softcamp.co.kr)
    • Specify a specific email (admin@softcamp.co.kr)
  • Recipient Conditions
    • No Limit
    • Specify a specific domain (gmail.com)
    • Specify a specific email (user@gmail.com)
  • Approval Process
    • Set to require approval from designated approvers before sending.
    • OFF: The existing policy will be implemented immediately.
    • ON: Sends upon completion of approval by calling the approval service API, and blocks in case of rejection.
    • Usage Example:
      • Approval from the security officer is required before sending important confidential documents.
      • Control of the sending process by designating approvers by department
  • The method for entering sender/recipient conditions supports direct input, domain input, and CSV upload.
  • Note: This applies to all external emails if there are no conditions.

4. Document Execution Policy Settings​

  • Select the actual document processing method to apply based on the conditions.
  • Selectable Policies:
    • Send as is
    • Send after document conversion(DRM, AIP, etc.)
    • Sending after decryption
    • Send after removing the attached document
    • Blocking Email Sending

5. Enable Policy​

  • You can set the usage and validity period of the policy.
  • Usage statusYou can set the activation or deactivation of the policy through the toggle button.
  • Expiration Date: You can specify a start date and an expiration date, and the expiration date will무기한You can also set it to.

6. Save and Complete​

  • Once all settings are complete저장Button Click
  • Registered in the policy list, and thereafterEdit/Deletepossible

Edit Recipient Conditional Policy​

  • You can click on the policy you want to edit from the policy list to change the detailed settings.
  • When changing the order of policies, the priority is reset.

Cautions​

  • For DRM and AIP documents, you need to check and set the list of convertible file extensions.
  • HWP, HWPXThe AIP conversion is not supported for this file extension.
  • Items with higher priority in the policy will be executed first.

Usage Examples​

  • Automatically convert general documents received via email into DRM documents operated within the company to enhance security strength.

Scheduled for update.