Skip to main content
Open Settings → Notifications in your app’s editor to manage the emails it sends to users.
Invitation and sign-in settings appear for public apps with login enabled. If you see No emails yet, check Settings → Login. “Public” apps can still require people to sign in.
Notifications settings showing Email branding, Sent from, Invitation, Sign-in, and Custom emails.

Customize branding and sender

Under Branding & sender:
  • Email branding: Inherit the app’s branding or choose an available Brand Kit.
  • Sent from: Select Connect an email account to use your own sender. Supported options include Gmail, Outlook, and a custom email server.
Custom authentication email branding, sender, and templates require Business access. Follow any upgrade prompt shown for your plan.

Edit an invitation or sign-in email

  1. Select the Invitation or Sign-in card. Sign-in opens Sign-in email.
  2. Update the subject, heading, and message. Use the available variables to include details such as the app name.
  3. For an invitation, you can also edit the Button label. The sign-in code email has no Button label. The code itself is not editable; each email carries a fresh code.
  4. Review the preview, save your changes, and send a test email before inviting customers.
Invitation links expire after 7 days. Sign-in codes expire after 10 minutes. An app starts sending codes only when you next republish it. Existing sign-in links keep working. Invitation emails still use a link. Do not forward invitation links or sign-in codes to someone else.
The old sign-in link email no longer has its own card. It is only sent by app versions published before sign-in codes. If you previously customized the sign-in email for a link, the app keeps your branding and sender. The code email uses the default wording until you next edit the app with the agent, which then rewords the custom copy for a code. The sign-in email includes the code, when it expires, and a short security note.

Custom emails from workflows

Use Custom emails to find workflows that send messages, or select Send an email to describe a new email task to Zite. For example:
When a customer submits a service request, email them a confirmation with the request number and expected response time.
Tell Zite the trigger, recipient, and content. Test with your own email address, then check Workflow Runs if a message does not arrive. Zite apps cannot send push notifications to phones. See Can my app send push notifications?.
Last modified on October 30, 2026