# Manage usage, limits, and alerts Before inviting users, decide how much email your tenant may send and who will hear when usage rises. Your tenant's **Billing** page shows usage, effective limits, and alert recipients together. An email hard limit can stop sign-in codes and recovery messages, so make that decision as part of your launch. **Evaluating Udibo?** The [pricing page](https://www.udibo.com/pricing) lists the plans and rates. This guide explains the controls in the dashboard. Use the allowances and availability shown for your own tenant; the pricing calculator does not change your plan or set a spending limit. Use this guide to prepare for launch and respond to a limit or alert. The [Billing reference](https://www.udibo.com/docs/identity/billing) explains the dashboard fields and usage counters. ## Understand the controls | Control | What it does | What happens when it is reached | | ----------------------------- | ------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- | | Monthly email hard limit | Bounds the number of messages one sender may send in a UTC calendar month | Further sends through that sender stop until its effective limit increases or the UTC month resets | | Daily email hard limit | Bounds messages through that sender in a UTC day | Further sends stop until its effective limit increases or the UTC day resets, even if the monthly limit has room | | Email alert threshold | Warns nominated recipients about usage | Sending continues until a hard limit is reached | | Retained-user alert threshold | Warns about returning users against the plan's allowance | Users keep signing in; retained users are never capped | These are counts of messages or users, not an overall currency budget. There is no dashboard control that caps total spending across resources today. Technical rate limits and the shared sender's abuse allowance are separate from the limits you set here. ## Read the month's usage Open your tenant in the dashboard and choose **Billing**. Under **Usage this month**, review: - **Retained users:** a person who returns more than 24 hours after creating their account counts once in that UTC calendar month - **Emails sent through Udibo:** messages carried by Udibo's shared sender - **Emails sent through your own sender:** messages carried by your [Resend account](https://www.udibo.com/docs/identity/email), shown when your tenant uses one The two email senders have separate counts, limits, and alerts. Udibo does not bill messages carried by your own sender; your provider's charges still apply. Only messages accepted by the sending provider count as sends. Failed, suppressed, and refused messages do not. Check the page's measurement time when reviewing usage and estimated charges. An estimate under **Charges this month** is not an issued invoice. **Current plan** and **Invoices** show the tenant's own plan and billing history. If the page says paid plans are unavailable, an estimate does not open a subscription. ## Set email limits Changing limits requires **Manage billing**, which the Owner access level includes. Ask the tenant owner if you can read usage but cannot edit it; see [team access](https://www.udibo.com/docs/identity/team-access). 1. Under **Usage this month**, choose **Edit limits** beside the sender you want to configure. 2. Set the monthly **Hard limit** where that field is editable. Leaving it empty restores the plan's default. A plan with no published allowance may have no default limit, so review the effective value after saving. 3. Optionally set a **Daily hard limit**. Leaving this field empty sets no daily limit. The day resets at midnight UTC. 4. Set **Alert threshold** and **Daily alert threshold** before the stops you want time to respond to. A threshold above its corresponding limit is refused. 5. Enter **Alert recipients**, comma separated, with up to five addresses, or leave it empty to notify your administrators. 6. Choose **Save limit** and review the effective values on the page. For email sent through Udibo, a published plan allowance is the default monthly hard limit. On a free plan it cannot be raised above that allowance. On a billing plan, raising it can permit paid usage above the allowance; it cannot be set below the allowance. Your own sender's monthly limit may be any nonnegative count, and daily limits may be lower than a monthly allowance. When you leave alert thresholds empty, the monthly warning defaults to 80% of the limit or allowance. The daily warning defaults to 80% of a daily limit, or a quarter of the monthly limit when no daily limit is set. A daily warning can therefore be active even when there is no daily stop. ## Choose who hears alerts Review **Nominated recipients** after saving. A new address must open its one-time confirmation email and confirm before it receives alerts. A verified administrator address can be confirmed immediately. The page labels each address **Confirmed** or **Pending confirmation** and offers **Resend confirmation** when a new link can be sent. When a resource has no nominated recipients, or none has confirmed yet, alerts go to verified Owner and Admin addresses. Once at least one nominated address confirms, alerts for that resource go to its confirmed nominees. Keep the recipient lists current when people change responsibilities. Usage alerts come from Udibo. They do not consume your tenant's email allowance and are not stopped by its email hard limit. Delivery can still fail, so review the dashboard and [audit log](https://www.udibo.com/docs/identity/audit-log) when investigating a missing alert. ## Set a retained-user alert Choose **Edit alert** beside retained users when the plan has a published allowance. Set an **Alert threshold** and recipients, then choose **Save alert**. A missing allowance leaves this control unavailable. Retained users have no hard limit. Crossing an allowance does not prevent sign-in. Charges, where applicable, follow the tenant's actual plan; the public pricing page does not establish that plan. ## Respond to a limit or alert An email hard limit stops further messages through the affected sender, including password resets, verification, sign-in codes, and magic links. A password or social sign-in that does not need an email can still work, as can an authenticator challenge. A user who needs a stopped recovery message cannot complete that step. - Confirm which sender and period reached its limit. Raising a monthly limit alone does not remove a daily stop. - Check whether the volume is expected before changing it. Investigate an unexpected burst with the audit log and [account protection](https://www.udibo.com/docs/identity/account-protection). - If you change a permitted limit or the period resets, test the user flow again. Do not assume a previously refused message will be sent later. - For delivery problems below your limits, follow [email troubleshooting](https://www.udibo.com/docs/identity/troubleshooting#email-does-not-arrive) and check your sender's health. Limits are checked before sends. If the billing state or counter cannot be read at that moment, the service permits delivery rather than losing the message. The limits therefore do not provide an unconditional spending guarantee during a billing failure. ## Send alerts to your own systems The audit log records `usage.halfway`, `usage.alert_threshold`, and `usage.limit_reached`. Subscribe a [webhook](https://www.udibo.com/docs/identity/webhooks#subscriptions) to `usage.*` to feed your monitoring. Email events identify the sender and day or month they concern; the daily window has no halfway step. A `usage.limit_reached` event for retained users means the allowance was passed, not that sign-in stopped. **Before launch:** confirm the effective email limits, confirm an alert recipient, and test sign-in and recovery with real inboxes. Continue with the [production checklist](https://www.udibo.com/docs/identity/production). _Last verified 2026-10-02._