Description:
Currently, Breeze (Breeze Assistant) creates notes in the user context but does not set an Activity Owner.
As a result, these notes are technically considered "unowned." In permission configurations where
employees are only allowed to edit/delete "their own notes," they cannot subsequently delete or edit the
notes they created via Breeze because no Activity Owner is recorded.
Desired Behavior:
When creating a note, Breeze should automatically set the executing user as the Activity Owner
– similar to what would happen if the user manually created the note in the record.
Use Case:
• Sales and service teams use Breeze to create conversation or meeting notes directly in the record.
• For compliance/security reasons, permissions are configured so that users can only delete or edit
"their own notes."
• Since Breeze does not set an Activity Owner, these users can no longer delete or correct their own
notes created with Breeze and are dependent on admins.
Impact:
• Increased administrative overhead, as admins/power users must delete notes on behalf of others.
• Increased risk of outdated or incorrect notes that cannot be corrected by the actual authors.
• Lower adoption of Breeze, as users cannot manage their own AI-generated notes.
Benefit of Implementation:
If Breeze sets the executing user as the Activity Owner by default, existing permission concepts
("own notes") will continue to function consistently, and teams can use Breeze much more flexibly and
without additional effort.