How to Require an Email Address to Access a Shared Microapp

Overview

Email gating is a two-step setting. First, enable Require email address at the microapp level — this doesn't gate anything by itself, but it unlocks a Require email checkbox in the Share modal, and every new share link created from that point on will default to that checkbox being checked. From there, you decide per link whether to keep the requirement (leave it checked) or turn it off for that specific link (uncheck it).

If the microapp-level setting is off, the Require email checkbox won't appear in the Share modal at all, and no link created from that microapp can require an email.

Note: Email addresses collected at access are not verified via a confirmation email — viewers can enter any address. The prompt identifies who is accessing your content but does not authenticate their identity.

Who Can Configure This

Role	What they can do
Library Administrator	Enable email gating at the microapp level, and set or override the per-link requirement when sharing.
Editor / Content Owner	Set or override the per-link requirement when sharing, once gating is enabled at the microapp level.
Viewer	Must provide an email address to access the microapp when a given share link has the requirement enabled.

ConfigurationStep 1: Enable Email Gating at the Microapp Level

This is a prerequisite step. Until this is turned on, the Require email option will not appear when you go to share the microapp.

1. Navigate to the Tiled Hub and locate the microapp.

2. Open the microapp Settings panel.

3. Under Sharing, toggle Require email address to on.

4. Click Save.

Step 2: Confirm or Override the Requirement for Each Share Link

Once gating is enabled at the microapp level, every new share link defaults to requiring an email address. You can leave this as-is, or uncheck it for a specific link if that link shouldn't be gated.

1. From the microapp, click Share.

2. In the share configuration dialog, the Require email checkbox appears — checked by default.

3. Leave it checked to require an email for this link, or uncheck it if this specific link shouldn't be gated.

4. Copy or distribute the link as usual.

Viewing Who Accessed Your Microapp

When the email gate is active on a link, email addresses collected at the point of access are recorded and available in the microapp's Engagement dashboard. You can use this data to see who has opened your shared content and when.

If someone other than the original intended recipient opens a share link, you'll see an alert in Engagement > My Activity identifying the email address that was used.

Common Questions

If I enable Require email address at the microapp level, does every share link require an email forever?

Not automatically forever. Enabling it at the microapp level makes the Require email checkbox available in the Share modal and defaults new links to having it checked, but you can uncheck it for any individual link if you don't want that particular link gated.

What happens if a viewer enters a fake email address?

The gate collects whatever email the viewer enters but does not verify it. If recipient identity verification is critical for your use case, consider pairing this setting with a password-protected share link for an additional layer of access control.

Does enabling this setting at the microapp level affect existing share links?

No — it affects new share links going forward, which will default to requiring an email. Previously generated links keep whatever setting they were created with. Check any existing links individually if you need to confirm their setting.

Where do I see the emails collected from viewers?

Collected email addresses appear in the Engagement dashboard for the microapp. You can also export engagement data from this view.

Can I use collected emails with my CRM?

Yes — engagement data including collected email addresses can be connected to downstream tools. See the related articles below for more details.