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

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-d20120b67e233d6228f9c72560346d0748a9169b%2Ftasks-1.png?alt=media)

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.](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-7a30349da983bc97597dc6d3c290721f9550c4c2%2Ftasks-2.png?alt=media)

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*](https://github.com/clientIO/appmixer-docs-gitbook/blob/v5.2/app-registration/utils/broken-reference/README.md) widget.