Skip to content
Udibo

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 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 explains the dashboard fields and usage counters.

Understand the controls

ControlWhat it doesWhat happens when it is reached
Monthly email hard limitBounds the number of messages one sender may send in a UTC calendar monthFurther sends through that sender stop until its effective limit increases or the UTC month resets
Daily email hard limitBounds messages through that sender in a UTC dayFurther sends stop until its effective limit increases or the UTC day resets, even if the monthly limit has room
Email alert thresholdWarns nominated recipients about usageSending continues until a hard limit is reached
Retained-user alert thresholdWarns about returning users against the plan's allowanceUsers keep signing in; retained users are never capped
New-account limit (optional)Bounds accounts created by self-service sign-up in a UTC month or dayNew sign-ups are refused until the UTC month or day resets; everyone with an account keeps signing in

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 daily ceiling 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, shown when your tenant uses one

  • Hosted permission checks: checks answered by Udibo for your tenant, with today's count, the monthly and daily limits, the alert threshold and its recipients

Each meter with a monthly hard limit shows it on its own row, including Free's fixed limits: Monthly limit 1,000, fixed by your plan.

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. Neither the charges under Charges this month on a paid plan nor the Standard estimate on Free is an issued invoice. Current plan and Invoices, or on Free the one plan block, 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 on this page requires Manage billing, which the Owner access level includes. Through the Management API, only raising or removing a limit does (see Who may change a limit); lowering one needs Manage tenant settings. Ask the tenant owner if you can read usage but cannot edit it; see 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 subscribe again, a monthly hard limit on email sent by Udibo or on hosted permission checks that is above the new plan's included amount goes back to that amount. Daily limits, alert thresholds and recipients are kept. Usage past the included amount bills again only after someone with Manage billing raises the limit.

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.

Who may change a limit

One rule applies to every hard limit, on every meter (email through Udibo, email through your own sender, hosted permission checks, new accounts) and in both windows (month and day):

  • Raising or removing a limit needs Manage billing, which the Owner access level carries and no machine credential can. Raising means a value above the one in force, or above the plan's default when you have set none. Removing a daily limit or a new-account limit counts, including by leaving it out of an API request.

  • Lowering a limit, setting a daily limit or a new-account limit where you had none, and changing an alert threshold or its recipients need Manage tenant settings.

A month's hosted permission checks are billed up to the highest monthly limit you had in effect that month, or your plan's allowance if that is higher; checks answered past it are not billed unless you raise the limit later that month, because the highest limit decides. The invoice line names how many checks past your limit were not billed. Lowering the limit late in a month does not reduce what the higher limit already allowed. Daily limits pace usage but do not change the bill.

An API request that raises one limit while lowering another needs Manage billing as a whole. Without it the request answers 403 and nothing is stored. The Billing page lets only a holder of Manage billing save any change.

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

Limit new accounts

Because retained users are never capped, an open sign-up page that attracts mass registration can grow your retained-user count, and any charge for it, without bound. A new-account limit is the control for that. It is optional and off by default, available on every plan, and not billed itself.

An account counts when it is created, before its email address is verified, so automated sign-ups count too, and deleting them does not reopen sign-up. Turn on CAPTCHA and set a daily limit so a burst can spend only one day's share.

  • Monthly limit (cap): accounts created by self-service sign-up in a UTC calendar month.

  • Daily limit (dailyCap): the same in a UTC day, for pacing a burst.

  • What counts and what is refused: sign-up on your hosted page with a password or a passkey, and a first sign-in through a social or OIDC provider that creates an account. Accounts you delete still count for the rest of their month or day, so deleting and re-creating accounts does not get past the limit. On a closed or waitlisted tenant, a person redeeming a waitlist invitation you sent is counted but never refused; on an open tenant an invitation does not change sign-up, so the limit applies to them as to anyone. Accounts your administrators create in the dashboard, through the Management API, or by importing users are neither counted nor refused.

  • What is never refused: sign-in by anyone who already has an account, by any method, including a two-step challenge, refreshing tokens, signing in through a provider for the first time when the provider's verified email matches their account, and connecting a provider to their account.

  • Who may change it: the rule in Who may change a limit. Setting a limit where there was none is a lowering.

On the Billing page, choose Edit new accounts limits on the New accounts row of Usage this month, set the monthly limit, the daily limit, the alert thresholds and the recipients, and choose Save limit. The row shows this month's and today's count against the limits, or No limit while none is set. Only a holder of Manage billing can save from the page.

You can also set it through the newAccounts slot of the Management API usage limits (replaceTenantUsageLimits in the API reference). The same response reports the effective limits under newAccounts, with used for this UTC month and usedToday.

Past either limit, the hosted sign-up page tells the visitor that the service isn't accepting new accounts right now and that an existing account can still sign in. It names neither the limit nor the count, and it answers the same whatever address was typed. The API answers 403 with problem reason new_account_limit, and the audit log records auth.sign_up.rejected with the same reason. The count is exact: concurrent sign-ups never pass the limit.

New-account alerts. The limit has an alert ladder going to the new-account recipients you set (otherwise your administrators):

  • Monthly: at half of the limit, at your alert threshold (80% of the limit by default), and when the limit is reached.

  • Daily: at your daily alert threshold (80% of the daily limit by default) and when the daily limit is reached, only when you set a daily limit or a daily threshold.

Each step is sent once per month or day, and recorded as a usage.* event targeting new_accounts:month or new_accounts:day. To reopen sign-up before the period resets, someone with Manage billing (an Owner by default) raises or removes the limit; deleting accounts does not reopen it.

Limit hosted permission checks

Hosted permission checks (POST /api/check and POST /api/check/batch on your tenant's own host) have their own monthly hard limit and an optional daily hard limit, counted per UTC calendar month and UTC day across your whole tenant.

  • Monthly limit: defaults to the checks your plan includes. On a plan that bills checks past the allowance, it may be raised but never set below the allowance. On a plan that bills no checks, including Free with its 25,000 checks, the allowance is the limit and cannot be raised.

  • Daily limit: none by default. It may be any number, for pacing a loop or a burst that would spend the month in hours.

  • Who may change them: the rule in Who may change a limit.

On the Billing page, choose Edit checks limits on the Hosted permission checks row. On Free the monthly limit is shown as fixed by your plan; the daily limit, alert threshold and recipients can still be set. Only a holder of Manage billing sees the control, and the page says who can change limits. You can also set them through the checks slot of the Management API usage limits (replaceTenantUsageLimits in the API reference). The same response reports the effective limit, this month's and today's checks, and enforced. The Charges this month list on a paid plan has a hosted checks line: used, included, and what has accrued at your pinned rate, or No charge this month for a month before checks bill.

At the limit. A hosted check past either limit answers 429 with problem reason usage_limit_reached, a resetAt timestamp, and Retry-After in seconds to the start of the next UTC month or day. Only that reset, or someone with Manage billing (an Owner by default) raising the limit, lets checks resume. A refusal is not an answer: deny or degrade, and retry after resetAt. Sign-in, token issuance, and refresh are never refused for this limit, and a refused check is not counted. The limit is enforced in memory and may be passed by the checks answered in about 20 seconds on another of Udibo's servers; if the limit cannot be read, checks are answered rather than refused.

Checks alerts. The limit has an alert ladder like the email limit's, going to the checks recipients you set (otherwise your administrators):

  • Monthly: at half of the limit, at your alert threshold (80% of the limit by default), and when the limit is reached.

  • Daily: at your daily alert threshold and when the daily limit is reached, only when you set a daily limit or a daily threshold. A daily warning derived from the monthly limit is not sent for checks.

Each step is sent once per month or day, and recorded as a usage.* event targeting checks:month or checks:day. An alert is sent within about 10 seconds of the count crossing a line, from Udibo's servers rather than the check request, and a failed alert never fails a check. Checks answered by Udibo's own tenant are not counted and raise nothing.

Each user's share

So that one account cannot use your tenant's whole month, each end user's share comes into force once your tenant has used half of its monthly limit. From then until the UTC month resets, each user may use at most a tenth of the limit more, counted from that point; what anyone used before it does not count. Until half the limit is used, nobody is held to a share. On Free that is 2,500 checks per user after the first 12,500; on Standard at the default limit, 25,000 after the first 125,000. Raising the monthly limit raises both. A tenant with fewer than two live accounts (deleted and disabled accounts do not count) has no share: its one user may use the whole limit. Udibo sets the share; it is not a tenant setting.

Past their share, that user's checks answer 429 with problem reason user_share_reached, a resetAt timestamp, and Retry-After to the start of the next UTC month; other users are unaffected, and a refused check is not counted. The usage limits response reports the rule (userShare, userShareFrom), each user's cap (userCap), and whether the share is in force this month (userShareInForce). To a caller who may read your users (View users), it also lists the end users with the most checks since the share came into force under topUsers (user id and count), so you can see who is using the allowance. The Billing page explains the share in one sentence and, to a caller who may read your users, lists these end users by id, each linking to its user page, once there are any.

Know the most you can be billed

Under Usage this month, Maximum monthly bill states the most your tenant can be billed for a month under its current limits: the plan base plus, for email through Udibo and for hosted checks, the amount past the allowance at the rate your subscription pinned, if that meter were used right up to its monthly limit. Each meter is rounded once to the nearest cent, as the invoice rounds it. Free shows $0.00, because it is never invoiced. A complimentary plan shows no figure.

Hosted checks add nothing for a month before checks bill, or when your plan has no checks rate, whatever their limit. Retained users are the one meter with no limit of its own: a person who returns keeps signing in, so retained users are billed as they return, unless you limit new accounts, and the total does not include them. A new-account limit bounds self-service sign-ups; it never stops someone who already has an account. The page says so beside the rate. For example, a Standard tenant with its limits at the allowances sees $5.00 plus retained users above 5,000; with its limits raised to 50,000 emails and 5,000,000 checks, at $10 per 1,000,000 past 250,000, it sees $92.50 plus retained users.

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.

  • 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 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 to usage.* to feed your monitoring. Email events identify the sender and day or month they concern (checks:month and checks:day for hosted permission checks, new_accounts:month and new_accounts:day for new accounts); 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.

Last verified 2026-11-16.

View Markdown