# Notifications

Platform emails by category: who gets them, how often and how they are chosen or turned off.

Source: https://ardumaker.com/en/docs/notificaciones/

- Category: Payments and administration
- Status: Available
- Requirements: An account with a verified email
- MCP tools: No MCP tools: it is used from the dashboard.

## What can you do with it?

- Choose per category and per company: immediately, daily digest, weekly digest or do not send.
- Let an admin set the company rule and add recipients, for example someone from accounting to billing.
- Unsubscribe from a category from the email itself, without logging in.

## When should you use it?

When too many deployment notices arrive, or when the person who pays needs billing emails without being an admin.

## How does it work in ArduMaker?

| Category | Mandatory |
| --- | --- |
| Account security | Yes |
| Legal | Yes |
| Billing | No |
| Apps and deploys | No |
| VPS | No |
| Calendar | No |
| Schools | No |
| Product | No |

The decision order is: mandatory, company access, what the person chose, the company rule and, last, the default. A company cannot force an email on someone who turned it off.

- Repeated notices for the same deploy within 10 minutes are grouped.
- There is a per-address cap of 12 optional emails per hour and 40 per day; anything above goes to the digest.
- The unsubscribe link expires after 60 days. Opening it does not unsubscribe: you must confirm.

## What actually changes?

Preferences and rules are stored per person, category and company. Each send leaves one delivery per recipient with its state: sent, grouped, skipped, suppressed, failed or bounced.

## Diagram

**From an event to an email**

```text
Event (charge, deploy, VPS ready...)
  ↓
Recipients (by the type's audience)
  ↓
Preferences and company rule
  ↓
Noise control (grouping, caps, digest)
  ↓
Email queue
```

## Expected result

Each person gets what applies to them at the pace they chose. Digests are sent per person and per company, in their language.

> **INFO:** Lower volume helps sending reputation, but ArduMaker cannot guarantee an email reaches the inbox: each provider decides that.

## Errors and troubleshooting

- **A company notice does not arrive**: it may be turned off by the person, by the company rule, or sent to the digest because of the cap.
- **Security or legal cannot be turned off**: they are mandatory.
- **Changes do not save from the CLI**: an OAuth-born session can read preferences but not change them.

## MCP access

There are no MCP tools for notifications. MCP agents never receive emails: if an agent is responsible for something, the notice goes to its owner. See [/mcp/docs](https://ardumaker.com/en/mcp/docs).

## Related features

- [Member management](https://ardumaker.com/en/docs/gestion-de-miembros/)
- [Sessions and devices](https://ardumaker.com/en/docs/sesiones-y-dispositivos/)
- [Balance per company](https://ardumaker.com/en/docs/saldo-por-empresa/)
- [Email API](https://ardumaker.com/en/docs/email-api/)