add preview confirmation workflow #209
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #175, @aarongerig We finally came up with a proper solution...
Some email providers have spam detection or security features that prefetch URLs from incoming emails (e.g., Safe Links in Microsoft Defender for Office 365).
To prevent unintended automatic activations, you can enable a "preview confirmation" page.
This requires users to manually confirm their registration by clicking an additional button.
This feature is disabled by default. To enable it, update your configuration as follows:
When enabled, users will first be redirected to /confirm-preview/{token},
where they must confirm their registration manually.