Getting Started
      Back to home
      1. Knowledge Base
      2. Getting Started

      Beta Program Participation

      Learn about participating in the beta program for User Acceptance Testing (UAT).

      Table of Contents

      Overview

      New Capabilities to Expect

      Outlook Add-in

      Admin Dashboard

      Deploying the Beta Add-in

      Beta Support

      Overview

      The invitation-only beta program, currently available for the Outlook Add-in, is designed to involve early adopters in User Acceptance Testing (UAT) to help identify, report, and resolve issues in new releases before full deployment.

      • New releases hit beta two weeks before the Production Main.

      • Releases are promoted to production after beta participants give their approval.

      • Features requested by beta participants are prioritized.

      • Slack Connect provides access to Preava engineers for real-time support. (Microsoft Teams may be available in the future.)

      New Capabilities to Expect

      Outlook Add-in

      No major feature updates are expected for the Outlook Add-in in 2024. However, in 2025, these features are anticipated:

      • Transactional email scanning to improve DLP, ML, and NLM functionality.
      • Task pane UI enhancements detailing alert reasons.

      Admin Dashboard

      The Admin Dashboard will undergo a major overhaul starting in late 2024, continuing into 2025. The following features are anticipated:

      • A new beta Admin Dashboard with an updated UI will be available to beta participants.

      • Improved auditing of risk alerts and user actions.
      • Analytics reporting on metrics like total emails scanned and corrective actions taken.

      Deploying the Beta Add-in

      📝 Same API and Admin Dashboard for Beta and Production Distributions

      The Preava API and Admin Dashboard are used for configuring both beta and production distributions.

      1. Add internal IT beta users to a dedicated Entra ID group (see instructions).
      2. Determine which manifest distribution(s) (see documentation) beta users will use:
        1. Beta for UAT only.
        2. Beta for UAT + Production Main: This alerts users to risks twice—once for each add-in distribution.
      3. Choose the deployment method (see documentation). Preava recommends the Optional method.
      4. Deploy the Beta for UAT to the specified Entra ID group (see instructions).

      Beta Support

      Two channels are available for beta users to submit feedback and report issues:

      1. Slack Connect: Email beta users' email addresses to support (see Contact Support).
      2. Email: Beta users can contact support directly via email (see Contact Support).