This bug will be used to track implementing a Normandy action to prompt and deliver SHIELD study addons to users.

We discussed some implementation details in a meeting: - The consent page will live in the system add-on, as we don't expect it to change often, and having the page be local to the add-on avoids issues with getting a remote page whitelisted for add-on installation without scary warning prompts. - We probably want some level of signing for SHIELD study add-ons, but which level is still undetermined. This also affects the level of review we want to get from AMO for study add-ons before we launch them. - We are considering making arguments to the action accept markdown in order to provide more control over the structure of the consent page, but aren't yet sure if we want to commit to that as it increases the complexity of the add-on.

That sounds accurate based on the meeting we had last week. Let me know if you have anything we need to clarify.

This is currently blocked by awaiting a final design for the study consent page, which will come after we ship more studies with the instrumented consent page. I don't think this fits in 2016q2 anymore. Matt_G: Feel free to re-add it to the tracker if you disagree.

Spec notes from prior meeting: Add a normandy action that prompts users to participate in a SHIELD study. The action form should include any specifications needed for the consent page & the study addon itself. The action should only be run if the user doesn't currently have the study addon installed, and we can determine they have not yet seen the prompt for this particular study. The Normandy addon should use a page worker to open a tab with the consent page that outlines the participation details, and allows users to install the study addon.