Who This Is For / When to Use
This feature is for Kyrios users who rely on Internal Notification (Email) actions to alert team members and need to keep managers, collaborators, or audit recipients informed automatically.
Use this when internal emails should reach multiple internal recipients without creating extra workflow steps.
What CC/BCC Support in Internal Notifications Does
CC and BCC support allows internal workflow emails to include additional recipients beyond the primary user type selected.
This enables:
Shared visibility across teams
Quiet oversight using BCC
Reduced workflow complexity by avoiding duplicate notification actions
The functionality mirrors CC/BCC behavior already available in the Email action and is now available in Internal Email Notifications.
Where CC and BCC Appear in the Action
When Email is selected as the notification type, the Internal Notification action displays dedicated CC and BCC fields.
These fields support:
Static email addresses
Dynamic values (merge fields)
How to Use CC/BCC in an Internal Email Notification
Step 1: Add an Internal Notification Action
In the Workflow Builder, add an Internal Notification action at the appropriate step.
Step 2: Select Email as the Notification Type
From the Type of Notification dropdown, select Email.
Step 3: Choose the Recipient User Type
Select the User Type that should receive the primary internal notification.
This determines the main recipient of the email.
Step 4: Add CC and/or BCC Recipients
Enter one or more email addresses in the CC and/or BCC fields.
Merge fields can be used to dynamically populate recipients.
Step 5: Save and Publish
Save the action and publish the workflow.
All future internal email notifications from this step will include the specified CC/BCC recipients.
Important Behavior Notes
CC and BCC are available only when Email is selected as the notification type.
CC recipients are visible to all recipients.
BCC recipients are hidden from other recipients.
Leaving CC/BCC empty does not affect existing notification behavior.
Why This Update Matters
Previously, adding additional recipients to internal notifications required:
Duplicate notification actions
Separate email workflows
Manual forwarding
Native CC/BCC support simplifies internal communication while keeping workflows clean, readable, and easier to maintain.
Common Issues and Fixes
CC/BCC fields do not appear
Cause: Notification type is not set to Email.
Fix: Change the Type of Notification to Email.
CC/BCC recipient does not receive the email
Cause: Invalid email address or unresolved merge field.
Fix: Confirm the email address format or verify that the merge field resolves to a valid email.
Multiple people need the same notification
Cause: Only one User Type is selected.
Fix: Use CC for visible recipients or BCC for silent recipients instead of duplicating actions.