Reach people before they have an account
Send an operation email to an address stored on the record, even when its recipient has no existing user session or profile. This supports invitations and other messages whose destination is known before registration.
Example — Invite a new colleague
An administrator enters the colleague’s email address. The invitation goes to that address, rather than back to the administrator who created it.
For engineers
Select the address from the operation result
An email notification can declare recipientEmailField: the name of one top-level field on the committed record containing one email-address string. It is not a nested path, address array or recipient selector. The membership invitation reads userEmail:
Selected from organization-members.shared.resources-config.schemas.ts; surrounding module configuration is omitted.
userNotifications: [
{
target: CoreUserNotificationTarget.USER_SELF,
channel: CoreUserNotificationChannel.EMAIL,
recipientEmailField: 'userEmail',
condition: isPendingOrganizationMemberInvitation,
}
]
That address takes the email-by-address route instead of recipient-user expansion. The target still participates in the notification/template identity; it does not override the explicit destination. Here USER_SELF preserves the invitation template reference, while userEmail identifies the invitee.
Supply content that does not assume a profile
The path uses application-default locale behavior because no user preferences record is available. Its base operation context and additional token context remain available, so the invitation template can render the acceptance URL. Do not assume a first name or personalized language exists merely because an address does.
The sender validates address format before network submission. Missing addresses or submission failures are logged as notification failures rather than reversing the completed business action. For critical invitation recovery, the named resend operation supplies a new token and message.