---
schema_version: "1"
id: 68fffb6102f5e49b3a49af44a200f59b4dc1393b85a92a2d66d8b08522396810
title: Considerations for Product and Service Notifications
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/mktg/264-0-0/pardot_admin_product_service_considerations.md
canonical_url: https://help.salesforce.com/s/articleView?id=mktg.pardot_admin_product_service_considerations.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2b04fe194aa4982fa98adf8e44f79e3c5c73b4d693aaf9f31b97005650553832
description: Keep these considerations in mind when using product and service notifications.
products:
  - Marketing
  - Marketing Cloud Account Engagement
release: "264"
---
# Considerations for Product and Service Notifications

Keep these considerations in mind when using product and service notifications.

- Any Account Engagement admin can edit points of contact.
- A point of contact must be an Account Engagement user. You can’t use agency users.
- Any user type can be a point of contact.
- For business units provisioned on or after December 7, 2015, all points of contact default to user who was created first.
- A point of contact can’t be empty. You can’t delete a user who is listed as a point of contact. Reassign the point of contact before deleting the user.
- Notifications can have only one user listed as a point of contact. To send a notification to multiple recipients, create an email distribution list, and then create a user with the distribution list email address.
- When you approach or reach a database limit, both the point of contact and the user who most recently logged in receive an email notice.