Merged
Conversation
added 26 commits
January 26, 2026 14:21
This reverts commit 88cf8a1e20d0d86e8c1fe6acf499c934bd33dd96.
Code Coverage Report: Only Changed Files listed
Minimum allowed coverage is |
CathLass
approved these changes
Apr 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This feature will implement a control on the use of the Schools Profile website, ensuring that a finite number of users can "register" and have a look around.
The registration process is simply a capture of email, with a parameter in the URL for which local authority they were referred from. This is to help with user research and understand what the service can provide for the public.
Once registered, users will receive an email with a link to return at a later date, but no longer than 7 days. The 7 day limit is enforced from a KeyVault value and can be changed.
The emails are stored in postgres, as are the Local Auths. There is also an instant kill-switch in the settings sql table should there be a need to close the application.
On every page load the gateway middleware checks for a cookie that matches a user's id, and if expired will direct them to the appropriate page.
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Checklist: