---
title: Security Group Compliance Manager Connector_Events
slug: security-group-compliance-manager-connectorevents
docTags: 
createdAt: 2026-02-19T02:37:17.387Z
---

Connector\_Events define how Activate processes Security Group Compliance Manager compliance changes. When AD objects or group memberships are modified, Activate evaluates configured Connector\_Events based on resource mappings and workflow configuration.

# AD object changes (ADChangeHandler)

The ADChangeHandler processes changes to AD objects.

When the changed object is a group:

- If the group is mapped to a GroupResource in Activate, the Connector\_Events parameter on that GroupResource is evaluated.
- If no Connector\_Events parameter exists, or the group is not mapped to a GroupResource, events are sourced from the ChangeWorkflow under:
  - Resources → ActiveDirectory

If no workflow nodes are configured at this level, an exception is thrown.

# AD group membership changes (ADGroupMember)

The ADGroupMember handler processes changes to group membership.

Processing occurs sequentially in the following order:

1. If the group is mapped to a GroupResource, its Connector\_Events are processed.
2. If the member row usage flags include DistributionLists, the Connector\_Events on the DLResource are processed.
3. If the member row is mapped to a Service, the Connector\_Events on the Service are processed.

More than one set of Connector\_Events can execute for a single membership change. While supported, this configuration is not generally recommended.

# Commit behaviour

Connector\_Events processing determines whether a change is committed.

- If any processing stage actions the change, it is committed.
- If no processing stage actions the change, it remains pending.

# Configuration considerations

When designing AD compliance behaviour:

- Ensure GroupResource mappings are clearly defined.
- Confirm Connector\_Events are configured at the correct level (GroupResource, DLResource, or Service).
- Validate that the ActiveDirectory ChangeWorkflow contains appropriate nodes where required.

Clear separation of responsibility between resource mappings and workflow configuration helps ensure predictable compliance processing.