Mailprotector

Product Requests

The Product Requests page enables Shield Admins to approve or deny user requests for Shield Pro, the only currently requestable product, which grants access to premium productivity and privacy features through a multi-step activation process ensuring users benefit from Shield Pro from day one.

Skip to main content

In this article

  1. 1.Description
  2. 2.Product Request and Approval Process
  3. 3.Managing Product Request Visibility

Description

The Product Requests page allows Shield Admins to approve or deny requests for products offered in Shield. Currently, Shield Pro is the only product a Shield user can request. The Shield Pro request process grants or denies users access to premium productivity and privacy features. The multi-step activation process with the required welcome guide ensures users benefit from their Shield Pro features from day one.

Product Request and Approval Process

Step 1: A Shield User Requests Shield Pro

When users encounter Shield Pro features that aren't yet available to them via the Shield Portal page, they'll see greyed-out options for:

  • Bundler - Organizes non-urgent messages to keep inboxes focused
  • Lockbox - Extra protection for sensitive emails with multi-factor authentication
  • Burner Addresses - Temporary email addresses you can create and delete on demand
  • VIP Pass - Trusted delivery addresses that bypass normal filtering

Clicking on any of these features in the Portal allows users to request Shield Pro access.

Shield Pro Options - Shield Portal.pngRequest Shield Pro - Shield User.png

Step 2: Shield Admins Review Requests

Product requests appear in Shield Ctrl, where Shield Admins who have Manage Request Notifications enabled can review and take action. The Product Requests page shows:

  • The name and email address of the Shield user making the request
  • The Shield Organization information
  • The product being requested (Shield Pro)
  • When the request was submitted
  • Approve and Deny action buttons

Shield Control - Product Requests.pngProduct Requests - Approve or Deny.png

Step 3: Shield Admin Makes a Decision

Shield Admins have two options for each request.

Approve the Request

  • Clicking Approve provisions Shield Pro for that user
  • The welcome email process is started, which requires the user to review the Welcome Guide for features Shield Pro to activate
  • The user's account is updated to include Pro features, visible on the Add or Remove Products page

Deny the Request

  • Clicking Deny removes the request without taking further action
  • The user maintains their standard Shield access level

Step 4: User Activation

When a request is approved, the user receives a welcome email requiring them to click the Open Welcome Guide button.

Users must complete the Shield Pro Welcome Guide before Shield Pro features become active. If they skip this step, Shield Pro remains inactive on their account.

Step 5: Account Updates

Once approved and activated, Shield Pro features will be illuminated, and each will click through to its respective configuration page.

Shield Pro enabled - Portal.png

Managing Product Request Visibility

Shield Admins control whether users who don’t yet have Shield Pro can see and request Shield Pro features.

Disable or Re-enable Product Requests

  1. 1.Go to your organization's preferences in Shield Ctrl
  2. 2.Find "Shield Pro Feature Previews"
  3. 3.Change from "Show to non-Pro users" to "Hide from non-Pro users"

This prevents non-Pro users from seeing greyed-out Pro features and requesting access.

Configure Preferences - Shield Pro Hide or Show.pngShield Pro Options - Shield Portal.png

Related to

Updated 1 year ago

Previous article

Breadcrumbs

Next article

View Groups

Was this article helpful?

0 out of 0 found this helpful

YesNo

Can't find what you're looking for?

Submit a request

9nnyrv9n9w9k.statuspage.io

9nnyrv9n9w9k.statuspage.io is blocked

This page has been blocked by an extension

  • Try disabling your extensions.

ERR_BLOCKED_BY_CLIENT

Reload

This page has been blocked by an extension

<% if (previousArticle || nextArticle) { %>

<% if (previousArticle) { %>

Previous article

<%= previousArticle.title %>

<% } %> <% if (nextArticle) { %>

Next article

<%= nextArticle.title %>

<% } %>

<% } %>