How Email Notifications Work

Email notifications inform users of events in the system.

When an event occurs, CA ControlMinder Enterprise Management checks if an email notification is enabled for the event.
If an email notification is enabled, CA ControlMinder Enterprise Management looks in the appropriate subdirectory for the event type.
For example, if an email is to be sent for the approval of a privileged account request, CA ControlMinder Enterprise Management looks in the Approved subdirectory.
CA ControlMinder Enterprise Management checks the subdirectory for an email template with the same name as the event, and does one of the following:
- If an email template exists with the same name as the event, CA ControlMinder Enterprise Management sends that email template to the recipients.
- If an email template with the same name as the event does not exist, CA ControlMinder Enterprise Management sends the defaultEvent.tmpl email template to the recipients.

Example

The following use case is an example of events and of notifications that are sent for them.

A user requests to use an account next Tuesday. An email is sent to the approver to let her know she has a request in her worklist.
A CreatePrivilegedAccountExceptionNotStartedEvent notification is sent to the 'pending' folder.
The approver approves the request. The user receives an email to inform him that the request was approved.
A CreatePrivilegedAccountExceptionNotStartedEvent notification is sent to the 'approved' folder.
On Tuesday the account becomes available to the user. The user receives an email to inform him that he can start working with the account.
A CreatePrivilegedAccountExceptionEvent notification is sent to the 'completed' folder.
Tuesday is over and the account is no longer available to the user. The user receives an email to inform him that he no longer has access to the account.
A DeletePrivilegedAccountExceptionEvent is sent to the 'completed' folder.

The most commonly used events are:

BreakGlassCheckOutAccountEvent: Sends a notification to the approver when a privileged account performs a Break Glass action.
CheckOutAccountPasswordEvent: Sends a notification to the approver every time a password is checked out.
CreatePrivilegedAccountExceptionEvent: Sends a notification to the requestor if an account is available. If you want to enable notification for this event, edit the template in the “completed” folder.
CreatePrivilegedAccountExceptionNotStartedEvent: Sends a notification to the approver that a request for access to a privileged account is pending in his worklist. Sends notifications to the requestor when the request is approved, rejected, or completed.