CDCgov
Ensure that Terms of Service are signed by onboarding organizations
User Story:
As a ReportStream admin, I want to ensure that newly onboarded organizations have signed the Terms of Service, so they can continue having access to the ReportStream platform and tools.
Background
From user synthesis: There appears to be an opportunity to ask a question about how we might input a forcing function to have users sign a Terms of Service before proceeding in the process. If we allow users to continue for weeks in the process without a signed Terms of Service as a soft blocker or service bottleneck, this will delay onboarding and continue to confuse users.
Risks/Impacts/Considerations
- Need to understand when / what step in the process this 'soft block' is implemented
- Need to strategize the severity of the 'soft block'; we don't want to bottleneck development and troubleshooting, but users do need to sign the ToS before continuing.
Dev Notes:
- TBD
Working links:
- MedArbor Research Synthesis Debrief
- [MedArbor Weekly Sync notes] (https://docs.google.com/document/d/1xQPASiXAT_HuFfUWf3I1-rTjzbbUgd9jU8DBxPzLT6I/edit#heading=h.8scal3o7ehc1)
Acceptance Criteria
- [ ] Strategy to implement soft block of ToS for newly onboarded organizations
Out of scope
- Implementation
@GlennRGrieves has confirmed that we did not get the ToS signed during onboarding for CVS and Carbon Health, but they have been signed now after onboarding.
We should flag this ticket for Q3 roadmap to be led by Acct Mgmt and Product
Currently not onboarding new senders/receivers, so this is not a high priority