As a user, I need the emailed permit and confirmation to state that my permit must be printed and cannot be stored on a mobile device in order to be valid.

[bryanmcfadden]

This comes from usability testing and users expecting to store permits in their mobile devices. This would be another point at which to educate the user that they must print a permit and not rely upon a digital version.

Acceptance Criteria

• [x] user can see and understand the email language about printing (similar to what's on form)

Tasks

• [x] add the text to the email (html and plaintext) (will)
• [x] Update url back to forest page to reflect the route change. (seth)
• [x] tts approval
• [x] PO approval

Definition of Done

• [x] Code unit / e2e tested and comply with QWASP
• [x] No new security vulnerabilities
• [x] Internal team code review
• [x] Documentation / readme.md / CircleCI updated
• [x] Docker updated
• [x] Compare finished design with mockup
• [x] Usability tested

[sadlerw]

in #259 we added language on the form - is this task just for just adding to the permit as well?

[bryanmcfadden]

@sadlerw - this is for adding the language to the email only. (that no digital copies are accepted..and the permit has to be printed to be valid). Maybe it will go here? (highlighted in yellow)

I would think we want to add the same language and styling as we did on the purchase permit page.

[sadlerw]

yea let's add "Your permit must be printed to be valid and cannot be stored on a mobile device." right after "Print your permit on plain white paper." @JaneZC

[sadlerw]

@MelissaBraxton is it an issue if someone prints it too small? We might want another story to clarify if needed.

[sadlerw]

@tram @MelissaBraxton @ASprinkle if you are ok with us adding as discussed please approve. thanks

[tram]

👍 Reads well! Ship it.

[ASprinkle]

@sadlerw Adding that information in the email gets to goal of the story to instruct the user to print the permit.