Group membership information can be used to distribute different email signatures to user groups. This is helpful when your data source lacks sufficient or updated information to segment users through field data.
Create the Groups Field in Xink
- Go to Preferences > Fields and click the + button.
- Add the property name
groupCnList
.
Xink accounts created after February 2018 include the Groups field by default.
Read Groups from Entra ID (formerly Azure Active Directory)
Submit a support ticket to enable group membership sync from Azure AD.
Example group memberships output:
Read Groups from On-Premises Active Directory
If your account was created before February 2018, download the latest version of the ADExport tool from your Xink portal.
By default, the tool does not export group memberships. Add the /ug
switch at the end of your command line to include them.
Examples
Export all Active Directory users and their group memberships:
C:\emsadexport.exe /secret:"INSERT-YOUR-SECRET-TOKEN" /ug
Export users from a specific Active Directory group:
C:\emsadexport.exe /secret:"INSERT-YOUR-SECRET-TOKEN" /group:"My Test" /remove+ /ug
To verify that group memberships are being exported correctly, check for the groupCnList
value in user records.
Learn more from Example #7 in this article.
If you receive[]
as a result, it's likely due to the use of the/domain:
switch, which is not compatible with/ug
.
Create a Rule to Target Group Membership
To assign signatures based on group membership, go to Preferences > Rules. Create a rule that checks the Groups field:
Best practice: Avoid adding extra conditions. Use one rule per group for easier maintenance.
Use the up/down rule order controls to define execution priority. The first matched rule will apply.