> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/email-this-issue/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/email-this-issue/faq/email-this-issue-for-jira-cloud-how-to-configure-the-email-this-issue-addon-user-in-jira-cloud.md).

# How to configure the Email This Issue addon user in Jira Cloud?

Each Jira Cloud addon has its own user account created in the Jira Cloud systems where the addon is enabled. The Email This Issue addon user is called **Email This Issue** with username `addon_com.metainf.jira.plugin.emailissue`.

The addon user must be properly configured to benefit from all features and exploits all potentials of Email This Issue for Jira Cloud. The use cases that require special attention are the following:

## Sending manual (ad-hoc) emails <a href="#howtoconfiguretheemailthisissueaddonuserinjiracloud-sendad-hocemails" id="howtoconfiguretheemailthisissueaddonuserinjiracloud-sendad-hocemails"></a>

In order to send issues in emails manually, the add-on user must have at least read access to the issue.

* Add *Browse Projects* and *Add Comments* permissions to the addon user.
  * Make sure the addon user is member of the project role **atlassian-addons-project-access**
  * Grant *Browser Projects, Add Comments* for this project role in the permission scheme
* Add the add-on user to all Issue Security levels either directly or via the addon project role (as described above).

## Sending emails to individual users and groups <a href="#howtoconfiguretheemailthisissueaddonuserinjiracloud-sendemailstoindividualusersandgroups" id="howtoconfiguretheemailthisissueaddonuserinjiracloud-sendemailstoindividualusersandgroups"></a>

To send emails to individual users and group **Browse Users Global Permission** is needed.


---

# 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:

```
GET https://docs.meta-inf.hu/email-this-issue/faq/email-this-issue-for-jira-cloud-how-to-configure-the-email-this-issue-addon-user-in-jira-cloud.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.