Conversation
Clarify that it begins when a user accepts the agreement on behalf of their organisation, rather than tying to the concept of Organisation Admin.
This decouples the MOU from our specific way we model permissions.
This eliminates unnecessary details, we don't need to explain why in the MOU.
This doesn't define any responsibilities and something that can be in the product documentation.
This simplifies the text, as organisation can generally provide access themselves without needing to get in touch.
Updated the text to specify that organisations are responsible for managing user access to GOV.UK Forms, including the prompt removal of access for users who no longer require it.
Updated the text be more general and remove specific examples.
Updated the text to clarify that users are responsible for the security and configuration of systems receiving form response data, while removing specific examples and redundant notes.
Updated the text to emphasize that users must validate any form response data, including email addresses, to ensure accuracy and suitability for its intended purpose.
|
|
🎉 A review copy of this PR has been deployed! You can reach it at: https://pr-2528.admin.review.forms.service.gov.uk/ It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready For the sign in details and more information, see the review apps wiki page. |
DavidBiddle
left a comment
There was a problem hiding this comment.
Changes all look sensible, they're clearly written, and well explained in the commit messages 🎉
I think the Last Updated date needs changing but once that's done I think this all looks good.
|
Out of date now. |



This pull request updates the Memorandum of Understanding (MOU) text shown to users in the
app/views/mou_signatures/_mou_version_current.html.erbfile. The changes clarify the agreement's start conditions, notification periods, and responsibilities regarding security, data management, and access. The language is simplified and some sections are condensed for clarity and to reduce prescriptive technical detail.Key changes include:
Agreement terms and notifications:
Security and access responsibilities:
Other clarifications: