Make some features (signature, sharing) that depend on multi_user responsive to whether it's turned on or off

[nonprofittechy]

I think we might want some Python functions to check for a valid SMS and email configuration.

I think we'll need to audit the default interview text to look for places we offer the ability to send by email or SMS and conditionally turn those off. In most places we allow both methods, and in some there's a backup method of clicking a link to copy text, so we probably don't want to turn these totally off in the footer.

[BryceStevenWilley]

I've made some progress on hiding SMS specific options downstream in MLH on just the Share page, trying to get it upstream now.

The places where I see we offer SMS sending that I've address in my branch:

• In the Share page
• In the reminder system
• the option to text the signature

I'm gonna focus on just those at the moment, since the email stuff seems to be in more places and more critical to running a DA server (with password resets, etc.)

[BryceStevenWilley]

Reopening, as I didn't cover things that have multi_user = False yet. I feel like there are a few approaches we could take to those interviews:

• turn things off entirely
• give users the ability to manually turn it on and off
• automatically turn it on when some one shares the signature screen, and turns it off once the form is signed (or some other type of control)

[nonprofittechy]

Reopening, as I didn't cover things that have multi_user = False yet. I feel like there are a few approaches we could take to those interviews:

* turn things off entirely

* give users the ability to manually turn it on and off

* automatically turn it on when some one shares the signature screen, and turns it off once the form is signed (or some other type of control)

I think we'll want to go with your first idea, turn sharing off entirely when multi_user=False. This is because it will usually only be the case when the author has to follow some data privacy liability standard, such as storing PII like a social security number or bank account number. Likely they'll have their data controls in a written policy that they have to maintain and certify that they're following. Making it up to the user to turn off doesn't sound like a good idea.

For signature to your phone, it would still work if the user is logged in, it's just a pain to use in that scenario.