# Tasks

There is a built-in Tasks component *RequestApprovalEmail.* This component is more like a template, something you can use and built your own version that better fits into your platform. Although, even this component may be useful. 

![](/files/-MVRWZmzgtBgTXiiUrri)

This component sends one email to the *requestor* and another email to the *approver.* It uses the Appmixer Mandrill account to do that. Those emails contain a few Appmixer related information - *Reply-To, From Email, ...* These can be configured using Backoffice.

![Possible configuration for RequestApprovalEmail component.](/files/-MXqkEPSathTKNcmpitO)

The email contains an Appmixer logo by default, you can change that by setting *logoURL key in the* Backoffice and pointing that to your own product log.

The last thing is the PEOPLE\_TASKS\_DASHBOARD\_URL environment variable that has to be set for the Appmixer engine. This URL will be used in the *RequestApprovalEmail* component to create links in the email that is sent to the approver. This has to point to a page in your application that will display the tasks. That is a page that implements the [*appmixer.ui.PeopleTasks*](broken://pages/-Lvp9T2V9gl_MeKjrr9m#appmixer-ui-peopletasks) widget.


---

# Agent Instructions: 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.appmixer.com/6.0/5.0/app-registration/utils/tasks.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.