darkhelm/notifications-admin
1
0
Fork 0
mirror of https://github.com/GSA/notifications-admin.git synced 2025-12-10 15:13:40 -05:00
Code Issues Packages Projects Releases Wiki Activity
Files
main
notifications-admin/app/navigation.py

360 lines
11 KiB
Python
Raw Permalink 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
Replace send_messages and manage_service strings across application with ServicePermission.SEND_MESSAGES and ServicePermission.MANAGE_SERVICE types
2025-07-15 23:56:58 -07:00
from app.enums import ServicePermission
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
class Navigation:
mapping = {}
Update dashboard and template flow (#514) * Updated header and footer * Moved files around and updated gulpfile to correct the build process when it goes to production * Updated fonts * Adjusted grid templating * Adding images to assets * Updated account pages, dashboard, and pages in message sending flow * Updated the styling for the landing pages in the account section once logged in
2023-06-08 13:12:00 -04:00
selected_class = "usa-current"
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.
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
self.get_endpoint_with_blueprint(endpoint)
for endpoint in endpoints
}
for navigation, endpoints in self.mapping.items()
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 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):
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
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
def is_selected(self, navigation_item):
if request.endpoint in self.mapping[navigation_item]:
Update dashboard and template flow (#514) * Updated header and footer * Moved files around and updated gulpfile to correct the build process when it goes to production * Updated fonts * Adjusted grid templating * Adding images to assets * Updated account pages, dashboard, and pages in message sending flow * Updated the styling for the landing pages in the account section once logged in
2023-06-08 13:12:00 -04:00
return self.selected_class
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
return ""
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
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
Simplify tests for excluded navigation endpoints Previously each navigation class had a list of endpoint to "exclude", which was only used in tests to ensure that all endpoints in the app were covered: either they are present in navigation, or excluded. However, over time the "exclude" lists have grown long and repetitive, and maintaining each of them individually adds extra work [1][2]. This switches to a more DRY approach, where the list of excluded endpoints is defined once, close to the single point of use in the test. Note the resulting test is _slightly_ less prescriptive, as it will now pass if an endpoint exist one in navigation, even if it should also exist in another. This seems a reasonable compromise. [1]: https://github.com/alphagov/notifications-admin/pull/3788/files#r572809972 [2]: https://github.com/alphagov/notifications-admin/pull/3794/files#diff-39387df3a9f89b313976957e7b5457be20deab1017b2d895541b142b957f1972
2021-02-26 18:19:47 +00:00
def get_endpoint_with_blueprint(endpoint):
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
return endpoint if "." in endpoint else "main.{}".format(endpoint)
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
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 = {
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"support": {
"support",
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
},
Fixed error
2024-11-13 10:01:33 -05:00
"best_practices": {
"best_practices",
Added subnav to fix css
2024-11-13 10:30:06 -05:00
"clear_goals",
"rules_and_regulations",
"establish_trust",
"write_for_action",
"multiple_languages",
add carrier column to reports
2024-11-21 15:08:49 -08:00
"benchmark_performance",
Added link to new guidance page that enables navigating
2024-11-04 11:44:45 -05:00
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"using_notify": {
"get_started",
"pricing",
"trial_mode_new",
"message_status",
changing guidance to how-do
2025-01-22 10:41:29 -08:00
"how_to",
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
},
Committing before merge
2023-10-12 10:21:11 -04:00
"accounts-or-dashboard": {
- Updated nav to allow for the active state throughout Service sub-nav - Fixed test for using-notify broken link
2023-10-12 13:52:03 -04:00
"conversation",
"service_dashboard",
"template_usage",
"view_notification",
"action_blocked",
"add_service_template",
"check_messages",
"check_notification",
"choose_template",
"choose_template_to_copy",
"confirm_redact_template",
"conversation_reply",
"copy_template",
"delete_service_template",
"edit_service_template",
"manage_template_folder",
Replace send_messages and manage_service strings across application with ServicePermission.SEND_MESSAGES and ServicePermission.MANAGE_SERVICE types
2025-07-15 23:56:58 -07:00
ServicePermission.SEND_MESSAGES,
- Updated nav to allow for the active state throughout Service sub-nav - Fixed test for using-notify broken link
2023-10-12 13:52:03 -04:00
"send_one_off",
"send_one_off_step",
"send_one_off_to_myself",
"set_sender",
"set_template_sender",
"view_template",
"view_template_version",
"view_template_versions",
"uploads",
"view_job",
"view_jobs",
- Updated navigation file to show active atate in top nav - Changing route back to - instead of _ so it won't break tests, also it was a mistake
2023-10-12 13:40:41 -04:00
"usage",
Committing before merge
2023-10-12 10:21:11 -04:00
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"documentation": {
"documentation",
"integration_testing",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"user-profile": {
"user_profile",
"user_profile_confirm_delete_mobile_number",
"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_mobile_number_delete",
"user_profile_name",
"user_profile_password",
notify-admin-931 initial
2023-11-30 12:39:37 -08:00
"user_profile_preferred_timezone",
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07: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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"platform-admin": {
"archive_user",
"change_user_auth",
"clear_cache",
"find_services_by_name",
"find_users_by_email",
"live_services",
"live_services_csv",
"notifications_sent_by_service",
"get_billing_report",
"get_users_report",
"get_daily_volumes",
add front end for download all users
2024-08-06 11:31:05 -07:00
"download_all_users",
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"get_daily_sms_provider_volumes",
"get_volumes_by_service",
"organizations",
"platform_admin",
"platform_admin_list_complaints",
"platform_admin_reports",
"platform_admin_splash_page",
"suspend_service",
"trial_services",
"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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"sign-in": {
"revalidate_email_sent",
"sign_in",
"two_factor_sms",
"two_factor_email",
"two_factor_email_sent",
"two_factor_email_interstitial",
"verify",
"verify_email",
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
},
}
Removed all govuk css (#2814) * Removed all govuk css * Updated reference files * Removing govuk js * Fixed casing for modules, removed unused page * Got more reference images * Updated template page * Removed govuk padding util * Updated hint to uswds hint * More govuk cleanup * Commiting backstopjs ref files * Fixed all unit tests that broke due to brittleness around govuk styling * Added new ref images * Final removal of govuk * Officially removed all govuk references * Updated reference file * Updated link to button * UI modernization * Cleanup * removed govuk escaping tests since they are no longer needed * Fix CodeQL security issue in escapeElementName function - Escape backslashes first before other special characters - Prevents potential double-escaping vulnerability - Addresses CodeQL alert about improper string escaping * Found more govuk removal. Fixed unit tests * Add missing pipeline check to pre-commit * updated test * Updated e2e test * More update to e2e test * Fixed another e2e test * Simple PR comments addressed * More updates * Updated backstop ref files * Refactored folder selection for non-admins * Updated redundant line * Updated tests to include correct mocks * Added more ref files * Addressing carlos comments * Addressing Carlo comments, cleanup of window initing * More cleanup and addressing carlo comments * Fixing a11 scan * Fixed a few issues with javascript * Fixed for pr * Fixing e2e tests * Tweaking e2e test * Added more ref files and cleaned up urls.js * Fixed bug with creating new template * Removed brittle test - addressed code ql comment * e2e race condition fix * More e2e test fixes * Updated e2e tests to not wait for text sent * Updated test to not wait for button click response * Made tear down more resilent if staging is down * reverted e2e test to what was working before main merge * Updated backstopRef images * Updated gulp to include job-polling differently
2025-10-06 09:38:54 -04:00
# header HTML now comes from USWDS so requires a boolean, not an attribute
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
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 = {
created new activity page
2024-07-18 15:57:29 -07:00
"activity": {
"all_jobs_activity",
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"dashboard": {
"conversation",
"service_dashboard",
"template_usage",
"view_notification",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"templates": {
"action_blocked",
"add_service_template",
"check_messages",
"check_notification",
"choose_template",
"choose_template_to_copy",
"confirm_redact_template",
"conversation_reply",
"copy_template",
"delete_service_template",
"edit_service_template",
"manage_template_folder",
Replace send_messages and manage_service strings across application with ServicePermission.SEND_MESSAGES and ServicePermission.MANAGE_SERVICE types
2025-07-15 23:56:58 -07:00
ServicePermission.SEND_MESSAGES,
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"send_one_off",
"send_one_off_step",
"send_one_off_to_myself",
"set_sender",
"set_template_sender",
"view_template",
"view_template_version",
"view_template_versions",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"uploads": {
"uploads",
"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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"team-members": {
"confirm_edit_user_email",
"confirm_edit_user_mobile_number",
"edit_user_email",
"edit_user_mobile_number",
"edit_user_permissions",
"invite_user",
"manage_users",
"remove_user_from_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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"usage": {
"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
},
Merge branch 'main' of https://github.com/GSA/notifications-admin into 1043-move-account-info-into-utility-nav
2024-01-03 13:51:11 -05:00
"user-profile": {
"user_profile",
"user_profile_confirm_delete_mobile_number",
"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_mobile_number_delete",
"user_profile_name",
"user_profile_password",
"user_profile_preferred_timezone",
"user_profile_disable_platform_admin_view",
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"settings": {
"link_service_to_organization",
"service_add_email_reply_to",
"service_add_sms_sender",
"service_confirm_delete_email_reply_to",
"service_confirm_delete_sms_sender",
"service_edit_email_reply_to",
"service_edit_sms_sender",
"service_email_reply_to",
"service_name_change",
"service_set_auth_type",
"service_set_channel",
"send_files_by_email_contact_details",
"service_set_inbound_number",
"service_set_inbound_sms",
"service_set_international_sms",
"service_set_reply_to_email",
"service_set_sms_prefix",
"service_verify_reply_to_address",
"service_verify_reply_to_address_updates",
"service_settings",
"service_sms_senders",
"set_free_sms_allowance",
"set_message_limit",
"set_rate_limit",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"api-integration": {
"api_callbacks",
"api_documentation",
"api_integration",
"api_keys",
"create_api_key",
"delivery_status_callback",
"received_text_messages_callback",
"revoke_api_key",
"guest_list",
"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
},
}
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 = {
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"send-one-off": {
"choose_template",
"send_one_off",
"send_one_off_step",
"send_one_off_to_myself",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"sent-messages": {
"view_notification",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"uploads": {
"view_jobs",
"view_job",
"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
}
Merge branch 'main' of https://github.com/GSA/notifications-admin into 1043-move-account-info-into-utility-nav
2024-01-03 13:51:11 -05:00
class SecondaryNavigation(Navigation):
mapping = {
"settings": {
"link_service_to_organization",
"service_add_email_reply_to",
"service_add_sms_sender",
"service_confirm_delete_email_reply_to",
"service_confirm_delete_sms_sender",
"service_edit_email_reply_to",
"service_edit_sms_sender",
"service_email_reply_to",
"service_name_change",
"service_set_auth_type",
"service_set_channel",
"send_files_by_email_contact_details",
"service_set_inbound_number",
"service_set_inbound_sms",
"service_set_international_sms",
"service_set_reply_to_email",
"service_set_sms_prefix",
"service_verify_reply_to_address",
"service_verify_reply_to_address_updates",
"service_settings",
"service_sms_senders",
"set_free_sms_allowance",
"set_message_limit",
"set_rate_limit",
"confirm_edit_user_email",
"confirm_edit_user_mobile_number",
"edit_user_email",
"edit_user_mobile_number",
"edit_user_permissions",
"invite_user",
"manage_users",
"remove_user_from_service",
"user_profile",
"user_profile_confirm_delete_mobile_number",
"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_mobile_number_delete",
"user_profile_name",
"user_profile_password",
"user_profile_preferred_timezone",
"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
class OrgNavigation(Navigation):
mapping = {
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"dashboard": {
"organization_dashboard",
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
},
Moved usage to it's own route to not confuse with dashboard
2025-10-14 12:27:15 -07:00
"usage": {
"organization_usage",
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"settings": {
"edit_organization_billing_details",
"edit_organization_domains",
"edit_organization_name",
"edit_organization_notes",
"edit_organization_type",
"organization_settings",
Add selected navigation for organisations page To match how the navigation works for a single service.
2018-04-25 13:17:47 +01:00
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"team-members": {
"edit_organization_user",
"invite_org_user",
"manage_org_users",
"remove_user_from_organization",
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
},
notify-api-412 use black to enforce python coding style
2023-08-25 09:12:23 -07:00
"trial-services": {
"organization_trial_mode_services",
},
"billing": {
"organization_billing",
Add new 'Billing' page for organisations We want organisation team members to be able to see the MOU details for their organisation. This change creates a new page called billing, which contains these details. It's only visible to platform admin users now - the plan is to add more information to this page, then to make it visible to all organisation users. The page showing the MOU covers the case of when agreement_signed is True, when an agreement_signed is False, and when agreement_signed is None. The case when an agreement_signed is None is very rare - it signifies that the agreement is not signed but that we have some service-specific agreements in place. We only have a few organisations in this state, so it's unlikely that the content for this scenario will be seen. When an organisation has signed the agreement we may know the full details (signing date, version signed, the person who signed it or who it was signed on behalf of), or we may only have the name of the person who signed the agreement. We show the more detailed content if possible, and a less detailed version of the content if not. There's a new route for downloading the agreement which is almost identical to the existing `.service_download_agreement` route (plus the test is almost the same), except that it takes an organisation ID instead of a service ID.
2021-12-07 13:42:44 +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
}
Reference in New Issue Copy Permalink