Signatures and daily limits

Two per-inbox settings live in the detail slide-over for each inbox in the card grid: a signature appended to outgoing emails, and a daily send limit that feeds rotation.

Inbox signatures

The slide-over's Signature section shows an Edit signature row — a filled green dot next to it means a signature is currently enabled. Clicking it opens a modal with an Off/On toggle, a plain-text editor, and a live preview.

Campaign body preview...

{{name}} · Sales, Acme Inc.

--
To stop receiving these emails, unsubscribe here: https://api.forgesend.cloud/unsubscribe?token=example

The preview is built from a fixed template: a placeholder campaign body, the signature (if enabled), then the same unsubscribe-footer example used elsewhere in the app — so what you see is the actual stack order, not just the raw text. Saving closes the modal and shows a "Signature saved." confirmation toast.

Signature validation

Rules are enforced in the UI and re-checked on the server, so a signature can't be saved in a state the backend would reject:

• Maximum 400 characters
• Plain text only — any HTML tag is rejected with "Signature must be plain text; HTML tags are not allowed."
• Only {{name}} and {{email}} are recognized as variables; any other {{...}} placeholder is rejected with "Signature contains unknown variables. Only {{name}} and {{email}} are allowed."
• Trying to save the toggle On with empty text is blocked, with "signatureTemplate is required when signatureEnabled is true." — an empty template with the toggle off saves fine, and the server itself forces signatureEnabled false if the template is blank.

Daily send limits

The slide-over's Sending section is a plain number input, 1 to 500, with its own Save button.

New inboxes start at a default limit of 50 sends/day. Raising the limit — or lowering it when it doesn't conflict with warmup — takes effect immediately for rotation: the next capacity check uses the new number, with no propagation delay. The daily counter itself resets automatically at UTC midnight, independent of when you change the limit.

Lowering a limit during warmup

If an inbox is running warmup and you try to lower its daily limit below what warmup itself needs that day, saving doesn't fail silently — it stops and asks you to confirm the tradeoff first.

The message tells you exactly how the new, smaller limit would be split — how much of it warmup would still take, and how much would actually be left over for real campaign sends. Confirming with Lower limit re-submits the same change with that tradeoff accepted; Cancel leaves the limit untouched. This check only fires on the way down, and only when warmup is actually running on that inbox — raising a limit, or changing it on an inbox with no active warmup, saves immediately with no extra step.

Related docs

Next: Inbox health and rotation

• Inboxes overview
• Connecting an inbox
• Campaigns overview — sender pool and compliance footer