mirror of
https://github.com/GSA/notifications-admin.git
synced 2026-09-02 17:48:50 -04:00
b68784207b
The first users of multiple email reply to addresses will be using the API. This means that the need to be able to specify the ID of the reply to address they want. We chose to implement it like this instead of by passing the address in directly because that means deploying code. For some teams deploying code can take weeks, and we’d like to let teams have the flexibility to make changes faster than this. Same as for templates, you shouldn’t have to go to the _edit_ page in order to get the ID. This means listing them on the page where you see all the reply to addresses. Listing the IDs like this means that it’s not really a table any more, because the information isn’t organised in columns. So I think it makes sense to reuse the pattern from the manage team page, which has a similar relationship between the information.
67 lines
2.2 KiB
HTML
67 lines
2.2 KiB
HTML
{% extends "withnav_template.html" %}
|
||
{% from "components/api-key.html" import api_key %}
|
||
{% from "components/page-footer.html" import page_footer %}
|
||
{% from "components/table.html" import row_group, row, text_field, edit_field, field, boolean_field, list_table %}
|
||
|
||
{% block service_page_title %}
|
||
Email reply to addresses
|
||
{% endblock %}
|
||
|
||
{% block maincolumn_content %}
|
||
|
||
<div class="grid-row bottom-gutter">
|
||
<div class="column-two-thirds">
|
||
<h1 class="heading-large">
|
||
Email reply to addresses
|
||
</h1>
|
||
</div>
|
||
<div class="column-one-third">
|
||
<a href="{{ url_for('.service_add_email_reply_to', service_id=current_service.id) }}" class="button align-with-heading">Add email address</a>
|
||
</div>
|
||
</div>
|
||
<div class="user-list">
|
||
{% if not reply_to_email_addresses %}
|
||
<div class="user-list-item">
|
||
<span class="hint">You haven’t added any email reply to addresses yet</span>
|
||
</div>
|
||
{% endif %}
|
||
{% for item in reply_to_email_addresses %}
|
||
<div class="user-list-item">
|
||
<h3>
|
||
<span class="heading-small">{{ item.email_address }}</span> <span class="hint">
|
||
{%- if item.is_default -%}
|
||
(default)
|
||
{% endif %}
|
||
</span>
|
||
</h3>
|
||
<ul class="tick-cross-list">
|
||
<li class="tick-cross-list-edit-link">
|
||
<a href="{{ url_for('.service_edit_email_reply_to', service_id =current_service.id, reply_to_email_id = item.id) }}">Change</a>
|
||
</li>
|
||
</ul>
|
||
{{ api_key(item.id, thing="ID") }}
|
||
</div>
|
||
{% endfor %}
|
||
</div>
|
||
<div class="grid-row">
|
||
<div class="column-five-sixths">
|
||
<p>
|
||
Your emails will be sent from
|
||
{{ current_service.email_from }}@notifications.service.gov.uk
|
||
</p>
|
||
<p>
|
||
This is so they have the best chance of being delivered.
|
||
This email address can’t receive replies.
|
||
</p>
|
||
<p>
|
||
Set up separate email addresses to receive replies
|
||
from your users.
|
||
{% if current_service.restricted and not reply_to_email_addresses %}
|
||
Your service can’t go live until you’ve added at least one
|
||
reply to address.
|
||
{% endif %}
|
||
</p>
|
||
</div>
|
||
</div>
|
||
{% endblock %}
|