> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/newsroom-planner/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/newsroom-planner/admin-guide/settings/configuration/email-service.md).

# Email service

```javascript
{
    "enable": true, // {1}
    "sendEndpoint": "${DBKS:EMAIL_SERVICE_SEND}", // {2}
    "listEndpoint": "${DBKS:EMAIL_SERVICE_LIST}", // {3}
    "serviceDomain": "${DBKS:EMAIL_SERVICE_DOMAIN}" // {4}
}
```

1. If email service should be displayed in app or not
2. URL to Naviga mail service Send (sendmail.Email/Send)
3. URL to Naviga mail service List (sendmail.Email/GetThread)
4. URL to the mail service domain (i.e. saas-stage.infomaker.io) 

### Structured Email template on share assignment

In NRP version 6.5.0, the email received upon share assignment is now presented in a more structured format, containing all the details available in the assignment, providing a comprehensive overview.

* Assignment name appears as a clickable link, which opens the assignment in a modal view within the "My Assignment" section.
* Connected Article section displays all articles linked to the assignment. Clicking on an article opens it directly in Writer for editing.
* The email now contains all the information included in the assignment, providing a comprehensive overview.

<figure><img src="https://content.gitbook.com/content/N4jAJdwyxhJ26rM91BZ7/blobs/4baQpHR9lGjAVaokSIW7/Email%20template.png" alt=""><figcaption><p>Structured email received on share assignment</p></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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.navigaglobal.com/newsroom-planner/admin-guide/settings/configuration/email-service.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.