Auto-Generated Fallback Links for Embedded Media/Iframes in Buzz Email Notifications

Enhancement Voting Buzz
1

Name of Feature/Request: Auto-Generated Fallback Links for Embedded Media/Iframes in Buzz Email Notifications

What financial, time savings, or quality of life improvements will occur with this:

  1. Quality of Life & Communication Integrity: Eliminates the risk of users and external customers missing critical updates, video instructions, or context hidden within embedded media. Users gain full confidence that email notifications accurately signal all content within a post.
  2. Time Savings: Prevents wasted time and redundant follow-ups caused by team members or clients acting on incomplete information because an embedded video was silently stripped from the notification email.
  3. Customer Experience: Enhances the reliability of Striven for external client interactions. When Striven users post updates for their clients, those clients will always receive a complete visual indicator of available content, protecting the professional quality of communications.

Attempted solutions so far:

  1. Manual Link Insertion: Manually adding explicit text hyper-links above or below embedded videos during Buzz post creation. This workaround relies entirely on user diligence, creates redundant visual clutter inside the Striven UI (where the iframe already renders natively), and fails to solve the issue for posts where the author forgets to add a backup link.
  2. Manual Verification: Requiring recipients to log into Striven to verify if an email notification is missing media, which defeats the purpose and efficiency of email alerts.

Digging deep - Any additional Why behind this request / How was this accomplished before Striven:

  1. The “Why”: Standard email clients (such as Gmail, Outlook, and Apple Mail) automatically strip <iframe> tags from incoming HTML emails due to security protocols. When a user embeds a video into a Striven Buzz post, the post renders correctly on the web platform, but the generated notification email strips the iframe entirely without leaving a placeholder or warning. As a result, email recipients have no way of knowing content was omitted unless they open the post directly in Striven.
  2. How it was accomplished before / Industry Standard: Systems that generate email notifications from rich-text/HTML posts typically run a parser on outgoing emails. When an <iframe> tag is detected, the system strips the iframe element for security compliance but automatically inserts a dynamic fallback link (e.g., a “Watch Embedded Media” button or direct URL text) immediately above or below where the iframe sat. This preserves the rich media experience inside the main application while maintaining 100% visibility and context within email notifications.