Suger

Email Notification

Enable and set up the email recipients to receive notification events from Suger service


Overview

Email notifications let you configure per-scope routing rules so that each notification event type has its own enable/disable toggle, recipient lists (TO, CC, BCC), and optional custom template. When an event from Suger matches an enabled scope, an email is automatically sent to the designated recipients.

Configuration

Enable Email Notification

Go to the settings page and open the Notification tab. Toggle the Enable Email Notification switch to activate email routing.

Email Routing Catalog

Once email notification is enabled, the Email Routing Configuration table displays all available notification scopes organized by category (Offers, Entitlements, Co-Sell, Workflows, etc.). Each category can be expanded or collapsed.

Every scope row provides the following columns:

ColumnDescription
TriggerToggle to enable or disable the notification scope. The scope name and its raw identifier are displayed.
TO RecipientsEmail addresses that receive the notification. Type an address and press Enter or comma to add.
CC RecipientsEmail addresses to CC on the notification.
BCC RecipientsEmail addresses to BCC on the notification.
TemplateSelect a custom email template from the dropdown, or choose + New Template to create one inline. When a template is assigned, icons appear to edit, view details, or delete it.
DiagnosticsClick Test to send a test email using the assigned template (requires a template to be selected).

Click Save after making changes to persist your configuration.

Email Routing Configuration table in Notification settings

Additional Settings

Below the routing catalog, two additional toggles are available:

  • Disable Email Notification on Offer Ready — Prevents sending email notifications when an offer is ready to accept.
  • Enable Expire Soon Offer Workflow Notification — Enables workflow notifications for offers that are about to expire. When enabled, you can configure the number of days before expiration to trigger the notification (default: 7 days).

Update History

The Update History table at the bottom of the Notification tab shows an audit log of configuration changes. You can search across all fields and click a row’s detail icon to inspect the full JSON payload of the change.

Custom Templates

Custom email templates allow you to personalize your notification emails with dynamic content and professional layouts. You can create templates that automatically incorporate data from your notification events, making your emails more informative and engaging.

Any scope can have a custom email template assigned to it, replacing the default content. Templates support dynamic variables (for example, buyer name, deal name, and product).

Create New Template

In the routing catalog, find the Template column for any scope row and select + New Template from the dropdown. The template creation dialog opens, and once saved the new template is automatically assigned to that scope.

New Template option in the Template column dropdown

In the template creation dialog:

  • Enter a descriptive name for your template
  • Select the evaluator type (currently, only Golang Template is supported)
  • Use the email builder to design your template
  • Click Create to save your template
Template creation dialog with the email builder

Use Email Builder

The email builder provides a comprehensive set of tools to create professional-looking emails:

  • Columns: It allows your users to add columns to your design in order to have a better design arrangement.
  • Button: Add any type of button in your email. You can change colors and styles.
  • Divider: It gives your users appropriate spacing at any point they want in their design.
  • Heading: Add headings (from level 1-6) to the design.
  • Text: Text is a built-in tool so users can add text to their designs.
  • Image: To make your emails attractive, you can add images using this tool.
  • Social: It is a built-in tool that lets users add their social media icons to your design.
  • Menu: Menu is a built-in tool used to create navigation menus.
  • HTML: This tool will give your users room to add custom HTML to the design.

Working with Dynamic Data

Using Single Variables
  1. Select a notification event type to make its variables available in the builder. By default, use the BaseNotificationEvent.

  2. In the text or heading tool, click the Merge Tags button and select the variable you want to insert

    Merge Tags button with variable selection list
Looping Over Lists

To display multiple items from a list:

  1. Add a Columns tool to your template
  2. Click the tag symbol on the Columns tool
    Tag icon button on the Columns tool
  3. Select the list you want to iterate over
    List selection dropdown for the Columns tool
  4. For complex objects in the list:
    • All variables from the list items become available within the Columns block
    • Use them in text tools just like single variables
    List item variables available inside the Columns block
  5. For simple values (strings or numbers):
    • Use the this merge tag to access the current item within the Columns block
    This merge tag for the current list item

Assign Templates to Notification Scopes

Templates are assigned directly in the Email Routing Catalog:

  1. Go to the settings page and open the Notification tab
  2. Find the scope you want to customize in the routing catalog
  3. In the Template column, select an existing template from the dropdown or choose + New Template to create one
  4. When a template is assigned, use the inline icons to:
    • Edit the template in the email builder
    • View details as a JSON payload
    • Delete the template (removes it from all scopes that reference it)
  5. Click Save to persist your changes

Test Custom Templates

Before using a template in production, you can test it to ensure it works as expected:

  1. In the routing catalog, find the scope row with the template you want to test
  2. Click the Test button in the Diagnostics column
  3. In the test dialog, provide the following information:
    • To Email: The recipient email address for the test
    • CC Emails: Optional comma-separated list of email addresses to CC
    • One event json data: Choose (and modify as you want) between:
  • Mock JSON data files
  • Last recorded events for your organization
Test dialog with recipient email and event JSON data

You can also edit the template directly from the test dialog by clicking the Edit Template button, which will open the email builder.

Notification Scope Reference

Each notification scope has its own trigger, its own TO/CC/BCC recipient lists, and an optional custom template that replaces the default content. Use the tables below to understand when each scope fires and what its default email contains.

Keep in mind:

  • Always-on scopesCreate Co-Sell, New Contact Added to Co-Sell, and Commission Terms Updated are always sent and cannot be disabled, so critical collaboration events always reach the right people.
  • Commission scopes — All commission scopes are enabled by default. You can configure custom recipients and templates for them, but they cannot be turned off.

Offers

ScopeWhen it firesDefault email content
Create Offer
CREATE.OFFER
A new private offer is created in your organizationOffer name, buyer, product, pricing, expiry date, link to the offer
Offer Creation Failed
CREATE_FAILED.OFFER
A private offer fails to be created on the cloud marketplaceFailure reason (the offer’s error details) and a link to the offer in the Suger console so your team can fix and resubmit
Accept Offer
ACCEPT.OFFER
A buyer accepts a private offerOffer name, buyer details, acceptance timestamp
Expire Offer
EXPIRE.OFFER
A private offer has passed its expiration date without being acceptedOffer name, buyer, expiry date
Update Offer
UPDATE.OFFER
An existing offer is modified (e.g. pricing, expiry, terms)Offer name, summary of what changed
Delete Offer
DELETE.OFFER
A private offer is deletedOffer name, deletion timestamp
Cancel Offer
CANCEL.OFFER
A private offer is cancelledOffer name, cancellation details
Submit Approval Request
SUBMIT_APPROVAL_REQUEST.OFFER
A team member submits an offer for internal approval reviewOffer details, submitter name, link for the approver to act
Review Approval Request
REVIEW_APPROVAL_REQUEST.OFFER
An offer approval request is ready for a reviewer to act onOffer details, approve/reject CTA
Pending Acceptance
PENDING_ACCEPTANCE.OFFER
An offer has been sent to the buyer and is awaiting their acceptanceMarketplace-specific template (AWS/Azure/GCP/Snowflake) with offer details and a direct acceptance link
Pending Partner Action
PENDING_PARTNER_ACTION.OFFER
An offer requires action from a channel partner (e.g. a CPPO step)Offer name, required action, link

Entitlements

ScopeWhen it firesDefault email content
Create Entitlement
CREATE.ENTITLEMENT
A buyer subscribes and a new entitlement is createdBuyer, product, subscription start date, pricing
Reinstate Entitlement
REINSTATE.ENTITLEMENT
A previously suspended or cancelled entitlement is reinstatedEntitlement name, buyer, reinstatement date
Suspend Entitlement
SUSPEND.ENTITLEMENT
An entitlement is suspended (typically due to a payment failure)Entitlement name, buyer, suspension reason, recommended next step
Pending Cancel Entitlement
PENDING_CANCEL.ENTITLEMENT
An entitlement has been scheduled for cancellationEntitlement name, buyer, scheduled cancellation date
Cancel Entitlement
CANCEL.ENTITLEMENT
An entitlement is fully cancelledEntitlement name, buyer, cancellation timestamp
Update Entitlement
UPDATE.ENTITLEMENT
An entitlement’s attributes are updated (e.g. seat count, pricing tier)Entitlement name, buyer, summary of changes
Meter Entitlement
METER.ENTITLEMENT
A usage metering record is submitted against an entitlementEntitlement name, buyer, metered dimension, reported usage amount
End Soon Entitlement
END_SOON.ENTITLEMENT
An entitlement is approaching its end dateEntitlement name, buyer, days until end date
Terminate Entitlement
TERMINATE.ENTITLEMENT
An entitlement is terminated (hard stop, distinct from cancellation)Entitlement name, buyer, termination date

Co-Sell

These scopes cover activity on co-sell referrals shared via cloud marketplace co-sell programs (AWS ACE, GCP, etc.).

ScopeWhen it firesDefault email content
Archive Referral
ARCHIVE.REFERRAL
A co-sell referral is archivedReferral name, cloud partner, archival timestamp
Reject Referral
REJECT.REFERRAL
A co-sell referral is rejected by the cloud partnerReferral name, cloud partner, rejection reason
Accept Referral
ACCEPT.REFERRAL
A co-sell referral is accepted by the cloud partnerReferral name, cloud partner, acceptance timestamp
Create Referral
CREATE.REFERRAL
A new co-sell referral is createdReferral name, cloud partner, deal details
Approve Referral
APPROVE.REFERRAL
A co-sell referral is approved internally before submission to the cloud partnerReferral name, approver, timestamp
Update Referral
UPDATE.REFERRAL
A co-sell referral is updated (e.g. deal value, stage, customer info)Referral name, summary of what changed
Pending Acceptance Referral
PENDING_ACCEPTANCE.REFERRAL
A co-sell referral has been submitted and is awaiting cloud partner acceptanceReferral name, cloud partner, submission timestamp
Inbound Referral
INBOUND.REFERRAL
A new inbound co-sell referral is received from the cloud partnerReferral name, cloud partner, customer details

Product

ScopeWhen it firesDefault email content
Create Product
CREATE.PRODUCT
A new product is created in your organizationProduct name, marketplace, creator
Update Product
UPDATE.PRODUCT
An existing product is updatedProduct name, summary of changes
Delete Product
DELETE.PRODUCT
A product is deletedProduct name, deletion timestamp

Partners

These scopes cover activity in Suger’s Partner Relationship Management (PRM) module, including partnership invitations, Suger co-sells, and commission lifecycle events.

ScopeWhen it firesDefault email subject
Accept Partnership
ACCEPT.PARTNERSHIP
A partner accepts your partnership invitation[Partner Company] accepted your partnership invitation
Decline Partnership
DECLINE.PARTNERSHIP
A partner declines your partnership invitation[Partner Company] declined your partnership invitation
Accept Sugercosell
ACCEPT.SUGERCOSELL
A partner accepts a seller-initiated Suger co-sell[Partner Company] accepted your co-sell: [Deal Name]
Decline Sugercosell
DECLINE.SUGERCOSELL
A partner declines a seller-initiated Suger co-sell[Partner Company] declined your co-sell: [Deal Name]
Close Won Reminder Sugercosell
CLOSE_WON_REMINDER.SUGERCOSELL
A party marks its co-sell copy Closed Won. A seller close-won notifies every partner; a referrer close-won notifies only the seller.

Always sent; cannot be disabled
Co-sell closed won: [Deal Name]
Pending Commission
PENDING.COMMISSION
A commission is created and awaiting seller approval

Enabled by default; cannot be disabled
Commission pending approval: [Deal Name]
Approve Commission
APPROVE.COMMISSION
A seller approves a commission payout

Enabled by default; cannot be disabled
Your commission for [Deal Name] has been approved
Payment Sent Commission
PAYMENT_SENT.COMMISSION
A seller marks a commission payment as sent to the partner

Enabled by default; cannot be disabled
Payment sent for [Deal Name]
Payment Confirmed Commission
PAYMENT_CONFIRMED.COMMISSION
A partner confirms receipt of a commission payment

Enabled by default; cannot be disabled
[Partner Company] confirmed receipt of payment — [Deal Name]
Auto Confirmed Commission
AUTO_CONFIRMED.COMMISSION
A commission is auto-confirmed after the confirmation window passes without action

Enabled by default; cannot be disabled
Commission auto-confirmed for [Deal Name]
Clawback Commission
CLAWBACK.COMMISSION
A commission is reversed

Enabled by default; cannot be disabled
Commission reversed for [Deal Name]

Auto-Share Report

ScopeWhen it firesDefault email content
Complete Auto Share Task
COMPLETE.AUTO_SHARE_TASK
An automated data-sharing task completes successfullyTask name, completion time, report summary and link
Fail Auto Share Task
FAIL.AUTO_SHARE_TASK
An automated data-sharing task failsTask name, failure reason, recommended remediation steps

Headless Entitlements

ScopeWhen it firesDefault email content
Notify Headless Entitlements
NOTIFY.HEADLESS_ENTITLEMENTS
A headless entitlement (one without a buyer-facing signup flow) is created or requires attentionEntitlement name, marketplace, buyer info, link to the entitlement detail

Revenue

ScopeWhen it firesDefault email content
Disburse Revenue Record
DISBURSE.REVENUE_RECORD
A revenue record disbursement is processed by SugerDisbursement amount, billing period, product, buyer

Suger Co-Sell

ScopeWhen it firesDefault email subjectNotes
New Contact Added Sugercosell
NEW_CONTACT_ADDED.SUGERCOSELL
A new contact is added to an existing Suger co-sellYou’ve been added to a co-sell: [Deal Name]Always sent to the newly added contact — cannot be disabled

Usage Metering Alerts

ScopeWhen it firesDefault email content
Abnormal Alert Usage Record Group
ABNORMAL_ALERT.USAGE_RECORD_GROUP
An abnormal usage pattern is detected in a usage record groupSubject: [Suger Alert] Abnormal Usage Record Groups Detected — includes the affected entitlement, metric name, anomalous values, and a link to your usage metering dashboard