> For the complete documentation index, see [llms.txt](https://docs.enate.net/whats-new/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.6-changes-overview/email-routes-page-adjustments.md).

# Email Routes Page Adjustments

We have adjust the design of our Email Routes configuration page to help optimise performance, speed and ease of use, especially when you are working with a large volume of email routes.&#x20;

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2FuC2TUrOPj5jWdhQHO4o1%2FEmail%20routes%20page.PNG?alt=media&amp;token=26510cd4-c0e5-4ad9-8bf1-d340da0e5b29" alt=""><figcaption></figcaption></figure>

Changes which have been made here are as follows:

#### Filter to show just one Connector

At header level, you can search to filter down your view to just one Connector&#x20;

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F3peV5w3tMtyVYUa8w38t%2FHeaderConnector.PNG?alt=media&amp;token=0bb92c3a-246b-4785-a6df-670799884192" alt=""><figcaption></figcaption></figure>

#### Search by Connector details within each section&#x20;

You can now search for a route at a connector-level, based on its email address, process and/or Ticket category (if relevant).

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2Ff56aYEng78fr4L8YN5oa%2FConnector%20Search.PNG?alt=media&amp;token=6e27f9b7-ab36-4a65-a4f1-17a87311efac" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Note that these searches are all now 'start with' searches rather than full wildcard searches, e.g. if you type 'France' it will search for items 'France\*' rather than \*France\*..
{% endhint %}

#### Quick-create Routes from Connector section shortcut

Additionally, as a useful shortcut you now have to ability to add a new email route directly within a specific email connector itself - clicking on the '+' icon next to a connector will bring up the 'Create an Email Route' pop-up with the email connector name already filled it.

#### Folder Filter for Graph API Routes

For Graph API routes, we've moved the option to view folders as an additional filter at the top of the screen.

#### Section by Section display

Note that as part of these changes you will now only be able to expand a single Connector section at one time.

<figure><img src="https://1296463846-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8xJkS0SKlesb8bmVBtGc%2Fuploads%2F2lFsePhKAhJfdxDKAaEj%2FSection%20by%20Section.PNG?alt=media&amp;token=94d43521-54c5-439b-b8c5-5c944393d43f" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.enate.net/whats-new/older-versions/changes-overview-older-versions/2022.6-changes-overview/email-routes-page-adjustments.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
