A Campaign operator has left the organization and no longer requires access to Adobe Campaign Classic. The operator's account has been disabled but is still receiving alerts and notifications from the Campaign. What should the developer do to stop sending Campaign notifications to the operator?

Disabling an operator's account in Adobe Campaign Classic only revokes their login privileges. The operator's profile, which includes their email address and group memberships, remains active within the system's database. System alerts and notifications configured to be sent to specific operators or operator groups (e.g., 'Administrators') will continue to be sent to the email address on the disabled profile. The only definitive way to stop all platform-related communications and fully offboard the user is to permanently delete their operator profile from the instance.

A. Removing the email address from their profile is an incomplete solution that leaves an unnecessary and orphaned operator record in the system.
C. Updating access settings only modifies the operator's permissions within the platform; it does not control system-generated notifications sent to their email address.

1. Adobe Experience League, Campaign Classic v7 Documentation, "Creating an operator and setting permissions." This document details the operator configuration options, including the "Disable account" checkbox. It clarifies that this action is for suspending access, not for complete removal. The operator entity itself continues to exist. (See section on operator parameters).

2. Adobe Experience League, Campaign Classic v7 Documentation, "List of operators." This guide illustrates the process of managing operators, including the "Delete" action. Deleting an operator is the procedure for permanent removal from the system, which is necessary to sever all ties, including notification subscriptions.

3. Adobe Experience League, Campaign Classic v7 Documentation, "Alerts" (within Workflow general operation). This section explains how alerts can be configured to notify operators in case of errors. It states, "The alert can be sent to the workflow supervisor... or to one or more other operators." This confirms that notifications are tied to the existence of an operator record, not its enabled/disabled login status.