Target
This article is intended for administrators who perform initial setup and operational management of HENNGE Email DLP.
Purpose
This article explains the columns (items) for address group settings.
By using a configuration file, you can register and update HENNGE Email DLP settings in bulk.
Please refer to the following article for instructions on creating and importing configuration files.
Creating import data (Setting file) for HENNGE Email DLP
Notes
1. The content of this article is based on the product specifications as of May 2024 and may be subject to change without notice.
2. Administrator privileges for HENNGE Email DLP are required to confirm actual screens and make changes to settings.
Please refer to the following article for setting up or changing administrators.
Setup/ Change HENNGE Email DLP Administrators
3. The URL of the HENNGE Email DLP management screen varies depending on your tenant.
Access URL example: https://console.mo.hdems.com/#/admin/[Main Domain]
Content
- File formats supported are YAML and JSON.
- The unique key is "name" (address group name).
- In the case of "overwrite", the information corresponding to the above unique key will be completely overwritten.
If you are adding one person to an existing address group, be sure to include other addresses registered in the address group in the import data.
Columns
Column | Description |
version |
Specify 1. (Fixed value) |
address_groups |
Create the address groups specified in the following lines. |
address_groups_sync |
Create the address groups specified in the following lines by synchronizing with Google Workspace / Microsoft 365 groups. |
name |
Specify the address group name. |
addresses |
Specify email addresses in the following lines. |
address |
Specify the email addresses belonging to the address group. (Example: '@hennge.com') |
approver |
If the address above is to be designated as an approver, specify true. |
Examples
Create "Group requiring approval", "Normal sending group", and "Non-encrypted recipients".
YAML format
version: 1
address_groups:
- name: Group requiring approval
addresses:
- address: user1@sample.hennge.one
- address: approvar1@sample.hennge.one
approver: true
- address: user2@sample.hennge.one
- name: Normal sending group
addresses:
- address: user3@sample.hennge.one
- name: Non-encrypted recipients
addresses:
- address: '@gaibu.hennge.one'
- address: .gaibu.hennge.one
JSON format
{
"version": 1,
"address_groups": [
{
"name": "Group requiring approval",
"addresses": [
{
"address": "user1@sample.hennge.one"
},
{
"address": "approvar1@sample.hennge.one",
"approver": true
},
{
"address": "user2@sample.hennge.one"
}
]
},
{
"name": "Normal sending group",
"addresses": [
{
"address": "user3@sample.hennge.one"
}
]
},
{
"name": "Non-encrypted recipients",
"addresses": [
{
"address": "@gaibu.hennge.one"
},
{
"address": ".gaibu.hennge.one"
}
]
}
]
}
Create and synchronize "Distribution Group A" and "Security Group B"
YAML format
version: 1
address_groups: []
address_groups_sync:
- name: Distribution Group A
- name: Security Group B
JSON format
{
"version": 1,
"address_groups": [],
"address_groups_sync": [
{
"name": "Distribution Group A"
},
{
"name": "Security Group B"
}
]
}
※Pre-configuration is required for group synchronization with Google Workspace / Microsoft 365. (For Google Workspace For Microsoft 365)
Also, since you cannot edit synchronized address groups, they cannot be used for the approval function.