# email

Canonical page: https://docs.ovok.com/settings-and-features/features/email

Lets Bots in the project send email. It controls email sent **by your automations**, not the emails Ovok sends on its own behalf.

| | |
| --- | --- |
| Type | Project feature |
| Value in `features` | `email` |
| Change with | `PATCH /v1/projects/me/features` (replaces the whole list) |
| Who can change it | Project admin. Any practitioner can read the list. |
| On for new projects | Yes |
| Needs | [bots](/settings-and-features/features/bots) |
| When off | A Bot's attempt to send email is refused with `403` |

## What it enables [#what-it-enables]

A Bot sends email through the Bot SDK's `sendEmail` call, which posts to `/email/v1/send` on the FHIR host. The platform accepts the send only when the Bot's project has `email` and the caller is a project admin.

## Turn it on [#turn-it-on]

```bash
curl --request PATCH \
  --url 'https://api.sandbox.ovok.com/v1/projects/me/features' \
  --header "Authorization: Bearer ${OVOK_TOKEN}" \
  --header 'Content-Type: application/json' \
  --data '{"features":["bots","cron","email","transaction-bundles","websocket-subscriptions"]}'
```

## What this feature does not control [#what-this-feature-does-not-control]

| Email | What controls it |
| --- | --- |
| Invitations, password resets and other messages Ovok sends itself | Not this feature, and not [MAILING_ENABLED](/settings-and-features/settings/mailing-enabled). They are sent when the template is [mapped](/email-templates/map-templates) and its provider is `ready`: see [Email templates](/email-templates). |
| Where the links in those emails point | [PATIENT_APP_URL](/settings-and-features/settings/patient-app-url) and [PRACTITIONER_APP_URL](/settings-and-features/settings/practitioner-app-url) |

Turning `email` off therefore does not stop invitation or password-reset emails.

## What callers see when it is off [#what-callers-see-when-it-is-off]

`403` (`Forbidden`) from `/email/v1/send`. In a Bot this surfaces as an error from `sendEmail`.

## Gotchas [#gotchas]

- **Two conditions, one `403`.** The send is refused if the project lacks `email` **or** the caller is not a project admin. If a Bot still gets `403` with the feature on, check the Bot's membership as well as the features list.
- **A successful response means "accepted", not "delivered".** Delivery depends on the platform's mail configuration, and the call does not report whether a message was actually sent.
- **`email` without `bots` is useless.** Bots are the only way to reach it. Add [bots](/settings-and-features/features/bots).
- **Projects created before this was a default can lack it.** Call `GET /v1/projects/me/features` and check.

## Related [#related]

- [Email templates](/email-templates), for the emails Ovok sends itself
- [bots](/settings-and-features/features/bots)
- [MAILING_ENABLED](/settings-and-features/settings/mailing-enabled)
- [PATIENT_APP_URL](/settings-and-features/settings/patient-app-url)
