darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2026-06-04 05:20:46 -04:00
Code Issues Packages Projects Releases Wiki Activity
Files
17f74cf621ced95f044b4ee467441928b5b80e50
notifications-admin/app/navigation.py

1354 lines
41 KiB
Python
Raw Normal View History

Highlight selected navigation item In research I’ve sometimes seen people click the wrong nav item. I reckon that people’s concept of which pages live behind which navigation items isn’t very strong. We can reinforce this relationship by showing, for every page, which is the corresponding nav item. The conventional way of doing this is either with some kind of emphasis, typically colour or bold. I’ve gone for bold because colour would be weird. --- The implementation of this is quite loosely coupled to our application code because: - our application code is not well structured (eg we don’t make any use of blueprints) - spreading this change across lots of files in our application would make it harder to test without actually hitting each endpoints; such tests would be slow and verbose So I’ve gone for more of a meta approach. Rather than testing that each endpoint has a specific navigation item selected, I’ve gone for validating that: - all endpoints being mapped to are real - all endpoints have _a_ selected navigation item (or are specifically excluded) This means that it’s impossible to add, change or remove an endpoint without also updating which navigation item should be selected. And the actual mapping is so declarative that it testing it would be redundant.
2018-04-24 12:48:05 +01:00
from itertools import chain
from flask import request
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
class Navigation:
Highlight selected navigation item In research I’ve sometimes seen people click the wrong nav item. I reckon that people’s concept of which pages live behind which navigation items isn’t very strong. We can reinforce this relationship by showing, for every page, which is the corresponding nav item. The conventional way of doing this is either with some kind of emphasis, typically colour or bold. I’ve gone for bold because colour would be weird. --- The implementation of this is quite loosely coupled to our application code because: - our application code is not well structured (eg we don’t make any use of blueprints) - spreading this change across lots of files in our application would make it harder to test without actually hitting each endpoints; such tests would be slow and verbose So I’ve gone for more of a meta approach. Rather than testing that each endpoint has a specific navigation item selected, I’ve gone for validating that: - all endpoints being mapped to are real - all endpoints have _a_ selected navigation item (or are specifically excluded) This means that it’s impossible to add, change or remove an endpoint without also updating which navigation item should be selected. And the actual mapping is so declarative that it testing it would be redundant.
2018-04-24 12:48:05 +01:00
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
mapping = {}
exclude = {}
Replace links in navigation Includes: - removing all styling of those links outside of GOV.UK Frontend (except for a few fixes due to their interaction with our design) - bringing together some duplicate styles into one block - changing how links are marked as selected, now they have multiple classes Fix Sass-lint error in navigation.scss
2019-12-11 20:33:57 +00:00
selected_class = "selected"
Highlight selected navigation item In research I’ve sometimes seen people click the wrong nav item. I reckon that people’s concept of which pages live behind which navigation items isn’t very strong. We can reinforce this relationship by showing, for every page, which is the corresponding nav item. The conventional way of doing this is either with some kind of emphasis, typically colour or bold. I’ve gone for bold because colour would be weird. --- The implementation of this is quite loosely coupled to our application code because: - our application code is not well structured (eg we don’t make any use of blueprints) - spreading this change across lots of files in our application would make it harder to test without actually hitting each endpoints; such tests would be slow and verbose So I’ve gone for more of a meta approach. Rather than testing that each endpoint has a specific navigation item selected, I’ve gone for validating that: - all endpoints being mapped to are real - all endpoints have _a_ selected navigation item (or are specifically excluded) This means that it’s impossible to add, change or remove an endpoint without also updating which navigation item should be selected. And the actual mapping is so declarative that it testing it would be redundant.
2018-04-24 12:48:05 +01:00
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
def __init__(self):
self.mapping = {
navigation: {
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
# if not specified, assume endpoints are all in the `main` blueprint.
self._get_endpoint_with_blueprint(endpoint) for endpoint in endpoints
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
} for navigation, endpoints in self.mapping.items()
}
Highlight selected navigation item In research I’ve sometimes seen people click the wrong nav item. I reckon that people’s concept of which pages live behind which navigation items isn’t very strong. We can reinforce this relationship by showing, for every page, which is the corresponding nav item. The conventional way of doing this is either with some kind of emphasis, typically colour or bold. I’ve gone for bold because colour would be weird. --- The implementation of this is quite loosely coupled to our application code because: - our application code is not well structured (eg we don’t make any use of blueprints) - spreading this change across lots of files in our application would make it harder to test without actually hitting each endpoints; such tests would be slow and verbose So I’ve gone for more of a meta approach. Rather than testing that each endpoint has a specific navigation item selected, I’ve gone for validating that: - all endpoints being mapped to are real - all endpoints have _a_ selected navigation item (or are specifically excluded) This means that it’s impossible to add, change or remove an endpoint without also updating which navigation item should be selected. And the actual mapping is so declarative that it testing it would be redundant.
2018-04-24 12:48:05 +01:00
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
@property
def endpoints_with_navigation(self):
return tuple(chain.from_iterable((
endpoints
for navigation_item, endpoints in self.mapping.items()
)))
Highlight selected navigation item In research I’ve sometimes seen people click the wrong nav item. I reckon that people’s concept of which pages live behind which navigation items isn’t very strong. We can reinforce this relationship by showing, for every page, which is the corresponding nav item. The conventional way of doing this is either with some kind of emphasis, typically colour or bold. I’ve gone for bold because colour would be weird. --- The implementation of this is quite loosely coupled to our application code because: - our application code is not well structured (eg we don’t make any use of blueprints) - spreading this change across lots of files in our application would make it harder to test without actually hitting each endpoints; such tests would be slow and verbose So I’ve gone for more of a meta approach. Rather than testing that each endpoint has a specific navigation item selected, I’ve gone for validating that: - all endpoints being mapped to are real - all endpoints have _a_ selected navigation item (or are specifically excluded) This means that it’s impossible to add, change or remove an endpoint without also updating which navigation item should be selected. And the actual mapping is so declarative that it testing it would be redundant.
2018-04-24 12:48:05 +01:00
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
@property
def endpoints_without_navigation(self):
return tuple(
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
self._get_endpoint_with_blueprint(endpoint) for endpoint in self.exclude
Revert "Revert "Statsd to prometheus""
2020-07-01 13:27:12 +01:00
) + ('static', 'status.show_status', 'metrics')
Highlight selected navigation item In research I’ve sometimes seen people click the wrong nav item. I reckon that people’s concept of which pages live behind which navigation items isn’t very strong. We can reinforce this relationship by showing, for every page, which is the corresponding nav item. The conventional way of doing this is either with some kind of emphasis, typically colour or bold. I’ve gone for bold because colour would be weird. --- The implementation of this is quite loosely coupled to our application code because: - our application code is not well structured (eg we don’t make any use of blueprints) - spreading this change across lots of files in our application would make it harder to test without actually hitting each endpoints; such tests would be slow and verbose So I’ve gone for more of a meta approach. Rather than testing that each endpoint has a specific navigation item selected, I’ve gone for validating that: - all endpoints being mapped to are real - all endpoints have _a_ selected navigation item (or are specifically excluded) This means that it’s impossible to add, change or remove an endpoint without also updating which navigation item should be selected. And the actual mapping is so declarative that it testing it would be redundant.
2018-04-24 12:48:05 +01:00
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
def is_selected(self, navigation_item):
if request.endpoint in self.mapping[navigation_item]:
Replace links in navigation Includes: - removing all styling of those links outside of GOV.UK Frontend (except for a few fixes due to their interaction with our design) - bringing together some duplicate styles into one block - changing how links are marked as selected, now they have multiple classes Fix Sass-lint error in navigation.scss
2019-12-11 20:33:57 +00:00
return " " + self.selected_class
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
return ''
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
@staticmethod
def _get_endpoint_with_blueprint(endpoint):
return endpoint if '.' in endpoint else 'main.{}'.format(endpoint)
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
class HeaderNavigation(Navigation):
mapping = {
'support': {
'bat_phone',
'feedback',
'support',
Direct members of the public somewhere more useful We can’t give advice to members of the public, but increasingly we’re seeing them try to use our support form to ask. It would be better for them if we can direct them straight to somewhere more useful, before they have the chance to raise a support ticket. This commit replaces the report a problem/ask a question triaging for users who aren’t signed in. It’s not possible for non-signed-in users to raise an priority 1 ticket, so we never need to triage the tickets in this way. Instead we can triage people based on whether they work in the public sector or not. If they do then we send them on to the feedback form. If not then they go to a new page which contains some useful links. We’ve chosen these links based on some analysis of the support tickets we’ve received recently[1] 1. https://docs.google.com/spreadsheets/d/1uBQn-ZnCYfz6ltFaUKZpytgvBF0-MeshCLZ1cD74R0c/edit?usp=sharing
2020-03-24 15:01:42 +00:00
'support_public',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'thanks',
'triage',
},
'features': {
'features',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'features_email',
'features_letters',
'features_sms',
'message_status',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'roadmap',
'security',
'terms',
Make ‘Trial mode’ page highlight features nav item
2019-06-04 11:31:31 +01:00
'trial_mode_new',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'using_notify',
},
'pricing': {
'pricing',
Add ‘How to pay’ page Content from https://docs.google.com/document/d/1uIFW8c7Vk0-FQ-d8H1FmNZLHKn_tOXWg5oUL8bbcZzw/edit?ts=5ced1ae4#
2019-06-04 10:43:15 +01:00
'how_to_pay',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
},
'documentation': {
'documentation',
'integration_testing',
},
'user-profile': {
'user_profile',
'user_profile_email',
'user_profile_email_authenticate',
'user_profile_email_confirm',
'user_profile_mobile_number',
'user_profile_mobile_number_authenticate',
'user_profile_mobile_number_confirm',
'user_profile_name',
'user_profile_password',
make sure tests all populate the platform admin field it's always returned by the API
2019-06-14 15:14:00 +01:00
'user_profile_disable_platform_admin_view',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
},
'platform-admin': {
Add page to archive user Users can only be archived by Platform Admin from the user page (/users/<user_id>). This removes them from all services and orgs and updates their details.
2019-05-22 11:38:47 +01:00
'archive_user',
add clear cache platform admin page a form that allows you to clear entries from the cache for all of either users, services or templates. It'll tell you the largest amount of keys deleted, since there are multiple keys associated with each model.
2019-02-15 10:27:38 +00:00
'clear_cache',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'create_email_branding',
Add page to create new letter branding This has a form with 3 fields - the file upload field, logo name, and an optional logo domain. Logos need to be uploaded in `.svg` format and we then convert this to `.png` format and upload both file types to S3 as well as saving the letter branding details in the database.
2019-01-31 16:56:35 +00:00
'create_letter_branding',
Add page showing priority of two SMS providers It’s not very useful to know the priority of one provider without knowing the other. And these pages were never really designed, so they weren’t super easy to understand anyway. This commit adds a page that takes the first two text message providers and shows their relative priority against each other. It follows the design of the events page, as a pattern for showing a log of historical events.
2019-12-02 14:29:34 +00:00
'edit_sms_provider_ratio',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'email_branding',
Find services by name or partial name
2019-08-13 16:25:26 +01:00
'find_services_by_name',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'find_users_by_email',
Add '/letter-branding' page to show all letter brands This is a platform admin page which lists all letter brands and their domain. Once the page to edit a letter brand has been created, each brand will link to its edit page, but for now this is just a list of brand names and domains.
2019-02-07 16:16:22 +00:00
'letter_branding',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'live_services',
Get live services csv report
2019-04-24 16:23:12 +01:00
'live_services_csv',
Add new report to show monthly notification stats for each service This report will be used by the engagement team. There is a form to give a start and end date for the report, and the form is then downloaded as a CSV file when the form is submitted.
2019-07-22 13:09:03 +01:00
'notifications_sent_by_service',
Provide Performance Platform report as Excel file This is the format we need to upload it in, so this means not having to manually re-save it as Excel.
2019-05-03 14:32:02 +01:00
'performance_platform_xlsx',
New report on platform-admin/reports page to get the usage for all services.
2019-08-23 17:14:04 +01:00
'usage_for_all_services',
Tidy up the platform admin pages This commit does two things: - brings the ‘All organisations’ page back within the platform admin part of the site (because it’s hard to find otherwise) - makes the layouts of all the pages within platform admin a bit closer to the service-specific pages in terms of heading sizes, spacing, etc so that moving between them doesn’t feel so jumpy
2020-04-23 11:08:43 +01:00
'organisations',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'platform_admin',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'platform_admin_list_complaints',
Basic reports page, returns 200 and is visible in PA sidebar
2019-04-24 10:27:57 +01:00
'platform_admin_reports',
Add a platform admin page to submit returned letter references A platform admin form accepts a list of references (one per line) received from DVLA and sends them to the API to update notification statuses. References we get from DVLA start with `NOTIFY00\d`, which isn't part of the reference we store in the database, so we remove them before sending the data to the API. The new `returned-letter` status should be treated as `delivered` for now until we decide a way to display returned letters to users.
2018-09-06 16:34:23 +01:00
'platform_admin_returned_letters',
Reduce usage of the platform admin index page This page is slow to load which means: - it’s annoying for us - it’s potentially causing load on the database This commit does two things to reduce the amount we’re unnecessarily looking at this page: 1. Avoid redirecting to it when signing in as a platform admin user 2. Don’t go directly to it when clicking ‘platform admin’ at the top, but instead show a holding page (there’s a fair chance you’ve clicked that link in order to go and manage some email branding or find a user, not wait for stats to load)
2020-03-19 10:49:40 +00:00
'platform_admin_splash_page',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'suspend_service',
'trial_services',
'update_email_branding',
Add update_letter_branding view function This works in a similar way to the create_letter_branding view function, but with a few minor differences: * Since we already have a file, uploading a file is no longer required (since we can just use the current file if a new one is not uploaded) * We save the changes in the database, then upload the new files to S3. If saving to S3 raises an error, we now rollback the database changes to prevent any errors when trying to view letters with the original logo.
2019-02-11 15:31:12 +00:00
'update_letter_branding',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'user_information',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'view_provider',
'view_providers',
},
'sign-in': {
Send 2fa email and move user to waiting page when they need to re-validate email access
2020-01-27 18:10:45 +00:00
'revalidate_email_sent',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'sign_in',
'two_factor',
'two_factor_email',
'two_factor_email_sent',
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run
2020-05-04 12:27:51 +01:00
'two_factor_email_interstitial',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'verify',
'verify_email',
},
}
exclude = {
'accept_invite',
'accept_org_invite',
'action_blocked',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'add_data_retention',
Use same layout as other organisation pages So it feels consistent from moving from one page to another, rather than jumping in and out of the platform admin view.
2019-07-02 09:49:00 +01:00
'add_organisation',
Let GP surgeries create their own organisations We have a bunch of GP surgeries who want to go live. They don’t automatically assigned to organisations. So this means a lot of back and forth to get these organisations set up, and then the service has to re-request to go live, and… it’s painful. Instead, let’s let GPs create their own organisations, by confirming the name of their organisation before going on to letting them accept the agreement.
2019-09-04 16:27:25 +01:00
'add_organisation_from_gp_service',
Let NHS Trusts and CCGs choose own organisation All we do via support is ask which organisation they work for and manually assign their service to it. This commit makes that process self service. We think we have all the trusts and clinical commissioning groups loaded into the database now. This will make the go live process smoother for these teams.
2019-09-05 16:18:02 +01:00
'add_organisation_from_nhs_local_service',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'add_service',
'add_service_template',
'api_callbacks',
'api_documentation',
'api_integration',
'api_keys',
'archive_service',
Add page where users can say they want branding At the moment branding is an undocumented feature. We get a bunch of support tickets from teams asking its possible. This commit: - lets people know it’s possible, and what the options are - is the first step towards making this process as self-service as possible In some cases we will be able to infer a user’s organisation from there email address, and Google image search their logo. So the experience for them is that they press a button and government just sorts it out for you (also known as "the dream"). In other cases we will have to get back to people asking for a copy of their logo, or to find out about their service, but this is what we have to do at the moment anyway.
2018-05-18 14:05:48 +01:00
'branding_request',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'callbacks',
'cancel_invited_org_user',
'cancel_invited_user',
'cancel_job',
Add link to cancel letters Added a link to cancel letters from the letter notification pages if the letter is still able to be cancelled. Clicking on this link will show a confirmation box, and will then cancel the letter if the user confirms.
2018-12-05 10:58:27 +00:00
'cancel_letter',
Letter job can't be cancelled if already printed Non-cancellable letter statuses mean that it's too late to cancel a job
2019-06-18 18:00:36 +01:00
'cancel_letter_job',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'check_and_resend_text_code',
'check_and_resend_verification_code',
'check_messages',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_messages_preview',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'check_notification',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_notification_preview',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'choose_account',
Add a page to choose a contact list You’ll be able to use a contact list by first choosing a template, then choosing the list you want to use. At the moment this shows all lists, not just the ones that are compatible with your template.
2020-03-13 17:51:22 +00:00
'choose_from_contact_list',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'choose_service',
'choose_template',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'choose_template_to_copy',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'confirm_edit_organisation_name',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'confirm_edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'confirm_edit_user_mobile_number',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'confirm_redact_template',
'conversation',
'conversation_reply',
'conversation_reply_with_template',
'conversation_updates',
'cookies',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'copy_template',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'create_api_key',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'data_retention',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'delete_service_template',
Build delete folder endpoint that calls template_folders_api_client
2018-11-13 17:56:47 +00:00
'delete_template_folder',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'delivery_and_failure',
'delivery_status_callback',
'design_content',
Add an endpoint to download a contact list In case you need to download it, modify it, and re-upload it when you don’t have access to the existing list.
2020-03-15 19:13:07 +00:00
'download_contact_list',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'download_notifications_csv',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'edit_data_retention',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_agreement',
'edit_organisation_crown_status',
'edit_organisation_domains',
'edit_organisation_email_branding',
'edit_organisation_letter_branding',
Allow custom notes when service goes live This adds an option on the organisation settings page to add 'request_to_go_live_notes'. When a service belonging to this organisation requests to go live, any go live notes for the organisation will be added to the Zendesk ticket in the 'Agreement signed' section.
2019-05-13 14:50:40 +01:00
'edit_organisation_go_live_notes',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'edit_organisation_name',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_type',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'edit_provider',
'edit_service_template',
Edit template postage from a separate view
2019-01-29 15:43:59 +00:00
'edit_template_postage',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'edit_user_org_permissions',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'edit_user_mobile_number',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'edit_user_permissions',
'email_not_received',
'email_template',
'error',
Move the ‘estimated usage’ questions We get a bunch of requests to go live where people have told us they're going to send email but there is no email reply-to address present. These come from 2 scenarios: 1. when there are email templates, and no reply to address – but they ignore the checklist 2. when there are no email templates (yet) but they provide anticipated volumes for email At the moment we only auto-check for a reply to address when they have email templates. And because the question about anticipated volumes follows the checklist, you'll get a checklist that passes (reply addresses not required as no templates present) - but your future intent that differs (reply address IS required because you have anticipated volumes). So let’s bring the request for anticipated volumes into the checklist, that way we can dynamically add the requirement for a reply to address if they say they will send email but don't have templates yet. We should begin storing it in the database against the service to stop people having to re-enter it each time they try to complete the go live screens. This also means moving the ‘consent to research question’ along with the questions about volume, because - we want people to answer both before going live - we don’t want to clutter up the summary page by asking questions there too
2019-02-15 11:03:19 +00:00
'estimate_usage',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'forgot_password',
'get_example_csv',
'get_notifications_as_json',
Add endpoint for new page
2019-10-17 16:15:28 +01:00
'get_started',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'get_started_old',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'go_to_dashboard_after_tour',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'guidance_index',
'branding_and_customisation',
'create_and_send_messages',
'edit_and_format_messages',
'send_files_by_email',
'upload_a_letter',
Move service history into it own file We’re going to do some work on this page, let’s put it in a sensible place first before we add a bunch more code to the wrong place.
2019-10-18 09:18:51 +01:00
'history',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'inbound_sms_admin',
'inbox',
'inbox_download',
'inbox_updates',
'index',
'information_risk_management',
'information_security',
'invite_org_user',
'invite_user',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.letter_branding_preview_image',
Add a redirect for the letter specification This way we have a URL we can give people that always points to the latest version of the spec. And it makes our code more Flask-idiomatic to be using `url_for` to be generating a URL, rather than passing around a constant.
2020-01-15 10:56:14 +00:00
'letter_spec',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'letter_template',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'link_service_to_organisation',
'manage_org_users',
Add a new endpoint for managing a folder, use it to rename folder - Add a GET / POST view: manage template folder - Add a template for that view, where a user can rename their folder - Add an API client method for updating a folder - Test the new feature, including the test that service without permissions cannot manage a folder
2018-11-12 16:37:37 +00:00
'manage_template_folder',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'manage_users',
'monthly',
'new_password',
'old_integration_testing',
'old_roadmap',
'old_service_dashboard',
'old_terms',
'old_using_notify',
'organisation_dashboard',
move trial mode services from org dashboard to separate page the new page is platform admin only, and also has search built in also, split test_organisation_invites into two files
2019-05-21 14:56:15 +01:00
'organisation_trial_mode_services',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'organisation_settings',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'organisation_preview_email_branding',
'organisation_preview_letter_branding',
Excluding the privacy page from the navigation stuff
2018-05-23 14:33:29 +01:00
'privacy',
Add URLs to download the agreement without login So that we can share these URLs in an email we’re sending out.
2018-05-08 14:06:26 +01:00
'public_agreement',
'public_download_agreement',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'received_text_messages_callback',
'redact_template',
'register',
'register_from_invite',
'register_from_org_invite',
'registration_continue',
'remove_user_from_organisation',
'remove_user_from_service',
'request_to_go_live',
'resend_email_link',
'resend_email_verification',
'resume_service',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letter_summary',
Add a page for each report It’s useful to get some kind of preview of the report before you download it. And if there’s only a few letters in there then you might not even need to download it at all. For teams with lots of letters we don’t want the page to load too slowly so let’s cap the number of displayed items to 50, same as previewing a spreadsheet.
2019-12-31 13:27:27 +00:00
'returned_letters',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letters_report',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'revoke_api_key',
'send_messages',
'send_notification',
'send_one_off',
input letter address data in a single block rather than in multiple placeholders - this is the first step towards making postcodes non-required, which is the first step towards international letters. they still populate address_line_# and postcode fields under the hood - to keep validation working the same, the last line always goes into `postcode`. the form normalises whitespace, removes extra new lines, and enforces that you have between three and seven lines. if the letter repeats address placeholders further down (eg "Dear ((address_line_1))"), then it'll fill those in as well. It'll still prompt you to fill them in, but they'll be pre-filled.
2020-03-10 15:12:19 +00:00
'send_one_off_letter_address',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'send_one_off_step',
'send_test',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.send_test_preview',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'send_test_step',
Add endpoint to redirect from contact list to send In order to use a contact list we’re going to put you in the normal upload a spreadsheet journey. Except without having to upload again. So this commit adds an endpoint that takes the file from the contact list bucket, puts it in the same place it would have gone if you’d uploaded it, then sends you on your way.
2020-03-13 14:38:43 +00:00
'send_from_contact_list',
Allow uploaded letters to be sent if valid Added a send button which only appears on the page if the query string indicates that the PDF is valid. Before actually sending, we check that the service has the right permissions and that the metadata for the letter confirms the letter is valid (because the query string can be changed).
2019-09-09 12:22:52 +01:00
'send_uploaded_letter',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_add_email_reply_to',
'service_add_letter_contact',
'service_add_sms_sender',
Add service-specific versions of agreement page Our usability testing found that jumping out of the service when going to download the agreement made it difficult for people to find their way back to the ‘Request to go live’ page. This commit adds a duplicate, service-specific versions of these pages which have the same content but: - keep the service navigation - have a link back to the ‘Request to go live’ page
2019-05-01 08:29:32 +01:00
'service_agreement',
Add pages to let users accept the agreement online At the moment, the process for accepting the data sharing and financial agreement is: 1. download a pdf * print it out * get someone to sign it * scan it * email it back to us * we rename the file and save it in Google Drive * we then update the organisation to say the MOU is signed * sometimes we also: * print it out and get it counter-signed * scan it again * email it back to the service Let's not do that any more. When the first service for an organisation that doesn't have the agreement in place is in the process of going live, then they should be able to accept the agreement online as part of the go live flow. This commit adds the pages that let someone do that. Where the checklist shows the agreement as **[not completed]** then they can follow a link where they can download it (as happens now). From here, they should then also be able to provide some info to accept it. The info that we need is: **Version** – because we version the agreements occasionally, we need to know which version they are accepting. It may not be the latest one if they downloaded it a while ago and it took time to be signed off **Who is accepting the agreement** – this will often be someone in the finance team, and not necessarily a team member, so we should let the person either accept as themselves, or on behalf of someone else. If it's on behalf of someone else we need to the name and email address of that person so we have that on record. Obvs if it's them accepting it themselves, we have that already (so we just store their user ID and not their name or email address). We then replay the collected info back in a sort of legally binding kind of way pulling in the organisation name too. The wording we’re using is inspired by what GOV.UK Pay have. Then there’s a big green button they can click to accept the agreement, which stores their user ID and and timestamp.
2019-06-18 14:24:29 +01:00
'service_accept_agreement',
'service_confirm_agreement',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_confirm_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_confirm_delete_letter_contact',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_confirm_delete_sms_sender',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_dashboard',
'service_dashboard_updates',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_delete_letter_contact',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_delete_sms_sender',
Determine agreement by service not user’s org A user might not have a guessable organisation type, even if the service they’re working on does have an organisation set. This can happen for users with @nhs.net email addresses, for example.
2019-07-02 17:04:26 +01:00
'service_download_agreement',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_edit_email_reply_to',
'service_edit_letter_contact',
'service_edit_sms_sender',
'service_email_reply_to',
'service_letter_contact_details',
Allow deleting default letter contact blocks It’s possible to delete default letter contact blocks because there is a fallback – having a blank letter contact block. This is different to SMS senders and reply to addresses. For this to make sense it also means: - adding the ‘blank’ letter contact block to the list of letter contact blocks - having a way of setting the default back to being blank
2019-07-05 13:17:48 +01:00
'service_make_blank_default_letter_contact',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_name_change',
'service_name_change_confirm',
Fixes for tests broken by changes - corrects target page for set_email_branding to new preview step instead of itself - removed check for helper method being called in email page test - updates expected result for test of global headers to include changes to `frame-src` - updates navigation config with brand preview page
2018-08-03 17:39:58 +01:00
'service_preview_email_branding',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'service_preview_letter_branding',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_set_auth_type',
Let users switch channels on and off by themselves We let people do this for letters already. We should let them do it for emails and texts too, rather than have to email us.
2019-01-29 14:51:31 +00:00
'service_set_channel',
Send files by email on for everyone and only depending on service having contact details set up. Display not set up yet for send files by email row when contact_link not set up
2020-02-25 11:27:43 +00:00
'send_files_by_email_contact_details',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_set_email_branding',
'service_set_inbound_number',
'service_set_inbound_sms',
'service_set_international_sms',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'service_set_letter_branding',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_set_letters',
'service_set_reply_to_email',
'service_set_sms_prefix',
'service_settings',
'service_sms_senders',
Allow excluding services from live services count Adds a front end for: https://github.com/alphagov/notifications-api/pull/2417 > Sometimes we have to make a few services for what really is one > service, for example GOV.UK Pay and GOV.UK Pay Direct Debit. We also > have our own test services which aren’t included in the count of live > services. We currently count these as one service by not including > them in the beta partners spreadsheet.
2019-03-25 14:46:42 +00:00
'service_switch_count_as_live',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'service_switch_live',
Replace platform admin service setting buttons with forms Most of the existing platform admin buttons on the service settings page used to issue GET requests to switch service settings. This means they weren't protected by CSRF. On top of that as our number of service permissions increases over time a lot of buttons on the page made it hard to work with. To fix these issues we replace most of the buttons with rows in the platform admin settings table. Each setting has a 'Change' link that leads to a page with an On/Off switch form. This removes "research mode" switch completely since we're planning to deprecate it in the future and we don't expect to switch any new services into research mode at the moment. Most service permissions are now handled by a shared endpoint that is parameterized with the permission name. Some permissions that require some additional logic before they can be toggled (like document upload, which requires setting a contact address) have separate initial endpoints that redirect to `set_service_permission`. "Archive", "Suspend" and "Resume" actions are kept as buttons since they display a confirmation banner (which is a CSRF-protected form) and they're not easily represented as an On/Off switch.
2019-02-18 16:56:43 +00:00
'service_set_permission',
No emails, texts or letters for broadcast services To make the interface as simple as possible we don’t want to mix up sending other types of communication where services have the broadcast permission. This commit removes the other permissions once a service has been given the broadcast permission by a platform admin user.
2020-07-13 08:56:57 +01:00
'service_set_broadcast_permission',
Verify email address when editing reply-to address Also fix the tests
2019-05-16 17:05:55 +01:00
'service_verify_reply_to_address',
'service_verify_reply_to_address_updates',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'services_or_dashboard',
'set_free_sms_allowance',
'set_sender',
'set_template_sender',
'show_accounts_or_dashboard',
'sign_out',
'start_job',
'start_tour',
'styleguide',
'submit_request_to_go_live',
'template_history',
'template_usage',
'trial_mode',
Let users upload a contact list to use later We increasingly have teams wanting to do business-continuity type messaging. They might be without access to their normal systems, which is where they would otherwise go to get the list of email addresses or phone numbers. So we want to give them a place in Notify where they can store their spreadsheets and use them at a later date. For the initial pass we’re going to scope this to only allowing spreadsheets with one column, ie just phone numbers/email addresses. This is because: - it minimises the amount of personal info we’re storing - it reduces the chance of getting a placeholder error when you go to send the message, which is probably a high-stress situation where you might not be able to re-generate the file The code for this is mostly copied from the existing upload CSV journey. It’s quite duplicative, but that’s what I needed to do to get this out quickly. There are opportunities for refactoring later. Similarly, I would have liked to split this up into better commit messages, but it really was a case of just bashing code out until it worked 😳 This commit does not: - implement the ‘view a contact list page’ (it just has a placeholder because the API isn’t ready at the moment) - link to this page (because it’s not ready to use yet)
2020-03-12 16:13:18 +00:00
'upload_contact_list',
'check_contact_list',
'save_contact_list',
'contact_list',
Let users delete a contact list Follows our standard pattern of confirming with a red banner for actions that are destructive.
2020-03-18 13:37:39 +00:00
'delete_contact_list',
Add letter upload form which redirects to blank preview page Added a form to upload a single letter. Currently this only uses the form to validate that a file is submitted and that the file is a PDF. If either of these validations fail, the form will display an error. Otherwise, we redirect to a new preview page which just has the filename as the heading for now.
2019-09-06 10:39:23 +01:00
'upload_letter',
'uploaded_letter_preview',
Add page to show all uploaded letters Because we won’t be showing uploaded letters individually on the uploads page any more we need a way of listing them. This should be by printing day, to match how we’re grouping them on the uploads page. This code reuses the notifications.html template, but flips the precedence of the filename and recipient because I reckon when you’re looking at uploads you’re thinking filename-first.
2020-05-11 10:52:43 +01:00
'uploaded_letters',
Add 'Uploads' hub and navigation The uploads hub is just a page with text for now - there are no actions available on the page. It is linked to from a new 'Uploads' menu item on the left of the page which is only visible if your service has the `letter` and `upload_letters` permissions and if the current user has permissions to send messages.
2019-08-09 08:44:11 +01:00
'uploads',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'usage',
'view_job',
'view_job_csv',
'view_job_updates',
'view_jobs',
'view_letter_notification_as_preview',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_letter_template_preview',
Show letter preview once file is uploaded This shows the sanitised letter preview if the file had no validation errors or the preview with the overlay if it failed validation.
2019-09-09 10:59:32 +01:00
'view_letter_upload_as_preview',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'view_notification',
'view_notification_updates',
'view_notifications',
'view_notifications_csv',
'view_template',
'view_template_version',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_template_version_preview',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
'view_template_versions',
Rename endpoint to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:03:40 +01:00
'guest_list',
Rename URL to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:07:29 +01:00
'old_guest_list',
Update who_its_for to who_can_use_notify
2020-05-20 15:54:15 +01:00
'who_can_use_notify',
Redirect old URL
2020-05-21 11:17:44 +01:00
'who_its_for',
Add a tour for users new to broadcast services This is an initial, prototype-quality attempt at introducing some kind of tour for users new to broadcasting. A lot of the users we’re speaking to don’t have a good concept of what broadcasting means, which is causing usability problems down the line. We did a similar thing in the early days of Notify to explain the concept of message templates and personalisation.
2020-08-03 13:37:34 +01:00
'broadcast_tour',
Add a dashboard for broadcast services This is just a placeholder for now
2020-07-08 11:34:16 +01:00
'broadcast_dashboard',
Make the broadcast dashboard update via AJAX Same technique as we use for other pages that update via AJAX. I’ve split the page up into separate chunks because the DiffDOM library we use finds it easier to work out what’s changed when there are fewer elements/a shallower tree.
2020-07-14 13:39:29 +01:00
'broadcast_dashboard_updates',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'broadcast',
'preview_broadcast_areas',
'choose_broadcast_library',
'choose_broadcast_area',
Let users select electoral wards of local authorities If a library has groups, we should show a link instead of selecting the group directly. Then we can give the user the choice of selecting the whole of that group, or specific areas within the group. For now the only libraries we have with groups are local authorities, which group electoral wards.
2020-07-31 16:20:37 +01:00
'choose_broadcast_sub_area',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'remove_broadcast_area',
'preview_broadcast_message',
Add a page to view a single broadcast This commit adds a page to view a single broadcast. This is important for two reasons: - users need an audit of what happened when, and who else was involved in approving or cancelling a broadcast - we need a place to put actions (approving, cancelling) on a broadcast so that you can confirm details of the message and the areas before performing the action
2020-07-10 14:06:00 +01:00
'view_broadcast_message',
Add button to approve broadcast Since new broadcasts will go into `pending-approval`, we now need a way of approving them. This commit adds a button to this page to start (or approve) the broadcast. This button is wrapped in a bordered box, to emphasise that it’s something consequential.
2020-07-17 08:07:44 +01:00
'approve_broadcast_message',
Add a link to reject a broadcast If a broadcast definitely shouldn’t go out (for example because it has a spelling mistake or is going to the wrong areas) then we should have a way of removing it. Once it’s removed no-one else can approve it, and it isn’t cluttering up the dashboard. This is a link (because it’s a secondary action) and red (because it’s destructive, in that it’s throwing away someone’s work).
2020-07-17 08:07:44 +01:00
'reject_broadcast_message',
Allow broadcasts to be cancelled Currently this is a `get` request from the dashboard. Once we have a page for viewing an individual broadcast it should probably show there instead and be a `get`/confirm/`post` loop like for deleting a template.
2020-07-10 09:16:36 +01:00
'cancel_broadcast_message',
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
}
Use header component for masthead Replaces the following blocks/variables with the `header` block filled by the `header` component: - header_class - proposition_header - global_header_text - homepage_url Also rewrites code that selects header nav items The original code inserts a class name to mark the nav item as selected. The GOVUK Frontend header just needs a boolean to be passed to indicate an item is selected. This uses the `header_navigation.is_selected` method, as before, but changes its return value to a boolean.
2019-10-09 16:00:45 +01:00
# header HTML now comes from GOVUK Frontend so requires a boolean, not an attribute
def is_selected(self, navigation_item):
Fix issues raised in pull request Includes: - replacing of conditional with statement that returns the same values - making lins to GDS page actually go there
2019-10-30 10:17:32 +00:00
return request.endpoint in self.mapping[navigation_item]
Use header component for masthead Replaces the following blocks/variables with the `header` block filled by the `header` component: - header_class - proposition_header - global_header_text - homepage_url Also rewrites code that selects header nav items The original code inserts a class name to mark the nav item as selected. The GOVUK Frontend header just needs a boolean to be passed to indicate an item is selected. This uses the `header_navigation.is_selected` method, as before, but changes its return value to a boolean.
2019-10-09 16:00:45 +01:00
Highlight selected item in proposition navigation It is standard practice when using GOV.UK template to highlight the selected navigation item in the propositional navigation (black bar) by colouring it blue. This commit adds a new subclass of `Navigation` with the mapping needed to decide which pages belong to which item in the navigation (or none at all).
2018-04-25 11:11:37 +01:00
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
class MainNavigation(Navigation):
mapping = {
'dashboard': {
Add a tour for users new to broadcast services This is an initial, prototype-quality attempt at introducing some kind of tour for users new to broadcasting. A lot of the users we’re speaking to don’t have a good concept of what broadcasting means, which is causing usability problems down the line. We did a similar thing in the early days of Notify to explain the concept of message templates and personalisation.
2020-08-03 13:37:34 +01:00
'broadcast_tour',
Add a dashboard for broadcast services This is just a placeholder for now
2020-07-08 11:34:16 +01:00
'broadcast_dashboard',
Make the broadcast dashboard update via AJAX Same technique as we use for other pages that update via AJAX. I’ve split the page up into separate chunks because the DiffDOM library we use finds it easier to work out what’s changed when there are fewer elements/a shallower tree.
2020-07-14 13:39:29 +01:00
'broadcast_dashboard_updates',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'conversation',
'inbox',
'monthly',
Make dashboard navigation active for returned letters
2020-02-17 10:23:59 +00:00
'returned_letter_summary',
'returned_letters',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_dashboard',
'template_usage',
'view_notification',
'view_notifications',
},
'templates': {
'action_blocked',
'add_service_template',
'check_messages',
'check_notification',
Add a page to choose a contact list You’ll be able to use a contact list by first choosing a template, then choosing the list you want to use. At the moment this shows all lists, not just the ones that are compatible with your template.
2020-03-13 17:51:22 +00:00
'choose_from_contact_list',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'choose_template',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'choose_template_to_copy',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'confirm_redact_template',
'conversation_reply',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'copy_template',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'delete_service_template',
'edit_service_template',
Edit template postage from a separate view
2019-01-29 15:43:59 +00:00
'edit_template_postage',
Add a new endpoint for managing a folder, use it to rename folder - Add a GET / POST view: manage template folder - Add a template for that view, where a user can rename their folder - Add an API client method for updating a folder - Test the new feature, including the test that service without permissions cannot manage a folder
2018-11-12 16:37:37 +00:00
'manage_template_folder',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'send_messages',
'send_one_off',
input letter address data in a single block rather than in multiple placeholders - this is the first step towards making postcodes non-required, which is the first step towards international letters. they still populate address_line_# and postcode fields under the hood - to keep validation working the same, the last line always goes into `postcode`. the form normalises whitespace, removes extra new lines, and enforces that you have between three and seven lines. if the letter repeats address placeholders further down (eg "Dear ((address_line_1))"), then it'll fill those in as well. It'll still prompt you to fill them in, but they'll be pre-filled.
2020-03-10 15:12:19 +00:00
'send_one_off_letter_address',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'send_one_off_step',
'send_test',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.send_test_preview',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'send_test_step',
'set_sender',
'set_template_sender',
'view_template',
'view_template_version',
'view_template_versions',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'broadcast',
'preview_broadcast_areas',
'choose_broadcast_library',
'choose_broadcast_area',
Let users select electoral wards of local authorities If a library has groups, we should show a link instead of selecting the group directly. Then we can give the user the choice of selecting the whole of that group, or specific areas within the group. For now the only libraries we have with groups are local authorities, which group electoral wards.
2020-07-31 16:20:37 +01:00
'choose_broadcast_sub_area',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'remove_broadcast_area',
'preview_broadcast_message',
Add a page to view a single broadcast This commit adds a page to view a single broadcast. This is important for two reasons: - users need an audit of what happened when, and who else was involved in approving or cancelling a broadcast - we need a place to put actions (approving, cancelling) on a broadcast so that you can confirm details of the message and the areas before performing the action
2020-07-10 14:06:00 +01:00
'view_broadcast_message',
Add button to approve broadcast Since new broadcasts will go into `pending-approval`, we now need a way of approving them. This commit adds a button to this page to start (or approve) the broadcast. This button is wrapped in a bordered box, to emphasise that it’s something consequential.
2020-07-17 08:07:44 +01:00
'approve_broadcast_message',
Add a link to reject a broadcast If a broadcast definitely shouldn’t go out (for example because it has a spelling mistake or is going to the wrong areas) then we should have a way of removing it. Once it’s removed no-one else can approve it, and it isn’t cluttering up the dashboard. This is a link (because it’s a secondary action) and red (because it’s destructive, in that it’s throwing away someone’s work).
2020-07-17 08:07:44 +01:00
'reject_broadcast_message',
Allow broadcasts to be cancelled Currently this is a `get` request from the dashboard. Once we have a page for viewing an individual broadcast it should probably show there instead and be a `get`/confirm/`post` loop like for deleting a template.
2020-07-10 09:16:36 +01:00
'cancel_broadcast_message',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
},
Add 'Uploads' hub and navigation The uploads hub is just a page with text for now - there are no actions available on the page. It is linked to from a new 'Uploads' menu item on the left of the page which is only visible if your service has the `letter` and `upload_letters` permissions and if the current user has permissions to send messages.
2019-08-09 08:44:11 +01:00
'uploads': {
Let users upload a contact list to use later We increasingly have teams wanting to do business-continuity type messaging. They might be without access to their normal systems, which is where they would otherwise go to get the list of email addresses or phone numbers. So we want to give them a place in Notify where they can store their spreadsheets and use them at a later date. For the initial pass we’re going to scope this to only allowing spreadsheets with one column, ie just phone numbers/email addresses. This is because: - it minimises the amount of personal info we’re storing - it reduces the chance of getting a placeholder error when you go to send the message, which is probably a high-stress situation where you might not be able to re-generate the file The code for this is mostly copied from the existing upload CSV journey. It’s quite duplicative, but that’s what I needed to do to get this out quickly. There are opportunities for refactoring later. Similarly, I would have liked to split this up into better commit messages, but it really was a case of just bashing code out until it worked 😳 This commit does not: - implement the ‘view a contact list page’ (it just has a placeholder because the API isn’t ready at the moment) - link to this page (because it’s not ready to use yet)
2020-03-12 16:13:18 +00:00
'upload_contact_list',
'check_contact_list',
'save_contact_list',
'contact_list',
Let users delete a contact list Follows our standard pattern of confirming with a red banner for actions that are destructive.
2020-03-18 13:37:39 +00:00
'delete_contact_list',
Add letter upload form which redirects to blank preview page Added a form to upload a single letter. Currently this only uses the form to validate that a file is submitted and that the file is a PDF. If either of these validations fail, the form will display an error. Otherwise, we redirect to a new preview page which just has the filename as the heading for now.
2019-09-06 10:39:23 +01:00
'upload_letter',
'uploaded_letter_preview',
Add page to show all uploaded letters Because we won’t be showing uploaded letters individually on the uploads page any more we need a way of listing them. This should be by printing day, to match how we’re grouping them on the uploads page. This code reuses the notifications.html template, but flips the precedence of the filename and recipient because I reckon when you’re looking at uploads you’re thinking filename-first.
2020-05-11 10:52:43 +01:00
'uploaded_letters',
Add 'Uploads' hub and navigation The uploads hub is just a page with text for now - there are no actions available on the page. It is linked to from a new 'Uploads' menu item on the left of the page which is only visible if your service has the `letter` and `upload_letters` permissions and if the current user has permissions to send messages.
2019-08-09 08:44:11 +01:00
'uploads',
Fix navigation around uploads and jobs The uploads and jobs page should start showing in the _Uploads_ menu on the left hand side. If you’ve navigated to a job from the uploads page (ie you haven’t got to that page because you’ve just sent the job) then you should see a link back to the uploads page.
2020-03-03 14:27:13 +00:00
'view_job',
'view_jobs',
Add 'Uploads' hub and navigation The uploads hub is just a page with text for now - there are no actions available on the page. It is linked to from a new 'Uploads' menu item on the left of the page which is only visible if your service has the `letter` and `upload_letters` permissions and if the current user has permissions to send messages.
2019-08-09 08:44:11 +01:00
},
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'team-members': {
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'confirm_edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'confirm_edit_user_mobile_number',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'edit_user_mobile_number',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'edit_user_permissions',
'invite_user',
'manage_users',
'remove_user_from_service',
},
'usage': {
'usage',
},
'settings': {
Let GP surgeries create their own organisations We have a bunch of GP surgeries who want to go live. They don’t automatically assigned to organisations. So this means a lot of back and forth to get these organisations set up, and then the service has to re-request to go live, and… it’s painful. Instead, let’s let GPs create their own organisations, by confirming the name of their organisation before going on to letting them accept the agreement.
2019-09-04 16:27:25 +01:00
'add_organisation_from_gp_service',
Let NHS Trusts and CCGs choose own organisation All we do via support is ask which organisation they work for and manually assign their service to it. This commit makes that process self service. We think we have all the trusts and clinical commissioning groups loaded into the database now. This will make the go live process smoother for these teams.
2019-09-05 16:18:02 +01:00
'add_organisation_from_nhs_local_service',
Add page where users can say they want branding At the moment branding is an undocumented feature. We get a bunch of support tickets from teams asking its possible. This commit: - lets people know it’s possible, and what the options are - is the first step towards making this process as self-service as possible In some cases we will be able to infer a user’s organisation from there email address, and Google image search their logo. So the experience for them is that they press a button and government just sorts it out for you (also known as "the dream"). In other cases we will have to get back to people asking for a copy of their logo, or to find out about their service, but this is what we have to do at the moment anyway.
2018-05-18 14:05:48 +01:00
'branding_request',
Move the ‘estimated usage’ questions We get a bunch of requests to go live where people have told us they're going to send email but there is no email reply-to address present. These come from 2 scenarios: 1. when there are email templates, and no reply to address – but they ignore the checklist 2. when there are no email templates (yet) but they provide anticipated volumes for email At the moment we only auto-check for a reply to address when they have email templates. And because the question about anticipated volumes follows the checklist, you'll get a checklist that passes (reply addresses not required as no templates present) - but your future intent that differs (reply address IS required because you have anticipated volumes). So let’s bring the request for anticipated volumes into the checklist, that way we can dynamically add the requirement for a reply to address if they say they will send email but don't have templates yet. We should begin storing it in the database against the service to stop people having to re-enter it each time they try to complete the go live screens. This also means moving the ‘consent to research question’ along with the questions about volume, because - we want people to answer both before going live - we don’t want to clutter up the summary page by asking questions there too
2019-02-15 11:03:19 +00:00
'estimate_usage',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'link_service_to_organisation',
'request_to_go_live',
'service_add_email_reply_to',
'service_add_letter_contact',
'service_add_sms_sender',
Add service-specific versions of agreement page Our usability testing found that jumping out of the service when going to download the agreement made it difficult for people to find their way back to the ‘Request to go live’ page. This commit adds a duplicate, service-specific versions of these pages which have the same content but: - keep the service navigation - have a link back to the ‘Request to go live’ page
2019-05-01 08:29:32 +01:00
'service_agreement',
Add pages to let users accept the agreement online At the moment, the process for accepting the data sharing and financial agreement is: 1. download a pdf * print it out * get someone to sign it * scan it * email it back to us * we rename the file and save it in Google Drive * we then update the organisation to say the MOU is signed * sometimes we also: * print it out and get it counter-signed * scan it again * email it back to the service Let's not do that any more. When the first service for an organisation that doesn't have the agreement in place is in the process of going live, then they should be able to accept the agreement online as part of the go live flow. This commit adds the pages that let someone do that. Where the checklist shows the agreement as **[not completed]** then they can follow a link where they can download it (as happens now). From here, they should then also be able to provide some info to accept it. The info that we need is: **Version** – because we version the agreements occasionally, we need to know which version they are accepting. It may not be the latest one if they downloaded it a while ago and it took time to be signed off **Who is accepting the agreement** – this will often be someone in the finance team, and not necessarily a team member, so we should let the person either accept as themselves, or on behalf of someone else. If it's on behalf of someone else we need to the name and email address of that person so we have that on record. Obvs if it's them accepting it themselves, we have that already (so we just store their user ID and not their name or email address). We then replay the collected info back in a sort of legally binding kind of way pulling in the organisation name too. The wording we’re using is inspired by what GOV.UK Pay have. Then there’s a big green button they can click to accept the agreement, which stores their user ID and and timestamp.
2019-06-18 14:24:29 +01:00
'service_accept_agreement',
'service_confirm_agreement',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_confirm_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_confirm_delete_letter_contact',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_confirm_delete_sms_sender',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_edit_email_reply_to',
'service_edit_letter_contact',
'service_edit_sms_sender',
'service_email_reply_to',
'service_letter_contact_details',
Allow deleting default letter contact blocks It’s possible to delete default letter contact blocks because there is a fallback – having a blank letter contact block. This is different to SMS senders and reply to addresses. For this to make sense it also means: - adding the ‘blank’ letter contact block to the list of letter contact blocks - having a way of setting the default back to being blank
2019-07-05 13:17:48 +01:00
'service_make_blank_default_letter_contact',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_name_change',
'service_name_change_confirm',
Fixes for tests broken by changes - corrects target page for set_email_branding to new preview step instead of itself - removed check for helper method being called in email page test - updates expected result for test of global headers to include changes to `frame-src` - updates navigation config with brand preview page
2018-08-03 17:39:58 +01:00
'service_preview_email_branding',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'service_preview_letter_branding',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_set_auth_type',
Let users switch channels on and off by themselves We let people do this for letters already. We should let them do it for emails and texts too, rather than have to email us.
2019-01-29 14:51:31 +00:00
'service_set_channel',
Send files by email on for everyone and only depending on service having contact details set up. Display not set up yet for send files by email row when contact_link not set up
2020-02-25 11:27:43 +00:00
'send_files_by_email_contact_details',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_set_email_branding',
'service_set_inbound_number',
'service_set_inbound_sms',
'service_set_international_sms',
'service_set_letters',
'service_set_reply_to_email',
'service_set_sms_prefix',
Verify email address when editing reply-to address Also fix the tests
2019-05-16 17:05:55 +01:00
'service_verify_reply_to_address',
'service_verify_reply_to_address_updates',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_settings',
'service_sms_senders',
'set_free_sms_allowance',
fix request letter branding page (it can now have a null type). also fix nav.py
2019-02-05 16:33:36 +00:00
'service_set_letter_branding',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'submit_request_to_go_live',
},
'api-integration': {
'api_callbacks',
'api_documentation',
'api_integration',
'api_keys',
'create_api_key',
'delivery_status_callback',
'received_text_messages_callback',
'revoke_api_key',
Rename endpoint to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:03:40 +01:00
'guest_list',
Rename URL to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:07:29 +01:00
'old_guest_list',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
},
}
exclude = {
'accept_invite',
'accept_org_invite',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'add_data_retention',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'add_organisation',
'add_service',
'archive_service',
Add page to archive user Users can only be archived by Platform Admin from the user page (/users/<user_id>). This removes them from all services and orgs and updates their details.
2019-05-22 11:38:47 +01:00
'archive_user',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'bat_phone',
'callbacks',
'cancel_invited_org_user',
'cancel_invited_user',
'cancel_job',
Add link to cancel letters Added a link to cancel letters from the letter notification pages if the letter is still able to be cancelled. Clicking on this link will show a confirmation box, and will then cancel the letter if the user confirms.
2018-12-05 10:58:27 +00:00
'cancel_letter',
Letter job can't be cancelled if already printed Non-cancellable letter statuses mean that it's too late to cancel a job
2019-06-18 18:00:36 +01:00
'cancel_letter_job',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'check_and_resend_text_code',
'check_and_resend_verification_code',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_messages_preview',
'no_cookie.check_notification_preview',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'choose_account',
'choose_service',
add clear cache platform admin page a form that allows you to clear entries from the cache for all of either users, services or templates. It'll tell you the largest amount of keys deleted, since there are multiple keys associated with each model.
2019-02-15 10:27:38 +00:00
'clear_cache',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'confirm_edit_organisation_name',
'conversation_reply_with_template',
'conversation_updates',
'cookies',
'create_email_branding',
Add page to create new letter branding This has a form with 3 fields - the file upload field, logo name, and an optional logo domain. Logos need to be uploaded in `.svg` format and we then convert this to `.png` format and upload both file types to S3 as well as saving the letter branding details in the database.
2019-01-31 16:56:35 +00:00
'create_letter_branding',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'data_retention',
Build delete folder endpoint that calls template_folders_api_client
2018-11-13 17:56:47 +00:00
'delete_template_folder',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'delivery_and_failure',
'design_content',
'documentation',
Add an endpoint to download a contact list In case you need to download it, modify it, and re-upload it when you don’t have access to the existing list.
2020-03-15 19:13:07 +00:00
'download_contact_list',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'download_notifications_csv',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'edit_data_retention',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_agreement',
'edit_organisation_crown_status',
'edit_organisation_email_branding',
'edit_organisation_domains',
Allow custom notes when service goes live This adds an option on the organisation settings page to add 'request_to_go_live_notes'. When a service belonging to this organisation requests to go live, any go live notes for the organisation will be added to the Zendesk ticket in the 'Agreement signed' section.
2019-05-13 14:50:40 +01:00
'edit_organisation_go_live_notes',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_letter_branding',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'edit_organisation_name',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_type',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'edit_provider',
Add page showing priority of two SMS providers It’s not very useful to know the priority of one provider without knowing the other. And these pages were never really designed, so they weren’t super easy to understand anyway. This commit adds a page that takes the first two text message providers and shows their relative priority against each other. It follows the design of the events page, as a pattern for showing a log of historical events.
2019-12-02 14:29:34 +00:00
'edit_sms_provider_ratio',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'edit_user_org_permissions',
'email_branding',
'email_not_received',
'email_template',
'error',
'features',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'features_email',
'features_letters',
'features_sms',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'feedback',
Find services by name or partial name
2019-08-13 16:25:26 +01:00
'find_services_by_name',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'find_users_by_email',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'forgot_password',
'get_example_csv',
'get_notifications_as_json',
Add endpoint for new page
2019-10-17 16:15:28 +01:00
'get_started',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'get_started_old',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'go_to_dashboard_after_tour',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'guidance_index',
'branding_and_customisation',
'create_and_send_messages',
'edit_and_format_messages',
'send_files_by_email',
'upload_a_letter',
Move service history into it own file We’re going to do some work on this page, let’s put it in a sensible place first before we add a bunch more code to the wrong place.
2019-10-18 09:18:51 +01:00
'history',
Add ‘How to pay’ page Content from https://docs.google.com/document/d/1uIFW8c7Vk0-FQ-d8H1FmNZLHKn_tOXWg5oUL8bbcZzw/edit?ts=5ced1ae4#
2019-06-04 10:43:15 +01:00
'how_to_pay',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'inbound_sms_admin',
'inbox_download',
'inbox_updates',
'index',
'information_risk_management',
'information_security',
'integration_testing',
'invite_org_user',
Add '/letter-branding' page to show all letter brands This is a platform admin page which lists all letter brands and their domain. Once the page to edit a letter brand has been created, each brand will link to its edit page, but for now this is just a list of brand names and domains.
2019-02-07 16:16:22 +00:00
'letter_branding',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.letter_branding_preview_image',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'live_services',
Get live services csv report
2019-04-24 16:23:12 +01:00
'live_services_csv',
Add a redirect for the letter specification This way we have a URL we can give people that always points to the latest version of the spec. And it makes our code more Flask-idiomatic to be using `url_for` to be generating a URL, rather than passing around a constant.
2020-01-15 10:56:14 +00:00
'letter_spec',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'letter_template',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'message_status',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'manage_org_users',
'new_password',
Add new report to show monthly notification stats for each service This report will be used by the engagement team. There is a form to give a start and end date for the report, and the form is then downloaded as a CSV file when the form is submitted.
2019-07-22 13:09:03 +01:00
'notifications_sent_by_service',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'old_integration_testing',
'old_roadmap',
'old_service_dashboard',
'old_terms',
'old_using_notify',
'organisation_dashboard',
move trial mode services from org dashboard to separate page the new page is platform admin only, and also has search built in also, split test_organisation_invites into two files
2019-05-21 14:56:15 +01:00
'organisation_trial_mode_services',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'organisation_preview_email_branding',
'organisation_preview_letter_branding',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'organisation_settings',
'organisations',
Provide Performance Platform report as Excel file This is the format we need to upload it in, so this means not having to manually re-save it as Excel.
2019-05-03 14:32:02 +01:00
'performance_platform_xlsx',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'platform_admin',
When someone complains about an email from the platform we get a callback from SES. A new platform admin page Email complaints has been added to surface those complaints. Eventually the complaints will be visible to the services so they can remove the email address from their mailing list. Next thing to implement is "x email complaints" warning on the platform admin summary page.
2018-06-06 15:22:48 +01:00
'platform_admin_list_complaints',
Basic reports page, returns 200 and is visible in PA sidebar
2019-04-24 10:27:57 +01:00
'platform_admin_reports',
Add a platform admin page to submit returned letter references A platform admin form accepts a list of references (one per line) received from DVLA and sends them to the API to update notification statuses. References we get from DVLA start with `NOTIFY00\d`, which isn't part of the reference we store in the database, so we remove them before sending the data to the API. The new `returned-letter` status should be treated as `delivered` for now until we decide a way to display returned letters to users.
2018-09-06 16:34:23 +01:00
'platform_admin_returned_letters',
Reduce usage of the platform admin index page This page is slow to load which means: - it’s annoying for us - it’s potentially causing load on the database This commit does two things to reduce the amount we’re unnecessarily looking at this page: 1. Avoid redirecting to it when signing in as a platform admin user 2. Don’t go directly to it when clicking ‘platform admin’ at the top, but instead show a holding page (there’s a fair chance you’ve clicked that link in order to go and manage some email branding or find a user, not wait for stats to load)
2020-03-19 10:49:40 +00:00
'platform_admin_splash_page',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'pricing',
Excluding the privacy page from the navigation stuff
2018-05-23 14:33:29 +01:00
'privacy',
Add URLs to download the agreement without login So that we can share these URLs in an email we’re sending out.
2018-05-08 14:06:26 +01:00
'public_agreement',
'public_download_agreement',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'redact_template',
'register',
'register_from_invite',
'register_from_org_invite',
'registration_continue',
'remove_user_from_organisation',
'resend_email_link',
'resend_email_verification',
'resume_service',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letters_report',
Send 2fa email and move user to waiting page when they need to re-validate email access
2020-01-27 18:10:45 +00:00
'revalidate_email_sent',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'roadmap',
'security',
'send_notification',
Add endpoint to redirect from contact list to send In order to use a contact list we’re going to put you in the normal upload a spreadsheet journey. Except without having to upload again. So this commit adds an endpoint that takes the file from the contact list bucket, puts it in the same place it would have gone if you’d uploaded it, then sends you on your way.
2020-03-13 14:38:43 +00:00
'send_from_contact_list',
Allow uploaded letters to be sent if valid Added a send button which only appears on the page if the query string indicates that the PDF is valid. Before actually sending, we check that the service has the right permissions and that the metadata for the letter confirms the letter is valid (because the query string can be changed).
2019-09-09 12:22:52 +01:00
'send_uploaded_letter',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_dashboard_updates',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_delete_letter_contact',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_delete_sms_sender',
Determine agreement by service not user’s org A user might not have a guessable organisation type, even if the service they’re working on does have an organisation set. This can happen for users with @nhs.net email addresses, for example.
2019-07-02 17:04:26 +01:00
'service_download_agreement',
Allow excluding services from live services count Adds a front end for: https://github.com/alphagov/notifications-api/pull/2417 > Sometimes we have to make a few services for what really is one > service, for example GOV.UK Pay and GOV.UK Pay Direct Debit. We also > have our own test services which aren’t included in the count of live > services. We currently count these as one service by not including > them in the beta partners spreadsheet.
2019-03-25 14:46:42 +00:00
'service_switch_count_as_live',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'service_switch_live',
Replace platform admin service setting buttons with forms Most of the existing platform admin buttons on the service settings page used to issue GET requests to switch service settings. This means they weren't protected by CSRF. On top of that as our number of service permissions increases over time a lot of buttons on the page made it hard to work with. To fix these issues we replace most of the buttons with rows in the platform admin settings table. Each setting has a 'Change' link that leads to a page with an On/Off switch form. This removes "research mode" switch completely since we're planning to deprecate it in the future and we don't expect to switch any new services into research mode at the moment. Most service permissions are now handled by a shared endpoint that is parameterized with the permission name. Some permissions that require some additional logic before they can be toggled (like document upload, which requires setting a contact address) have separate initial endpoints that redirect to `set_service_permission`. "Archive", "Suspend" and "Resume" actions are kept as buttons since they display a confirmation banner (which is a CSRF-protected form) and they're not easily represented as an On/Off switch.
2019-02-18 16:56:43 +00:00
'service_set_permission',
No emails, texts or letters for broadcast services To make the interface as simple as possible we don’t want to mix up sending other types of communication where services have the broadcast permission. This commit removes the other permissions once a service has been given the broadcast permission by a platform admin user.
2020-07-13 08:56:57 +01:00
'service_set_broadcast_permission',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'services_or_dashboard',
'show_accounts_or_dashboard',
'sign_in',
'sign_out',
'start_job',
'start_tour',
'styleguide',
'support',
Direct members of the public somewhere more useful We can’t give advice to members of the public, but increasingly we’re seeing them try to use our support form to ask. It would be better for them if we can direct them straight to somewhere more useful, before they have the chance to raise a support ticket. This commit replaces the report a problem/ask a question triaging for users who aren’t signed in. It’s not possible for non-signed-in users to raise an priority 1 ticket, so we never need to triage the tickets in this way. Instead we can triage people based on whether they work in the public sector or not. If they do then we send them on to the feedback form. If not then they go to a new page which contains some useful links. We’ve chosen these links based on some analysis of the support tickets we’ve received recently[1] 1. https://docs.google.com/spreadsheets/d/1uBQn-ZnCYfz6ltFaUKZpytgvBF0-MeshCLZ1cD74R0c/edit?usp=sharing
2020-03-24 15:01:42 +00:00
'support_public',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'suspend_service',
'template_history',
'terms',
'thanks',
'triage',
'trial_mode',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'trial_mode_new',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'trial_services',
'two_factor',
'two_factor_email',
'two_factor_email_sent',
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run
2020-05-04 12:27:51 +01:00
'two_factor_email_interstitial',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'update_email_branding',
Add update_letter_branding view function This works in a similar way to the create_letter_branding view function, but with a few minor differences: * Since we already have a file, uploading a file is no longer required (since we can just use the current file if a new one is not uploaded) * We save the changes in the database, then upload the new files to S3. If saving to S3 raises an error, we now rollback the database changes to prevent any errors when trying to view letters with the original logo.
2019-02-11 15:31:12 +00:00
'update_letter_branding',
New report on platform-admin/reports page to get the usage for all services.
2019-08-23 17:14:04 +01:00
'usage_for_all_services',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'user_information',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'user_profile',
'user_profile_email',
'user_profile_email_authenticate',
'user_profile_email_confirm',
'user_profile_mobile_number',
'user_profile_mobile_number_authenticate',
'user_profile_mobile_number_confirm',
'user_profile_name',
'user_profile_password',
make sure tests all populate the platform admin field it's always returned by the API
2019-06-14 15:14:00 +01:00
'user_profile_disable_platform_admin_view',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'using_notify',
'verify',
'verify_email',
'view_job_csv',
'view_job_updates',
'view_letter_notification_as_preview',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_letter_template_preview',
Show letter preview once file is uploaded This shows the sanitised letter preview if the file had no validation errors or the preview with the overlay if it failed validation.
2019-09-09 10:59:32 +01:00
'view_letter_upload_as_preview',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
'view_notification_updates',
'view_notifications_csv',
'view_provider',
'view_providers',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_template_version_preview',
Update who_its_for to who_can_use_notify
2020-05-20 15:54:15 +01:00
'who_can_use_notify',
Redirect old URL
2020-05-21 11:17:44 +01:00
'who_its_for',
Rewrite navigation as a class Because we have multiple navigations, which will share the same methods (by subclassing) but different mappings of navigation items to endpoints by overriding the `.mapping` and `.exclude` attributes.
2018-04-25 10:24:32 +01:00
}
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
class CaseworkNavigation(Navigation):
mapping = {
Add a dashboard for broadcast services This is just a placeholder for now
2020-07-08 11:34:16 +01:00
'dashboard': {
Add a tour for users new to broadcast services This is an initial, prototype-quality attempt at introducing some kind of tour for users new to broadcasting. A lot of the users we’re speaking to don’t have a good concept of what broadcasting means, which is causing usability problems down the line. We did a similar thing in the early days of Notify to explain the concept of message templates and personalisation.
2020-08-03 13:37:34 +01:00
'broadcast_tour',
Add a dashboard for broadcast services This is just a placeholder for now
2020-07-08 11:34:16 +01:00
'broadcast_dashboard',
Make the broadcast dashboard update via AJAX Same technique as we use for other pages that update via AJAX. I’ve split the page up into separate chunks because the DiffDOM library we use finds it easier to work out what’s changed when there are fewer elements/a shallower tree.
2020-07-14 13:39:29 +01:00
'broadcast_dashboard_updates',
Add a dashboard for broadcast services This is just a placeholder for now
2020-07-08 11:34:16 +01:00
},
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'send-one-off': {
Add a page to choose a contact list You’ll be able to use a contact list by first choosing a template, then choosing the list you want to use. At the moment this shows all lists, not just the ones that are compatible with your template.
2020-03-13 17:51:22 +00:00
'choose_from_contact_list',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'choose_template',
'send_one_off',
input letter address data in a single block rather than in multiple placeholders - this is the first step towards making postcodes non-required, which is the first step towards international letters. they still populate address_line_# and postcode fields under the hood - to keep validation working the same, the last line always goes into `postcode`. the form normalises whitespace, removes extra new lines, and enforces that you have between three and seven lines. if the letter repeats address placeholders further down (eg "Dear ((address_line_1))"), then it'll fill those in as well. It'll still prompt you to fill them in, but they'll be pre-filled.
2020-03-10 15:12:19 +00:00
'send_one_off_letter_address',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'send_one_off_step',
'send_test',
'send_test_step',
Add sent notifications page for caseworkers The other task that caseworkers have to do (much less often than sending messages) is look at the messages which they’ve sent. The reason for doing this is usually to find a specific message which someone has complained about. This commit adds: - a page where they can do that - a navigation item so they can get to that page We reckon that because this is about finding specific messages, not reporting that it’s fine to mush all the channels (email, text, letter) into one table.
2018-06-13 14:16:10 +01:00
},
'sent-messages': {
'view_notifications',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'view_notification',
},
Let caseworkers see uploads page At the moment they can only see it if there are existing jobs. This commit lets them also see it if their service can upload letters, because caseworkers might be the ones uploading some letters.
2019-10-09 10:58:15 +01:00
'uploads': {
Show jobs in basic view There are some teams who send jobs on a daily/weekly basis. They have team members who only use Notify for this purpose. So they would probably benefit from basic view, because they don’t need to see the dashboard. This commit: - adds a new item (uploaded files) to the basic view navigation for teams that have sent at least one job - makes the job pages visible to basic view users I think we should do this now, rather than as a later enhancement to basic view. We only have one chance to announce the feature, so teams who do send jobs may otherwise discount it as not useful for them and the opportunity to have them use it is lost.
2018-07-30 17:40:32 +01:00
'view_jobs',
'view_job',
Let users upload a contact list to use later We increasingly have teams wanting to do business-continuity type messaging. They might be without access to their normal systems, which is where they would otherwise go to get the list of email addresses or phone numbers. So we want to give them a place in Notify where they can store their spreadsheets and use them at a later date. For the initial pass we’re going to scope this to only allowing spreadsheets with one column, ie just phone numbers/email addresses. This is because: - it minimises the amount of personal info we’re storing - it reduces the chance of getting a placeholder error when you go to send the message, which is probably a high-stress situation where you might not be able to re-generate the file The code for this is mostly copied from the existing upload CSV journey. It’s quite duplicative, but that’s what I needed to do to get this out quickly. There are opportunities for refactoring later. Similarly, I would have liked to split this up into better commit messages, but it really was a case of just bashing code out until it worked 😳 This commit does not: - implement the ‘view a contact list page’ (it just has a placeholder because the API isn’t ready at the moment) - link to this page (because it’s not ready to use yet)
2020-03-12 16:13:18 +00:00
'upload_contact_list',
'check_contact_list',
'save_contact_list',
'contact_list',
Let users delete a contact list Follows our standard pattern of confirming with a red banner for actions that are destructive.
2020-03-18 13:37:39 +00:00
'delete_contact_list',
Let caseworkers see uploads page At the moment they can only see it if there are existing jobs. This commit lets them also see it if their service can upload letters, because caseworkers might be the ones uploading some letters.
2019-10-09 10:58:15 +01:00
'upload_letter',
'uploaded_letter_preview',
Add page to show all uploaded letters Because we won’t be showing uploaded letters individually on the uploads page any more we need a way of listing them. This should be by printing day, to match how we’re grouping them on the uploads page. This code reuses the notifications.html template, but flips the precedence of the filename and recipient because I reckon when you’re looking at uploads you’re thinking filename-first.
2020-05-11 10:52:43 +01:00
'uploaded_letters',
Let caseworkers see uploads page At the moment they can only see it if there are existing jobs. This commit lets them also see it if their service can upload letters, because caseworkers might be the ones uploading some letters.
2019-10-09 10:58:15 +01:00
'uploads',
Show jobs in basic view There are some teams who send jobs on a daily/weekly basis. They have team members who only use Notify for this purpose. So they would probably benefit from basic view, because they don’t need to see the dashboard. This commit: - adds a new item (uploaded files) to the basic view navigation for teams that have sent at least one job - makes the job pages visible to basic view users I think we should do this now, rather than as a later enhancement to basic view. We only have one chance to announce the feature, so teams who do send jobs may otherwise discount it as not useful for them and the opportunity to have them use it is lost.
2018-07-30 17:40:32 +01:00
},
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
}
exclude = {
'accept_invite',
'accept_org_invite',
'action_blocked',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'add_data_retention',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'add_organisation',
Let GP surgeries create their own organisations We have a bunch of GP surgeries who want to go live. They don’t automatically assigned to organisations. So this means a lot of back and forth to get these organisations set up, and then the service has to re-request to go live, and… it’s painful. Instead, let’s let GPs create their own organisations, by confirming the name of their organisation before going on to letting them accept the agreement.
2019-09-04 16:27:25 +01:00
'add_organisation_from_gp_service',
Let NHS Trusts and CCGs choose own organisation All we do via support is ask which organisation they work for and manually assign their service to it. This commit makes that process self service. We think we have all the trusts and clinical commissioning groups loaded into the database now. This will make the go live process smoother for these teams.
2019-09-05 16:18:02 +01:00
'add_organisation_from_nhs_local_service',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'add_service',
'add_service_template',
'api_callbacks',
'api_documentation',
'api_integration',
'api_keys',
'archive_service',
Add page to archive user Users can only be archived by Platform Admin from the user page (/users/<user_id>). This removes them from all services and orgs and updates their details.
2019-05-22 11:38:47 +01:00
'archive_user',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'bat_phone',
'branding_request',
'callbacks',
'cancel_invited_org_user',
'cancel_invited_user',
'cancel_job',
Add link to cancel letters Added a link to cancel letters from the letter notification pages if the letter is still able to be cancelled. Clicking on this link will show a confirmation box, and will then cancel the letter if the user confirms.
2018-12-05 10:58:27 +00:00
'cancel_letter',
Letter job can't be cancelled if already printed Non-cancellable letter statuses mean that it's too late to cancel a job
2019-06-18 18:00:36 +01:00
'cancel_letter_job',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'check_and_resend_text_code',
'check_and_resend_verification_code',
'check_messages',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_messages_preview',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'check_notification',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_notification_preview',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'choose_account',
'choose_service',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'choose_template_to_copy',
add clear cache platform admin page a form that allows you to clear entries from the cache for all of either users, services or templates. It'll tell you the largest amount of keys deleted, since there are multiple keys associated with each model.
2019-02-15 10:27:38 +00:00
'clear_cache',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_agreement',
'edit_organisation_crown_status',
'edit_organisation_domains',
'edit_organisation_email_branding',
Allow custom notes when service goes live This adds an option on the organisation settings page to add 'request_to_go_live_notes'. When a service belonging to this organisation requests to go live, any go live notes for the organisation will be added to the Zendesk ticket in the 'Agreement signed' section.
2019-05-13 14:50:40 +01:00
'edit_organisation_go_live_notes',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_letter_branding',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'confirm_edit_organisation_name',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'confirm_edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'confirm_edit_user_mobile_number',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'confirm_redact_template',
'conversation',
'conversation_reply',
'conversation_reply_with_template',
'conversation_updates',
'cookies',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'copy_template',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'create_api_key',
'create_email_branding',
Add page to create new letter branding This has a form with 3 fields - the file upload field, logo name, and an optional logo domain. Logos need to be uploaded in `.svg` format and we then convert this to `.png` format and upload both file types to S3 as well as saving the letter branding details in the database.
2019-01-31 16:56:35 +00:00
'create_letter_branding',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'data_retention',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'delete_service_template',
Build delete folder endpoint that calls template_folders_api_client
2018-11-13 17:56:47 +00:00
'delete_template_folder',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'delivery_and_failure',
'delivery_status_callback',
'design_content',
'documentation',
Add an endpoint to download a contact list In case you need to download it, modify it, and re-upload it when you don’t have access to the existing list.
2020-03-15 19:13:07 +00:00
'download_contact_list',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'download_notifications_csv',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'edit_data_retention',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_agreement',
'edit_organisation_crown_status',
'edit_organisation_domains',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'edit_organisation_name',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_type',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'edit_provider',
Add page showing priority of two SMS providers It’s not very useful to know the priority of one provider without knowing the other. And these pages were never really designed, so they weren’t super easy to understand anyway. This commit adds a page that takes the first two text message providers and shows their relative priority against each other. It follows the design of the events page, as a pattern for showing a log of historical events.
2019-12-02 14:29:34 +00:00
'edit_sms_provider_ratio',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'edit_service_template',
Edit template postage from a separate view
2019-01-29 15:43:59 +00:00
'edit_template_postage',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'edit_user_mobile_number',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'edit_user_org_permissions',
'edit_user_permissions',
'email_branding',
'email_not_received',
'email_template',
'error',
Move the ‘estimated usage’ questions We get a bunch of requests to go live where people have told us they're going to send email but there is no email reply-to address present. These come from 2 scenarios: 1. when there are email templates, and no reply to address – but they ignore the checklist 2. when there are no email templates (yet) but they provide anticipated volumes for email At the moment we only auto-check for a reply to address when they have email templates. And because the question about anticipated volumes follows the checklist, you'll get a checklist that passes (reply addresses not required as no templates present) - but your future intent that differs (reply address IS required because you have anticipated volumes). So let’s bring the request for anticipated volumes into the checklist, that way we can dynamically add the requirement for a reply to address if they say they will send email but don't have templates yet. We should begin storing it in the database against the service to stop people having to re-enter it each time they try to complete the go live screens. This also means moving the ‘consent to research question’ along with the questions about volume, because - we want people to answer both before going live - we don’t want to clutter up the summary page by asking questions there too
2019-02-15 11:03:19 +00:00
'estimate_usage',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'features',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'features_email',
'features_letters',
'features_sms',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'feedback',
Find services by name or partial name
2019-08-13 16:25:26 +01:00
'find_services_by_name',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'find_users_by_email',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'forgot_password',
'get_example_csv',
'get_notifications_as_json',
Add endpoint for new page
2019-10-17 16:15:28 +01:00
'get_started',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'get_started_old',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'go_to_dashboard_after_tour',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'guidance_index',
'branding_and_customisation',
'create_and_send_messages',
'edit_and_format_messages',
'send_files_by_email',
'upload_a_letter',
Move service history into it own file We’re going to do some work on this page, let’s put it in a sensible place first before we add a bunch more code to the wrong place.
2019-10-18 09:18:51 +01:00
'history',
Add ‘How to pay’ page Content from https://docs.google.com/document/d/1uIFW8c7Vk0-FQ-d8H1FmNZLHKn_tOXWg5oUL8bbcZzw/edit?ts=5ced1ae4#
2019-06-04 10:43:15 +01:00
'how_to_pay',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'inbound_sms_admin',
'inbox_download',
'inbox_updates',
fix user permissions save button sometimes deleting when you hit the delete button, it flashes the delete button and takes you to the `/service/../user/../delete` url. If you then click the save button, it would make a POST to the delete URL... and delete the user. now the page stays on the edit url, but adds a `?delete=yes` query string. The dangerous flash banner now has an action field which defines where the browser will make the POST to (which remains at /delete).
2019-03-14 17:31:51 +00:00
'inbox',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'index',
'information_risk_management',
'information_security',
'integration_testing',
'invite_org_user',
'invite_user',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.letter_branding_preview_image',
fix user permissions save button sometimes deleting when you hit the delete button, it flashes the delete button and takes you to the `/service/../user/../delete` url. If you then click the save button, it would make a POST to the delete URL... and delete the user. now the page stays on the edit url, but adds a `?delete=yes` query string. The dangerous flash banner now has an action field which defines where the browser will make the POST to (which remains at /delete).
2019-03-14 17:31:51 +00:00
'letter_branding',
Add a redirect for the letter specification This way we have a URL we can give people that always points to the latest version of the spec. And it makes our code more Flask-idiomatic to be using `url_for` to be generating a URL, rather than passing around a constant.
2020-01-15 10:56:14 +00:00
'letter_spec',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'letter_template',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'link_service_to_organisation',
'live_services',
Get live services csv report
2019-04-24 16:23:12 +01:00
'live_services_csv',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'manage_org_users',
Add a new endpoint for managing a folder, use it to rename folder - Add a GET / POST view: manage template folder - Add a template for that view, where a user can rename their folder - Add an API client method for updating a folder - Test the new feature, including the test that service without permissions cannot manage a folder
2018-11-12 16:37:37 +00:00
'manage_template_folder',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'manage_users',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'message_status',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'monthly',
'new_password',
Add new report to show monthly notification stats for each service This report will be used by the engagement team. There is a form to give a start and end date for the report, and the form is then downloaded as a CSV file when the form is submitted.
2019-07-22 13:09:03 +01:00
'notifications_sent_by_service',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'old_integration_testing',
'old_roadmap',
'old_service_dashboard',
'old_terms',
'old_using_notify',
'organisation_dashboard',
move trial mode services from org dashboard to separate page the new page is platform admin only, and also has search built in also, split test_organisation_invites into two files
2019-05-21 14:56:15 +01:00
'organisation_trial_mode_services',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'organisation_preview_email_branding',
'organisation_preview_letter_branding',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'organisation_settings',
'organisations',
Provide Performance Platform report as Excel file This is the format we need to upload it in, so this means not having to manually re-save it as Excel.
2019-05-03 14:32:02 +01:00
'performance_platform_xlsx',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'platform_admin_list_complaints',
Basic reports page, returns 200 and is visible in PA sidebar
2019-04-24 10:27:57 +01:00
'platform_admin_reports',
Add a platform admin page to submit returned letter references A platform admin form accepts a list of references (one per line) received from DVLA and sends them to the API to update notification statuses. References we get from DVLA start with `NOTIFY00\d`, which isn't part of the reference we store in the database, so we remove them before sending the data to the API. The new `returned-letter` status should be treated as `delivered` for now until we decide a way to display returned letters to users.
2018-09-06 16:34:23 +01:00
'platform_admin_returned_letters',
fix user permissions save button sometimes deleting when you hit the delete button, it flashes the delete button and takes you to the `/service/../user/../delete` url. If you then click the save button, it would make a POST to the delete URL... and delete the user. now the page stays on the edit url, but adds a `?delete=yes` query string. The dangerous flash banner now has an action field which defines where the browser will make the POST to (which remains at /delete).
2019-03-14 17:31:51 +00:00
'platform_admin',
Reduce usage of the platform admin index page This page is slow to load which means: - it’s annoying for us - it’s potentially causing load on the database This commit does two things to reduce the amount we’re unnecessarily looking at this page: 1. Avoid redirecting to it when signing in as a platform admin user 2. Don’t go directly to it when clicking ‘platform admin’ at the top, but instead show a holding page (there’s a fair chance you’ve clicked that link in order to go and manage some email branding or find a user, not wait for stats to load)
2020-03-19 10:49:40 +00:00
'platform_admin_splash_page',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'pricing',
'privacy',
'public_agreement',
'public_download_agreement',
'received_text_messages_callback',
'redact_template',
'register_from_invite',
'register_from_org_invite',
fix user permissions save button sometimes deleting when you hit the delete button, it flashes the delete button and takes you to the `/service/../user/../delete` url. If you then click the save button, it would make a POST to the delete URL... and delete the user. now the page stays on the edit url, but adds a `?delete=yes` query string. The dangerous flash banner now has an action field which defines where the browser will make the POST to (which remains at /delete).
2019-03-14 17:31:51 +00:00
'register',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'registration_continue',
'remove_user_from_organisation',
'remove_user_from_service',
'request_to_go_live',
'resend_email_link',
'resend_email_verification',
'resume_service',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letter_summary',
Add a page for each report It’s useful to get some kind of preview of the report before you download it. And if there’s only a few letters in there then you might not even need to download it at all. For teams with lots of letters we don’t want the page to load too slowly so let’s cap the number of displayed items to 50, same as previewing a spreadsheet.
2019-12-31 13:27:27 +00:00
'returned_letters',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letters_report',
Send 2fa email and move user to waiting page when they need to re-validate email access
2020-01-27 18:10:45 +00:00
'revalidate_email_sent',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'revoke_api_key',
'roadmap',
'security',
'send_messages',
'send_notification',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.send_test_preview',
Add endpoint to redirect from contact list to send In order to use a contact list we’re going to put you in the normal upload a spreadsheet journey. Except without having to upload again. So this commit adds an endpoint that takes the file from the contact list bucket, puts it in the same place it would have gone if you’d uploaded it, then sends you on your way.
2020-03-13 14:38:43 +00:00
'send_from_contact_list',
Allow uploaded letters to be sent if valid Added a send button which only appears on the page if the query string indicates that the PDF is valid. Before actually sending, we check that the service has the right permissions and that the metadata for the letter confirms the letter is valid (because the query string can be changed).
2019-09-09 12:22:52 +01:00
'send_uploaded_letter',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_add_email_reply_to',
'service_add_letter_contact',
'service_add_sms_sender',
Add service-specific versions of agreement page Our usability testing found that jumping out of the service when going to download the agreement made it difficult for people to find their way back to the ‘Request to go live’ page. This commit adds a duplicate, service-specific versions of these pages which have the same content but: - keep the service navigation - have a link back to the ‘Request to go live’ page
2019-05-01 08:29:32 +01:00
'service_agreement',
Add pages to let users accept the agreement online At the moment, the process for accepting the data sharing and financial agreement is: 1. download a pdf * print it out * get someone to sign it * scan it * email it back to us * we rename the file and save it in Google Drive * we then update the organisation to say the MOU is signed * sometimes we also: * print it out and get it counter-signed * scan it again * email it back to the service Let's not do that any more. When the first service for an organisation that doesn't have the agreement in place is in the process of going live, then they should be able to accept the agreement online as part of the go live flow. This commit adds the pages that let someone do that. Where the checklist shows the agreement as **[not completed]** then they can follow a link where they can download it (as happens now). From here, they should then also be able to provide some info to accept it. The info that we need is: **Version** – because we version the agreements occasionally, we need to know which version they are accepting. It may not be the latest one if they downloaded it a while ago and it took time to be signed off **Who is accepting the agreement** – this will often be someone in the finance team, and not necessarily a team member, so we should let the person either accept as themselves, or on behalf of someone else. If it's on behalf of someone else we need to the name and email address of that person so we have that on record. Obvs if it's them accepting it themselves, we have that already (so we just store their user ID and not their name or email address). We then replay the collected info back in a sort of legally binding kind of way pulling in the organisation name too. The wording we’re using is inspired by what GOV.UK Pay have. Then there’s a big green button they can click to accept the agreement, which stores their user ID and and timestamp.
2019-06-18 14:24:29 +01:00
'service_accept_agreement',
'service_confirm_agreement',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_confirm_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_confirm_delete_letter_contact',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_confirm_delete_sms_sender',
'service_dashboard',
'service_dashboard_updates',
'service_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_delete_letter_contact',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_delete_sms_sender',
Determine agreement by service not user’s org A user might not have a guessable organisation type, even if the service they’re working on does have an organisation set. This can happen for users with @nhs.net email addresses, for example.
2019-07-02 17:04:26 +01:00
'service_download_agreement',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_edit_email_reply_to',
'service_edit_letter_contact',
'service_edit_sms_sender',
'service_email_reply_to',
'service_letter_contact_details',
Allow deleting default letter contact blocks It’s possible to delete default letter contact blocks because there is a fallback – having a blank letter contact block. This is different to SMS senders and reply to addresses. For this to make sense it also means: - adding the ‘blank’ letter contact block to the list of letter contact blocks - having a way of setting the default back to being blank
2019-07-05 13:17:48 +01:00
'service_make_blank_default_letter_contact',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_name_change',
'service_name_change_confirm',
Fixes for tests broken by changes - corrects target page for set_email_branding to new preview step instead of itself - removed check for helper method being called in email page test - updates expected result for test of global headers to include changes to `frame-src` - updates navigation config with brand preview page
2018-08-03 17:39:58 +01:00
'service_preview_email_branding',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'service_preview_letter_branding',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_set_auth_type',
Let users switch channels on and off by themselves We let people do this for letters already. We should let them do it for emails and texts too, rather than have to email us.
2019-01-29 14:51:31 +00:00
'service_set_channel',
Send files by email on for everyone and only depending on service having contact details set up. Display not set up yet for send files by email row when contact_link not set up
2020-02-25 11:27:43 +00:00
'send_files_by_email_contact_details',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_set_email_branding',
'service_set_inbound_number',
'service_set_inbound_sms',
'service_set_international_sms',
'service_set_letters',
'service_set_reply_to_email',
'service_set_sms_prefix',
'service_settings',
'service_sms_senders',
Allow excluding services from live services count Adds a front end for: https://github.com/alphagov/notifications-api/pull/2417 > Sometimes we have to make a few services for what really is one > service, for example GOV.UK Pay and GOV.UK Pay Direct Debit. We also > have our own test services which aren’t included in the count of live > services. We currently count these as one service by not including > them in the beta partners spreadsheet.
2019-03-25 14:46:42 +00:00
'service_switch_count_as_live',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'service_switch_live',
Replace platform admin service setting buttons with forms Most of the existing platform admin buttons on the service settings page used to issue GET requests to switch service settings. This means they weren't protected by CSRF. On top of that as our number of service permissions increases over time a lot of buttons on the page made it hard to work with. To fix these issues we replace most of the buttons with rows in the platform admin settings table. Each setting has a 'Change' link that leads to a page with an On/Off switch form. This removes "research mode" switch completely since we're planning to deprecate it in the future and we don't expect to switch any new services into research mode at the moment. Most service permissions are now handled by a shared endpoint that is parameterized with the permission name. Some permissions that require some additional logic before they can be toggled (like document upload, which requires setting a contact address) have separate initial endpoints that redirect to `set_service_permission`. "Archive", "Suspend" and "Resume" actions are kept as buttons since they display a confirmation banner (which is a CSRF-protected form) and they're not easily represented as an On/Off switch.
2019-02-18 16:56:43 +00:00
'service_set_permission',
No emails, texts or letters for broadcast services To make the interface as simple as possible we don’t want to mix up sending other types of communication where services have the broadcast permission. This commit removes the other permissions once a service has been given the broadcast permission by a platform admin user.
2020-07-13 08:56:57 +01:00
'service_set_broadcast_permission',
Verify email address when editing reply-to address Also fix the tests
2019-05-16 17:05:55 +01:00
'service_verify_reply_to_address',
'service_verify_reply_to_address_updates',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'services_or_dashboard',
'set_free_sms_allowance',
fix request letter branding page (it can now have a null type). also fix nav.py
2019-02-05 16:33:36 +00:00
'service_set_letter_branding',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'set_sender',
'set_template_sender',
'show_accounts_or_dashboard',
'sign_in',
'sign_out',
'start_job',
'start_tour',
'styleguide',
'submit_request_to_go_live',
'support',
Direct members of the public somewhere more useful We can’t give advice to members of the public, but increasingly we’re seeing them try to use our support form to ask. It would be better for them if we can direct them straight to somewhere more useful, before they have the chance to raise a support ticket. This commit replaces the report a problem/ask a question triaging for users who aren’t signed in. It’s not possible for non-signed-in users to raise an priority 1 ticket, so we never need to triage the tickets in this way. Instead we can triage people based on whether they work in the public sector or not. If they do then we send them on to the feedback form. If not then they go to a new page which contains some useful links. We’ve chosen these links based on some analysis of the support tickets we’ve received recently[1] 1. https://docs.google.com/spreadsheets/d/1uBQn-ZnCYfz6ltFaUKZpytgvBF0-MeshCLZ1cD74R0c/edit?usp=sharing
2020-03-24 15:01:42 +00:00
'support_public',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'suspend_service',
'template_history',
'template_usage',
'terms',
'thanks',
'triage',
'trial_mode',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'trial_mode_new',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'trial_services',
'two_factor',
'two_factor_email',
'two_factor_email_sent',
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run
2020-05-04 12:27:51 +01:00
'two_factor_email_interstitial',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'update_email_branding',
Add update_letter_branding view function This works in a similar way to the create_letter_branding view function, but with a few minor differences: * Since we already have a file, uploading a file is no longer required (since we can just use the current file if a new one is not uploaded) * We save the changes in the database, then upload the new files to S3. If saving to S3 raises an error, we now rollback the database changes to prevent any errors when trying to view letters with the original logo.
2019-02-11 15:31:12 +00:00
'update_letter_branding',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'usage',
New report on platform-admin/reports page to get the usage for all services.
2019-08-23 17:14:04 +01:00
'usage_for_all_services',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'user_information',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'user_profile',
'user_profile_email',
'user_profile_email_authenticate',
'user_profile_email_confirm',
'user_profile_mobile_number',
'user_profile_mobile_number_authenticate',
'user_profile_mobile_number_confirm',
'user_profile_name',
'user_profile_password',
make sure tests all populate the platform admin field it's always returned by the API
2019-06-14 15:14:00 +01:00
'user_profile_disable_platform_admin_view',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'using_notify',
'verify',
'verify_email',
'view_job_csv',
'view_job_updates',
'view_letter_notification_as_preview',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_letter_template_preview',
Show letter preview once file is uploaded This shows the sanitised letter preview if the file had no validation errors or the preview with the overlay if it failed validation.
2019-09-09 10:59:32 +01:00
'view_letter_upload_as_preview',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'view_notification_updates',
'view_notifications_csv',
'view_provider',
'view_providers',
'view_template',
'view_template_version',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_template_version_preview',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
'view_template_versions',
Rename endpoint to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:03:40 +01:00
'guest_list',
Rename URL to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:07:29 +01:00
'old_guest_list',
Update who_its_for to who_can_use_notify
2020-05-20 15:54:15 +01:00
'who_can_use_notify',
Redirect old URL
2020-05-21 11:17:44 +01:00
'who_its_for',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'broadcast',
'preview_broadcast_areas',
'choose_broadcast_library',
'choose_broadcast_area',
Let users select electoral wards of local authorities If a library has groups, we should show a link instead of selecting the group directly. Then we can give the user the choice of selecting the whole of that group, or specific areas within the group. For now the only libraries we have with groups are local authorities, which group electoral wards.
2020-07-31 16:20:37 +01:00
'choose_broadcast_sub_area',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'remove_broadcast_area',
'preview_broadcast_message',
Add a page to view a single broadcast This commit adds a page to view a single broadcast. This is important for two reasons: - users need an audit of what happened when, and who else was involved in approving or cancelling a broadcast - we need a place to put actions (approving, cancelling) on a broadcast so that you can confirm details of the message and the areas before performing the action
2020-07-10 14:06:00 +01:00
'view_broadcast_message',
Add button to approve broadcast Since new broadcasts will go into `pending-approval`, we now need a way of approving them. This commit adds a button to this page to start (or approve) the broadcast. This button is wrapped in a bordered box, to emphasise that it’s something consequential.
2020-07-17 08:07:44 +01:00
'approve_broadcast_message',
Add a link to reject a broadcast If a broadcast definitely shouldn’t go out (for example because it has a spelling mistake or is going to the wrong areas) then we should have a way of removing it. Once it’s removed no-one else can approve it, and it isn’t cluttering up the dashboard. This is a link (because it’s a secondary action) and red (because it’s destructive, in that it’s throwing away someone’s work).
2020-07-17 08:07:44 +01:00
'reject_broadcast_message',
Allow broadcasts to be cancelled Currently this is a `get` request from the dashboard. Once we have a page for viewing an individual broadcast it should probably show there instead and be a `get`/confirm/`post` loop like for deleting a template.
2020-07-10 09:16:36 +01:00
'cancel_broadcast_message',
Let caseworkers send one off messages The main task that we think ‘caseworker’ users do is send one off messages. So this commit: - makes sure users who don’t have the `view_activity` permission (ie not ‘admin’ users) can still send messages - adds navigation so that these users have a place to go from which to start the process of sending a one off message
2018-06-12 16:17:20 +01:00
}
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
class OrgNavigation(Navigation):
mapping = {
'dashboard': {
'organisation_dashboard',
},
'settings': {
'confirm_edit_organisation_name',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_agreement',
'edit_organisation_crown_status',
'edit_organisation_domains',
'edit_organisation_email_branding',
'edit_organisation_letter_branding',
'edit_organisation_domains',
Allow custom notes when service goes live This adds an option on the organisation settings page to add 'request_to_go_live_notes'. When a service belonging to this organisation requests to go live, any go live notes for the organisation will be added to the Zendesk ticket in the 'Agreement signed' section.
2019-05-13 14:50:40 +01:00
'edit_organisation_go_live_notes',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'edit_organisation_name',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
'edit_organisation_type',
'organisation_preview_email_branding',
'organisation_preview_letter_branding',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'organisation_settings',
Allow editing of an organisation’s details Adds a user interface for updating all the columns added in https://github.com/alphagov/notifications-api/pull/2368 Sorry for the mega commit 😓
2019-02-19 17:26:16 +00:00
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
},
'team-members': {
'edit_user_org_permissions',
'invite_org_user',
'manage_org_users',
'remove_user_from_organisation',
move trial mode services from org dashboard to separate page the new page is platform admin only, and also has search built in also, split test_organisation_invites into two files
2019-05-21 14:56:15 +01:00
},
'trial-services': {
'organisation_trial_mode_services',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
}
}
exclude = {
'accept_invite',
'accept_org_invite',
'action_blocked',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'add_data_retention',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'add_organisation',
Let GP surgeries create their own organisations We have a bunch of GP surgeries who want to go live. They don’t automatically assigned to organisations. So this means a lot of back and forth to get these organisations set up, and then the service has to re-request to go live, and… it’s painful. Instead, let’s let GPs create their own organisations, by confirming the name of their organisation before going on to letting them accept the agreement.
2019-09-04 16:27:25 +01:00
'add_organisation_from_gp_service',
Let NHS Trusts and CCGs choose own organisation All we do via support is ask which organisation they work for and manually assign their service to it. This commit makes that process self service. We think we have all the trusts and clinical commissioning groups loaded into the database now. This will make the go live process smoother for these teams.
2019-09-05 16:18:02 +01:00
'add_organisation_from_nhs_local_service',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'add_service',
'add_service_template',
'api_callbacks',
'api_documentation',
'api_integration',
'api_keys',
'archive_service',
Add page to archive user Users can only be archived by Platform Admin from the user page (/users/<user_id>). This removes them from all services and orgs and updates their details.
2019-05-22 11:38:47 +01:00
'archive_user',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'bat_phone',
Add page where users can say they want branding At the moment branding is an undocumented feature. We get a bunch of support tickets from teams asking its possible. This commit: - lets people know it’s possible, and what the options are - is the first step towards making this process as self-service as possible In some cases we will be able to infer a user’s organisation from there email address, and Google image search their logo. So the experience for them is that they press a button and government just sorts it out for you (also known as "the dream"). In other cases we will have to get back to people asking for a copy of their logo, or to find out about their service, but this is what we have to do at the moment anyway.
2018-05-18 14:05:48 +01:00
'branding_request',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'callbacks',
'cancel_invited_org_user',
'cancel_invited_user',
'cancel_job',
Add link to cancel letters Added a link to cancel letters from the letter notification pages if the letter is still able to be cancelled. Clicking on this link will show a confirmation box, and will then cancel the letter if the user confirms.
2018-12-05 10:58:27 +00:00
'cancel_letter',
Letter job can't be cancelled if already printed Non-cancellable letter statuses mean that it's too late to cancel a job
2019-06-18 18:00:36 +01:00
'cancel_letter_job',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'check_and_resend_text_code',
'check_and_resend_verification_code',
'check_messages',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_messages_preview',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'check_notification',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.check_notification_preview',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'choose_account',
Add a page to choose a contact list You’ll be able to use a contact list by first choosing a template, then choosing the list you want to use. At the moment this shows all lists, not just the ones that are compatible with your template.
2020-03-13 17:51:22 +00:00
'choose_from_contact_list',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'choose_service',
'choose_template',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'choose_template_to_copy',
add clear cache platform admin page a form that allows you to clear entries from the cache for all of either users, services or templates. It'll tell you the largest amount of keys deleted, since there are multiple keys associated with each model.
2019-02-15 10:27:38 +00:00
'clear_cache',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'confirm_edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'confirm_edit_user_mobile_number',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'confirm_redact_template',
'conversation',
'conversation_reply',
'conversation_reply_with_template',
'conversation_updates',
'cookies',
Add option to copy existing template when adding Sometimes when setting up a service you might have a few very similar templates, in which only a small amount of content. Or you might even have a few of services, which are used by different teams but have similar templates. Copy and pasting, especially from one service to another, is a pain. This commit makes it easier by allowing users to copy an existing template when choosing to add a new one, instead of starting from scratch.
2018-07-19 12:30:04 +01:00
'copy_template',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'create_api_key',
'create_email_branding',
Add page to create new letter branding This has a form with 3 fields - the file upload field, logo name, and an optional logo domain. Logos need to be uploaded in `.svg` format and we then convert this to `.png` format and upload both file types to S3 as well as saving the letter branding details in the database.
2019-01-31 16:56:35 +00:00
'create_letter_branding',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'data_retention',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'delete_service_template',
Build delete folder endpoint that calls template_folders_api_client
2018-11-13 17:56:47 +00:00
'delete_template_folder',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'delivery_and_failure',
'delivery_status_callback',
'design_content',
'documentation',
Add an endpoint to download a contact list In case you need to download it, modify it, and re-upload it when you don’t have access to the existing list.
2020-03-15 19:13:07 +00:00
'download_contact_list',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'download_notifications_csv',
Adding views to view, add and edit service data retention policies. Only visible to a platform admin. A service can have a custom number of days to retain the notification data for each notification type.
2018-07-17 14:39:04 +01:00
'edit_data_retention',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'edit_provider',
'edit_service_template',
Add page showing priority of two SMS providers It’s not very useful to know the priority of one provider without knowing the other. And these pages were never really designed, so they weren’t super easy to understand anyway. This commit adds a page that takes the first two text message providers and shows their relative priority against each other. It follows the design of the events page, as a pattern for showing a log of historical events.
2019-12-02 14:29:34 +00:00
'edit_sms_provider_ratio',
Edit template postage from a separate view
2019-01-29 15:43:59 +00:00
'edit_template_postage',
Confirm edit user email changes user email
2019-02-20 11:50:34 +00:00
'edit_user_email',
Change team member's mobile number upon confirmation Also add edit user mobile number urls to navigation exceptions
2019-02-22 16:01:04 +00:00
'edit_user_mobile_number',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'edit_user_permissions',
'email_branding',
'email_not_received',
'email_template',
'error',
Move the ‘estimated usage’ questions We get a bunch of requests to go live where people have told us they're going to send email but there is no email reply-to address present. These come from 2 scenarios: 1. when there are email templates, and no reply to address – but they ignore the checklist 2. when there are no email templates (yet) but they provide anticipated volumes for email At the moment we only auto-check for a reply to address when they have email templates. And because the question about anticipated volumes follows the checklist, you'll get a checklist that passes (reply addresses not required as no templates present) - but your future intent that differs (reply address IS required because you have anticipated volumes). So let’s bring the request for anticipated volumes into the checklist, that way we can dynamically add the requirement for a reply to address if they say they will send email but don't have templates yet. We should begin storing it in the database against the service to stop people having to re-enter it each time they try to complete the go live screens. This also means moving the ‘consent to research question’ along with the questions about volume, because - we want people to answer both before going live - we don’t want to clutter up the summary page by asking questions there too
2019-02-15 11:03:19 +00:00
'estimate_usage',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'features',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'features_email',
'features_letters',
'features_sms',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'feedback',
Find services by name or partial name
2019-08-13 16:25:26 +01:00
'find_services_by_name',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'find_users_by_email',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'forgot_password',
'get_example_csv',
'get_notifications_as_json',
Add endpoint for new page
2019-10-17 16:15:28 +01:00
'get_started',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'get_started_old',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'go_to_dashboard_after_tour',
Add left hand navigation Due to the way the navigation dictionaries are built this mean being less smart about the view method for the guidance pages.
2020-01-24 15:57:29 +00:00
'guidance_index',
'branding_and_customisation',
'create_and_send_messages',
'edit_and_format_messages',
'send_files_by_email',
'upload_a_letter',
Move service history into it own file We’re going to do some work on this page, let’s put it in a sensible place first before we add a bunch more code to the wrong place.
2019-10-18 09:18:51 +01:00
'history',
Add ‘How to pay’ page Content from https://docs.google.com/document/d/1uIFW8c7Vk0-FQ-d8H1FmNZLHKn_tOXWg5oUL8bbcZzw/edit?ts=5ced1ae4#
2019-06-04 10:43:15 +01:00
'how_to_pay',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'inbound_sms_admin',
'inbox',
'inbox_download',
'inbox_updates',
'index',
'information_risk_management',
'information_security',
'integration_testing',
'invite_user',
Add '/letter-branding' page to show all letter brands This is a platform admin page which lists all letter brands and their domain. Once the page to edit a letter brand has been created, each brand will link to its edit page, but for now this is just a list of brand names and domains.
2019-02-07 16:16:22 +00:00
'letter_branding',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.letter_branding_preview_image',
Add a redirect for the letter specification This way we have a URL we can give people that always points to the latest version of the spec. And it makes our code more Flask-idiomatic to be using `url_for` to be generating a URL, rather than passing around a constant.
2020-01-15 10:56:14 +00:00
'letter_spec',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'letter_template',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'link_service_to_organisation',
'live_services',
Get live services csv report
2019-04-24 16:23:12 +01:00
'live_services_csv',
Add a new endpoint for managing a folder, use it to rename folder - Add a GET / POST view: manage template folder - Add a template for that view, where a user can rename their folder - Add an API client method for updating a folder - Test the new feature, including the test that service without permissions cannot manage a folder
2018-11-12 16:37:37 +00:00
'manage_template_folder',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'manage_users',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'message_status',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'monthly',
'new_password',
Add new report to show monthly notification stats for each service This report will be used by the engagement team. There is a form to give a start and end date for the report, and the form is then downloaded as a CSV file when the form is submitted.
2019-07-22 13:09:03 +01:00
'notifications_sent_by_service',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'old_integration_testing',
'old_roadmap',
'old_service_dashboard',
'old_terms',
'old_using_notify',
'organisations',
Provide Performance Platform report as Excel file This is the format we need to upload it in, so this means not having to manually re-save it as Excel.
2019-05-03 14:32:02 +01:00
'performance_platform_xlsx',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'platform_admin',
When someone complains about an email from the platform we get a callback from SES. A new platform admin page Email complaints has been added to surface those complaints. Eventually the complaints will be visible to the services so they can remove the email address from their mailing list. Next thing to implement is "x email complaints" warning on the platform admin summary page.
2018-06-06 15:22:48 +01:00
'platform_admin_list_complaints',
Basic reports page, returns 200 and is visible in PA sidebar
2019-04-24 10:27:57 +01:00
'platform_admin_reports',
Add a platform admin page to submit returned letter references A platform admin form accepts a list of references (one per line) received from DVLA and sends them to the API to update notification statuses. References we get from DVLA start with `NOTIFY00\d`, which isn't part of the reference we store in the database, so we remove them before sending the data to the API. The new `returned-letter` status should be treated as `delivered` for now until we decide a way to display returned letters to users.
2018-09-06 16:34:23 +01:00
'platform_admin_returned_letters',
Reduce usage of the platform admin index page This page is slow to load which means: - it’s annoying for us - it’s potentially causing load on the database This commit does two things to reduce the amount we’re unnecessarily looking at this page: 1. Avoid redirecting to it when signing in as a platform admin user 2. Don’t go directly to it when clicking ‘platform admin’ at the top, but instead show a holding page (there’s a fair chance you’ve clicked that link in order to go and manage some email branding or find a user, not wait for stats to load)
2020-03-19 10:49:40 +00:00
'platform_admin_splash_page',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'pricing',
Excluding the privacy page from the navigation stuff
2018-05-23 14:33:29 +01:00
'privacy',
Add URLs to download the agreement without login So that we can share these URLs in an email we’re sending out.
2018-05-08 14:06:26 +01:00
'public_agreement',
'public_download_agreement',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'received_text_messages_callback',
'redact_template',
'register',
'register_from_invite',
'register_from_org_invite',
'registration_continue',
'remove_user_from_service',
'request_to_go_live',
'resend_email_link',
'resend_email_verification',
'resume_service',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letter_summary',
Add a page for each report It’s useful to get some kind of preview of the report before you download it. And if there’s only a few letters in there then you might not even need to download it at all. For teams with lots of letters we don’t want the page to load too slowly so let’s cap the number of displayed items to 50, same as previewing a spreadsheet.
2019-12-31 13:27:27 +00:00
'returned_letters',
Added returned-letter-summary page. This page displays a list of available reports, a report is a set of returned lettters that have been reported on the same day. Each line of the page is a link that can download the report. I'm not sure the format of the csv is right. The data might be confusing especially if the service has a mix of precompiled templates and jobs. Units tests are still to come.
2019-12-18 11:53:46 +00:00
'returned_letters_report',
Send 2fa email and move user to waiting page when they need to re-validate email access
2020-01-27 18:10:45 +00:00
'revalidate_email_sent',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'revoke_api_key',
'roadmap',
'security',
'send_messages',
'send_notification',
'send_one_off',
input letter address data in a single block rather than in multiple placeholders - this is the first step towards making postcodes non-required, which is the first step towards international letters. they still populate address_line_# and postcode fields under the hood - to keep validation working the same, the last line always goes into `postcode`. the form normalises whitespace, removes extra new lines, and enforces that you have between three and seven lines. if the letter repeats address placeholders further down (eg "Dear ((address_line_1))"), then it'll fill those in as well. It'll still prompt you to fill them in, but they'll be pre-filled.
2020-03-10 15:12:19 +00:00
'send_one_off_letter_address',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'send_one_off_step',
'send_test',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.send_test_preview',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'send_test_step',
Add endpoint to redirect from contact list to send In order to use a contact list we’re going to put you in the normal upload a spreadsheet journey. Except without having to upload again. So this commit adds an endpoint that takes the file from the contact list bucket, puts it in the same place it would have gone if you’d uploaded it, then sends you on your way.
2020-03-13 14:38:43 +00:00
'send_from_contact_list',
Allow uploaded letters to be sent if valid Added a send button which only appears on the page if the query string indicates that the PDF is valid. Before actually sending, we check that the service has the right permissions and that the metadata for the letter confirms the letter is valid (because the query string can be changed).
2019-09-09 12:22:52 +01:00
'send_uploaded_letter',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_add_email_reply_to',
'service_add_letter_contact',
'service_add_sms_sender',
Add service-specific versions of agreement page Our usability testing found that jumping out of the service when going to download the agreement made it difficult for people to find their way back to the ‘Request to go live’ page. This commit adds a duplicate, service-specific versions of these pages which have the same content but: - keep the service navigation - have a link back to the ‘Request to go live’ page
2019-05-01 08:29:32 +01:00
'service_agreement',
Add pages to let users accept the agreement online At the moment, the process for accepting the data sharing and financial agreement is: 1. download a pdf * print it out * get someone to sign it * scan it * email it back to us * we rename the file and save it in Google Drive * we then update the organisation to say the MOU is signed * sometimes we also: * print it out and get it counter-signed * scan it again * email it back to the service Let's not do that any more. When the first service for an organisation that doesn't have the agreement in place is in the process of going live, then they should be able to accept the agreement online as part of the go live flow. This commit adds the pages that let someone do that. Where the checklist shows the agreement as **[not completed]** then they can follow a link where they can download it (as happens now). From here, they should then also be able to provide some info to accept it. The info that we need is: **Version** – because we version the agreements occasionally, we need to know which version they are accepting. It may not be the latest one if they downloaded it a while ago and it took time to be signed off **Who is accepting the agreement** – this will often be someone in the finance team, and not necessarily a team member, so we should let the person either accept as themselves, or on behalf of someone else. If it's on behalf of someone else we need to the name and email address of that person so we have that on record. Obvs if it's them accepting it themselves, we have that already (so we just store their user ID and not their name or email address). We then replay the collected info back in a sort of legally binding kind of way pulling in the organisation name too. The wording we’re using is inspired by what GOV.UK Pay have. Then there’s a big green button they can click to accept the agreement, which stores their user ID and and timestamp.
2019-06-18 14:24:29 +01:00
'service_accept_agreement',
'service_confirm_agreement',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_confirm_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_confirm_delete_letter_contact',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_confirm_delete_sms_sender',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_dashboard',
'service_dashboard_updates',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_delete_email_reply_to',
Let users delete letter contact blocks Because they can delete email reply to addresses and text message senders.
2019-07-04 16:11:19 +01:00
'service_delete_letter_contact',
Highlight the new endpoints in the appropriate navigation menus Added the four new endpoints to navigation.py to determine which (if any) navigation items get highlighted when the endpoints are visited.
2018-04-30 14:18:41 +01:00
'service_delete_sms_sender',
Determine agreement by service not user’s org A user might not have a guessable organisation type, even if the service they’re working on does have an organisation set. This can happen for users with @nhs.net email addresses, for example.
2019-07-02 17:04:26 +01:00
'service_download_agreement',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_edit_email_reply_to',
'service_edit_letter_contact',
'service_edit_sms_sender',
'service_email_reply_to',
'service_letter_contact_details',
Allow deleting default letter contact blocks It’s possible to delete default letter contact blocks because there is a fallback – having a blank letter contact block. This is different to SMS senders and reply to addresses. For this to make sense it also means: - adding the ‘blank’ letter contact block to the list of letter contact blocks - having a way of setting the default back to being blank
2019-07-05 13:17:48 +01:00
'service_make_blank_default_letter_contact',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_name_change',
'service_name_change_confirm',
Fixes for tests broken by changes - corrects target page for set_email_branding to new preview step instead of itself - removed check for helper method being called in email page test - updates expected result for test of global headers to include changes to `frame-src` - updates navigation config with brand preview page
2018-08-03 17:39:58 +01:00
'service_preview_email_branding',
Show letter branding preview when selecting a brand This adds a preview pane which is visible when updating a letter brand. If JavaScript is enabled, the preview pane shows on the set-letter-branding page, and submitting the form saves updates the letter brand for a service immediately. If Javascript is not enabled, there is a separate 'Preview email branding' page which shows a preview of the brand and has a 'Save' button on it.
2019-02-15 14:47:39 +00:00
'service_preview_letter_branding',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_set_auth_type',
Let users switch channels on and off by themselves We let people do this for letters already. We should let them do it for emails and texts too, rather than have to email us.
2019-01-29 14:51:31 +00:00
'service_set_channel',
Send files by email on for everyone and only depending on service having contact details set up. Display not set up yet for send files by email row when contact_link not set up
2020-02-25 11:27:43 +00:00
'send_files_by_email_contact_details',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_set_email_branding',
'service_set_inbound_number',
'service_set_inbound_sms',
'service_set_international_sms',
'service_set_letters',
'service_set_reply_to_email',
'service_set_sms_prefix',
'service_settings',
'service_sms_senders',
Allow excluding services from live services count Adds a front end for: https://github.com/alphagov/notifications-api/pull/2417 > Sometimes we have to make a few services for what really is one > service, for example GOV.UK Pay and GOV.UK Pay Direct Debit. We also > have our own test services which aren’t included in the count of live > services. We currently count these as one service by not including > them in the beta partners spreadsheet.
2019-03-25 14:46:42 +00:00
'service_switch_count_as_live',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'service_switch_live',
Replace platform admin service setting buttons with forms Most of the existing platform admin buttons on the service settings page used to issue GET requests to switch service settings. This means they weren't protected by CSRF. On top of that as our number of service permissions increases over time a lot of buttons on the page made it hard to work with. To fix these issues we replace most of the buttons with rows in the platform admin settings table. Each setting has a 'Change' link that leads to a page with an On/Off switch form. This removes "research mode" switch completely since we're planning to deprecate it in the future and we don't expect to switch any new services into research mode at the moment. Most service permissions are now handled by a shared endpoint that is parameterized with the permission name. Some permissions that require some additional logic before they can be toggled (like document upload, which requires setting a contact address) have separate initial endpoints that redirect to `set_service_permission`. "Archive", "Suspend" and "Resume" actions are kept as buttons since they display a confirmation banner (which is a CSRF-protected form) and they're not easily represented as an On/Off switch.
2019-02-18 16:56:43 +00:00
'service_set_permission',
No emails, texts or letters for broadcast services To make the interface as simple as possible we don’t want to mix up sending other types of communication where services have the broadcast permission. This commit removes the other permissions once a service has been given the broadcast permission by a platform admin user.
2020-07-13 08:56:57 +01:00
'service_set_broadcast_permission',
Verify email address when editing reply-to address Also fix the tests
2019-05-16 17:05:55 +01:00
'service_verify_reply_to_address',
'service_verify_reply_to_address_updates',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'services_or_dashboard',
'set_free_sms_allowance',
fix request letter branding page (it can now have a null type). also fix nav.py
2019-02-05 16:33:36 +00:00
'service_set_letter_branding',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'set_sender',
'set_template_sender',
'show_accounts_or_dashboard',
'sign_in',
'sign_out',
'start_job',
'start_tour',
'styleguide',
'submit_request_to_go_live',
'support',
Direct members of the public somewhere more useful We can’t give advice to members of the public, but increasingly we’re seeing them try to use our support form to ask. It would be better for them if we can direct them straight to somewhere more useful, before they have the chance to raise a support ticket. This commit replaces the report a problem/ask a question triaging for users who aren’t signed in. It’s not possible for non-signed-in users to raise an priority 1 ticket, so we never need to triage the tickets in this way. Instead we can triage people based on whether they work in the public sector or not. If they do then we send them on to the feedback form. If not then they go to a new page which contains some useful links. We’ve chosen these links based on some analysis of the support tickets we’ve received recently[1] 1. https://docs.google.com/spreadsheets/d/1uBQn-ZnCYfz6ltFaUKZpytgvBF0-MeshCLZ1cD74R0c/edit?usp=sharing
2020-03-24 15:01:42 +00:00
'support_public',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'suspend_service',
'template_history',
'template_usage',
'terms',
'thanks',
'triage',
'trial_mode',
Add new pages to navigation dictionaries
2019-04-11 11:47:09 +01:00
'trial_mode_new',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'trial_services',
'two_factor',
'two_factor_email',
'two_factor_email_sent',
Add interstitial page before using email auth token Some email clients will pre-fetch links in emails to check whether they’re safe. This has the unfortunate side effect of claiming the token that’s in the link. Long term, we don’t want to let the link be used multiple times, because this reduces how secure it is (eg someone with access to your browser history could re-use the link even if you’d signed out). Instead, this commit adds an extra page which is served when the user clicks the link from the email. This page includes a form which submits to the actual URL that uses the token, thereby not claiming the token as soon as the page is loaded. For convenience, this page also includes some Javascript which clicks the link on the user’s behalf. If the user has Javascript turned off they will see the link and can click it themselves. This is going on the assumption that whatever the email clients are doing when prefetching the link doesn’t involve running any Javascript. This Javascript is inlined so that: - it is run as fast as possible - it’s more resilient – even if our assets domain is unreachable or the connection is interrupted, it will still run
2020-05-04 12:27:51 +01:00
'two_factor_email_interstitial',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'update_email_branding',
Add update_letter_branding view function This works in a similar way to the create_letter_branding view function, but with a few minor differences: * Since we already have a file, uploading a file is no longer required (since we can just use the current file if a new one is not uploaded) * We save the changes in the database, then upload the new files to S3. If saving to S3 raises an error, we now rollback the database changes to prevent any errors when trying to view letters with the original logo.
2019-02-11 15:31:12 +00:00
'update_letter_branding',
Let users upload a contact list to use later We increasingly have teams wanting to do business-continuity type messaging. They might be without access to their normal systems, which is where they would otherwise go to get the list of email addresses or phone numbers. So we want to give them a place in Notify where they can store their spreadsheets and use them at a later date. For the initial pass we’re going to scope this to only allowing spreadsheets with one column, ie just phone numbers/email addresses. This is because: - it minimises the amount of personal info we’re storing - it reduces the chance of getting a placeholder error when you go to send the message, which is probably a high-stress situation where you might not be able to re-generate the file The code for this is mostly copied from the existing upload CSV journey. It’s quite duplicative, but that’s what I needed to do to get this out quickly. There are opportunities for refactoring later. Similarly, I would have liked to split this up into better commit messages, but it really was a case of just bashing code out until it worked 😳 This commit does not: - implement the ‘view a contact list page’ (it just has a placeholder because the API isn’t ready at the moment) - link to this page (because it’s not ready to use yet)
2020-03-12 16:13:18 +00:00
'upload_contact_list',
'check_contact_list',
'save_contact_list',
'contact_list',
Let users delete a contact list Follows our standard pattern of confirming with a red banner for actions that are destructive.
2020-03-18 13:37:39 +00:00
'delete_contact_list',
Add letter upload form which redirects to blank preview page Added a form to upload a single letter. Currently this only uses the form to validate that a file is submitted and that the file is a PDF. If either of these validations fail, the form will display an error. Otherwise, we redirect to a new preview page which just has the filename as the heading for now.
2019-09-06 10:39:23 +01:00
'upload_letter',
'uploaded_letter_preview',
Add page to show all uploaded letters Because we won’t be showing uploaded letters individually on the uploads page any more we need a way of listing them. This should be by printing day, to match how we’re grouping them on the uploads page. This code reuses the notifications.html template, but flips the precedence of the filename and recipient because I reckon when you’re looking at uploads you’re thinking filename-first.
2020-05-11 10:52:43 +01:00
'uploaded_letters',
Add 'Uploads' hub and navigation The uploads hub is just a page with text for now - there are no actions available on the page. It is linked to from a new 'Uploads' menu item on the left of the page which is only visible if your service has the `letter` and `upload_letters` permissions and if the current user has permissions to send messages.
2019-08-09 08:44:11 +01:00
'uploads',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'usage',
New report on platform-admin/reports page to get the usage for all services.
2019-08-23 17:14:04 +01:00
'usage_for_all_services',
Add view that displays user information, including: - name - email - phone number - services - last login - failed login attempts if any The view can be accessed from results of find_users_by_email logged_in_at added to User serialization on admin frontend as a part of this work
2018-07-10 17:24:20 +01:00
'user_information',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'user_profile',
'user_profile_email',
'user_profile_email_authenticate',
'user_profile_email_confirm',
'user_profile_mobile_number',
'user_profile_mobile_number_authenticate',
'user_profile_mobile_number_confirm',
'user_profile_name',
'user_profile_password',
make sure tests all populate the platform admin field it's always returned by the API
2019-06-14 15:14:00 +01:00
'user_profile_disable_platform_admin_view',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'using_notify',
'verify',
'verify_email',
'view_job',
'view_job_csv',
'view_job_updates',
'view_jobs',
'view_letter_notification_as_preview',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_letter_template_preview',
Show letter preview once file is uploaded This shows the sanitised letter preview if the file had no validation errors or the preview with the overlay if it failed validation.
2019-09-09 10:59:32 +01:00
'view_letter_upload_as_preview',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'view_notification',
'view_notification_updates',
'view_notifications',
'view_notifications_csv',
'view_provider',
'view_providers',
'view_template',
'view_template_version',
change letter previews to be in the no_cookies blueprint this blueprint should be applied to every endpoint that is loaded async (as in via a src tag on an img, iframe, etc)
2019-11-29 11:40:49 +00:00
'no_cookie.view_template_version_preview',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
'view_template_versions',
Rename endpoint to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:03:40 +01:00
'guest_list',
Rename URL to remove term ‘whitelist’ See c31264d4c for rationale. To avoid confusion the codebase should use the same terminology as the UI.
2020-06-12 09:07:29 +01:00
'old_guest_list',
Update who_its_for to who_can_use_notify
2020-05-20 15:54:15 +01:00
'who_can_use_notify',
Redirect old URL
2020-05-21 11:17:44 +01:00
'who_its_for',
Add a tour for users new to broadcast services This is an initial, prototype-quality attempt at introducing some kind of tour for users new to broadcasting. A lot of the users we’re speaking to don’t have a good concept of what broadcasting means, which is causing usability problems down the line. We did a similar thing in the early days of Notify to explain the concept of message templates and personalisation.
2020-08-03 13:37:34 +01:00
'broadcast_tour',
Add a dashboard for broadcast services This is just a placeholder for now
2020-07-08 11:34:16 +01:00
'broadcast_dashboard',
Make the broadcast dashboard update via AJAX Same technique as we use for other pages that update via AJAX. I’ve split the page up into separate chunks because the DiffDOM library we use finds it easier to work out what’s changed when there are fewer elements/a shallower tree.
2020-07-14 13:39:29 +01:00
'broadcast_dashboard_updates',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'broadcast',
'preview_broadcast_areas',
'choose_broadcast_library',
'choose_broadcast_area',
Let users select electoral wards of local authorities If a library has groups, we should show a link instead of selecting the group directly. Then we can give the user the choice of selecting the whole of that group, or specific areas within the group. For now the only libraries we have with groups are local authorities, which group electoral wards.
2020-07-31 16:20:37 +01:00
'choose_broadcast_sub_area',
Add some views for selecting broadcast areas These are just so we have some pages to click through for now. They don’t use real templates, or any of the broadcast stuff from the database. But I think it’s useful to get some skeleton pages in first so that we can see the map etc working in production, then build on that, without having to do it all in one mega PR. For that reason there are two short term things I’ve done in this commit which should be revisited soon: - no tests for the endpoints - data about which areas are selected is stored in the session
2020-07-06 10:53:14 +01:00
'remove_broadcast_area',
'preview_broadcast_message',
Add a page to view a single broadcast This commit adds a page to view a single broadcast. This is important for two reasons: - users need an audit of what happened when, and who else was involved in approving or cancelling a broadcast - we need a place to put actions (approving, cancelling) on a broadcast so that you can confirm details of the message and the areas before performing the action
2020-07-10 14:06:00 +01:00
'view_broadcast_message',
Add button to approve broadcast Since new broadcasts will go into `pending-approval`, we now need a way of approving them. This commit adds a button to this page to start (or approve) the broadcast. This button is wrapped in a bordered box, to emphasise that it’s something consequential.
2020-07-17 08:07:44 +01:00
'approve_broadcast_message',
Add a link to reject a broadcast If a broadcast definitely shouldn’t go out (for example because it has a spelling mistake or is going to the wrong areas) then we should have a way of removing it. Once it’s removed no-one else can approve it, and it isn’t cluttering up the dashboard. This is a link (because it’s a secondary action) and red (because it’s destructive, in that it’s throwing away someone’s work).
2020-07-17 08:07:44 +01:00
'reject_broadcast_message',
Allow broadcasts to be cancelled Currently this is a `get` request from the dashboard. Once we have a page for viewing an individual broadcast it should probably show there instead and be a `get`/confirm/`post` loop like for deleting a template.
2020-07-10 09:16:36 +01:00
'cancel_broadcast_message',
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
}
Reference in New Issue Copy Permalink