# Track usage and set email limits The **Billing** page, in the **Tenant** group of your tenant's dashboard, shows what the tenant has used this month and what that costs on its plan. It is also where you put a hard limit on email and choose who is warned as usage approaches it. Viewing the page needs the **View billing** permission, which Owner, Admin and Support all carry. In the dashboard, changing a limit, an alert or the plan needs **Manage billing**, which only Owner carries; without it, the page has no edit buttons. Your plan and billing state never decide whether your users can sign in. An email hard limit you set is the exception for email-based sign-in: once it is reached, sign-in codes and links stop along with every other email. ## Read this month's usage The band at the top shows **Charges so far**, your **Plan**, **Retained users**, **Emails through Udibo** (or **Emails, own sender** once you have one), and **Machine tokens**. Under **Usage this month**, a table has one row per meter with the columns **Resource**, **Used**, **Included** and **Action**. **Used** shows the count with the hard limit or **No limit** under it. **Included** shows what your plan includes, or **Not set** when a plan does not include that amount. Free includes 500 retained users and 1,000 emails; Standard includes 5,000 and 10,000. For your own sender and machine tokens it shows a dash, read aloud as "Does not apply": Udibo includes and bills none of either. Under the resource's name, a paid plan shows its rate, and once a hard limit is set the row also shows the alert threshold and who is alerted: | Row | What it counts | | ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Retained users | A person who returns more than 24 hours after creating their account counts once in that UTC calendar month; see [pricing](https://www.udibo.com/docs/identity/pricing#what-counts-as-a-retained-user) | | Emails sent through Udibo | Email delivered from Udibo's shared sender | | Emails sent through your own sender | Email delivered through [your own sender](https://www.udibo.com/docs/identity/email#connect-your-own-sender); shown once you have one or have used one this month | | Machine tokens issued | Tokens your machine applications obtained with client credentials; there is no per-token charge | Under **Totals**, below the table, **Active users this month** counts the people who signed in this month, **Total users** counts every account, and **All emails sent this month** adds both email rows. The user counts include people only, not the service accounts behind machine applications. Email counts are current when the page loads. The other figures are currently collected once a day, and the page shows when they were last measured. Anyone who can view billing also sees this month's usage on the tenant's **Overview** page, each figure linking back to **Billing**. ## Set an email hard limit An Owner chooses **Edit limits** on the **Emails sent through Udibo** row: - **Hard limit** is the most email sent in a UTC calendar month. Leave it empty for your plan's default, which is the plan's included email allowance. A Free tenant cannot raise it above that; a Standard tenant can. - **Daily hard limit** stops email until you raise the effective limit or the UTC day resets, so a loop or an attack cannot spend the month in an hour. Leave it empty for none. - **Daily alert threshold** defaults to 80% of the daily limit, or a quarter of the monthly limit when there is no daily limit. - **Alert threshold** defaults to 80% of the hard limit. - **Alert recipients** takes up to five addresses, comma separated. Leave it empty to alert your administrators; see [choose who hears alerts](https://www.udibo.com/docs/identity/billing#choose-who-hears-alerts). Choose **Save limit**. An alert threshold above its own limit is refused. The **Emails sent through your own sender** row has its own **Edit limits** with the same fields. It is a separate meter: Udibo bills nothing for mail your provider carries, so this limit only guards your provider account against runaway sending. ## What happens at the limit Limits are checked before every send. Once the month's or the day's count reaches a hard limit, every email on that meter is refused, including sign-in codes, magic links, password resets, verification, and [waitlist](https://www.udibo.com/docs/identity/waitlist) and organization invitations. Password, social and authenticator sign-in do not use email and keep working. A monthly limit lifts when the UTC month turns or when you raise it; a daily limit lifts when the UTC day turns or when you raise it. If both limits are exhausted, both must have room before sending resumes. If your limits cannot be read at the moment of a send, the message is sent rather than held. Mail through Udibo's shared sender also has a daily ceiling of its own, separate from these limits; see [delivery by Udibo](https://www.udibo.com/docs/identity/email#delivery-by-udibo). ## Usage alerts Each email meter warns you in up to three steps each month: at half of the monthly limit, at the alert threshold, and when the limit is reached. The day has two steps, its alert threshold and its limit. Alerts are checked when a message is sent, so a step is announced by the first send that finds usage at or past it. Each step is announced at most once per meter per period; raise a limit and reach it again, and it is announced again. An alert threshold works without a hard limit. Set one on its own to be warned without ever stopping email. Alerts come from Udibo, not from your sender. They do not count toward your usage and are not stopped by your limits. Every step is also recorded as a `usage.*` event that a [webhook](https://www.udibo.com/docs/identity/webhooks#subscriptions) can deliver to your own systems. Retained users are never capped. Their row has an **Edit alert** button for an Owner on a plan that includes retained users, and you are warned at half of what your plan includes, at the alert threshold, and when usage passes what is included. ## Choose who hears alerts By default, alerts go to up to five of the tenant's Owner and Admin seat holders, owners first. To send them elsewhere, name up to five addresses in a row's **Alert recipients**. A nominated address hears nothing until it confirms. Saving the list sends each new address an email from Udibo, "Confirm usage alerts from _your tenant_ on Udibo". Its link lasts an hour and opens a page where the recipient chooses **Receive usage alerts**. The verified email of anyone holding an Owner, Admin or Support seat on the tenant is confirmed at once, without an email. Until at least one address on a list has confirmed, that list's alerts keep going to your administrators. An address confirms once for the tenant, whichever rows name it. Taking an address off every row forgets it, confirmed or not, and naming it again starts over. **Nominated recipients** lists every named address as **Confirmed** or **Pending confirmation**, with the time an outstanding link expires. When a link expired or could not be sent, an Owner can choose **Resend confirmation**. A resend is refused while a link is still outstanding, for an address that has already confirmed, and for an address that bounced or reported Udibo's mail; nominate a different address instead. One tenant can cause 15 confirmation emails an hour. Past that, a new address is listed as pending and is sent nothing, and a resend is refused until the hour has passed. ## Plan, charges and invoices On a paid plan, three sections follow: - **Charges this month** shows the plan base, any usage over what is included, and the total so far. - **Current plan** shows the plan, its price, and when the period ends. An Owner sees **Manage billing**, which continues on the payment provider's hosted pages. After a plan is canceled there, this section says the date it ends, after which the tenant is on the free plan. - **Invoices** lists what Udibo has billed the tenant, marked **Paid**, **Awaiting payment**, **Draft**, **Written off** or **Void**, with a link to each invoice where one exists. On Free, one block, **Free plan — nothing is billed**, takes their place. It describes the plan, estimates what the month would cost on Standard when a paid plan is offered, and gives an Owner **Upgrade**, which continues on the payment provider's hosted pages. A tenant that was billed before moving to Free still sees those invoices there, under **Past invoices**. If one of them is still unpaid, the heading reads **Free plan — an earlier invoice is unpaid** instead, and a notice under it names the invoice with a **Pay invoice** link where the payment provider offers one. Standard is open to a tenant's Owner when the page shows **Upgrade**. If the page says paid plans are unavailable, an estimate does not open a subscription. ### Billing contact for an organization's tenant When an organization owns the tenant, **Upgrade** first asks for the **Organization billing contact**: the address invoices and receipts go to. The first time, the field is empty; once the organization has a contact on file, it starts filled in with that address, and you can change it. Use an address the organization controls, such as a shared billing inbox, rather than a person's own. The contact belongs to the organization, so every tenant it owns bills the same address, and every organization admin counts as an Owner of those tenants: any of them can change it, from any of the organization's tenants. Once a contact is on file, the **Billing contact** section shows it on both the free and paid plans. An Owner can enter a new one and choose **Save billing contact**; the payment provider's record changes first, then Udibo's, and the address it replaced gets an email saying invoices no longer go there. If the payment provider cannot be reached, nothing is changed and the page says so; try again in a moment. The payment provider's billing portal does not change the billing email; only this section does. If the billing contact was the address of someone whose account was erased, Udibo removes it here, asks the payment provider to remove it too, and emails the organization's owners and admins. Invoices the provider finalised before the erasure keep the address they were sent to. The **Billing contact** section then says a contact is needed. Invoices are still created and charged; set a new contact there, or at the next upgrade, so they reach your organization. A tenant a person owns bills that person's own address and has no separate billing contact. ## Management API reference These operations are dashboard-only today; see [choose the right API](https://www.udibo.com/docs/identity/apis#the-management-api). Paths are under `https://www.udibo.com/api/identity/{tenantId}`: | Method | Path | Scope | Permission | Dashboard equivalent | | ------ | --------------- | ------------------------ | ---------------------------------------------------- | ------------------------------------ | | `GET` | `/usage-limits` | `identity:tenants:read` | **View tenant settings** (`identity.tenant.read`) | The limits, sends and recipient list | | `PUT` | `/usage-limits` | `identity:tenants:write` | **Manage tenant settings** (`identity.tenant.write`); raising or removing any hard limit also needs **Manage billing** (`identity.billing.manage`) | **Edit limits** and **Edit alert** | `GET` returns the limits as stored, the limit actually in force on each email meter, this month's and today's sends, and every nominated address with its confirmation state. `PUT` replaces every limit at once, so read first and send the whole set back: ```json { "emails": { "cap": 50000, "alertAt": 40000, "dailyCap": 5000, "recipients": ["ops@example.com"] }, "ownSenderEmails": { "dailyCap": 10000 } } ``` `emails` and `ownSenderEmails` take `cap`, `alertAt`, `dailyCap`, `dailyAlertAt` and `recipients`; `users` takes `alertAt` and `recipients`. A key you leave out is cleared to its default, `{}` clears everything, and an unknown key is refused with a 400. Raising or removing any hard limit needs **Manage billing** (`identity.billing.manage`), which the built-in Owner role carries (a custom role can too) and no machine credential can. That covers the monthly `cap` and the `dailyCap` on `emails`, `ownSenderEmails` and `checks`: a value above the one in force (above the plan's allowance when none is stored), and removing a daily limit, including by leaving its slot out of the body. A body that raises one limit while lowering another needs it too. Without it the call answers 403 and stores nothing. Lowering a limit, setting a daily limit where there was none, and changing an alert threshold or recipients need only **Manage tenant settings**. Resending a confirmation, the plan and invoices have no API operation. The full reference is in the [API reference](https://www.udibo.com/docs/api). ## Limits today - Email stops at the included allowance until the month turns or, on Standard, someone with Manage billing (an Owner by default) raises the hard limit. Retained users are never capped; their alerts follow the plan's allowance. - A monthly alert threshold set without a hard limit is saved and alerts as described, but its row does not show it until usage passes it; open **Edit limits** to see it. - Each row takes at most five recipients, and confirmation links last an hour. - There is no single budget that stops every meter at once; each limit covers one meter. **Maximum monthly bill** under **Usage this month** adds them up for you: the base plus each billed meter at its limit, leaving retained users out because they are billed as they return. See [Usage, limits, and alerts](https://www.udibo.com/docs/identity/usage-limits#know-the-most-you-can-be-billed). - New accounts have their own row and **Edit new accounts limits** control, an optional limit that refuses sign-up while existing people can still sign in; see [Limit new accounts](https://www.udibo.com/docs/identity/usage-limits#limit-new-accounts). - Hosted permission checks have their own row, limits and **Edit checks limits** control; see [Limit hosted permission checks](https://www.udibo.com/docs/identity/usage-limits#limit-hosted-permission-checks). Next: [send email from your domain](https://www.udibo.com/docs/identity/email), [subscribe to usage events](https://www.udibo.com/docs/identity/webhooks#subscriptions), or [give your team access](https://www.udibo.com/docs/identity/team-access). _Last verified 2026-11-14._