> 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/2021.2-changes-overview/sharing-emails-between-linked-work-items.md).

# Sharing Emails between Linked Work Items

v2021.2

As part of supporting work being carried out across multiple Cases & Tickets, you can share emails between Linked work items to allow them to be viewed more widely. You can even do this for work items which you don't have permissions on.

{% embed url="<https://media.enate.net/WorkManager/13LinkedWorkItems/SharingEmailsBetweenLinkedWorkItems.mp4>" %}

You can share emails between linked work items in two ways.

**1. From an existing email -** Clicking on the '+' icon at the top of an existing email in the timeline and selecting the relevant work item you wish to share the email with.

**2. From composing new email -** Another way is when writing a new email, you can simply add the work item reference number into the To / CC / BCC of an email by clicking the '+' icon, just as you wold when adding an email address:

You can even use this approach when you just want to share emails between linked work items, without needing to add an email address.

{% hint style="info" %}
Please note that you can only share emails between work items that are linked. Additionally, once an email has been shared between work items, it cannot be unshared.
{% endhint %}

The email will be sent as normal to any emails addresses specified, and it will also be shared with the selected work items.

When someone responds to the shared email, that response will be attached to both work items.


---

# 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.enate.net/whats-new/older-versions/changes-overview-older-versions/2021.2-changes-overview/sharing-emails-between-linked-work-items.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.