Notifications
What Joryio tells you - the people who use Joryio - and where: the bell in the header, and email. This page is about notifications to your team, not the campaigns and journeys you send to your own customers. You choose what reaches you in your notification settings.
The bell
The bell at the top of every page is your own inbox. The red badge is the number of items you have not read yet; it refreshes every 30 seconds.
- Click an item to open what it is about (the campaign, the alert's history, the Monitoring page). Opening it marks it read.
- Mark all as read clears the badge for everything in the list.
- Show older loads earlier items.
Read state is per person: when you read an item, it stays unread for everyone else who received it.
The bell shows the items for the workspace you are in, plus account-wide items (for example a low messaging wallet) in every workspace.
What appears in the bell
| Item | Who gets it |
|---|---|
| Approval needed for a campaign | Everyone who can approve campaigns in that workspace, except the person who submitted it |
| Approved / Changes requested | The person who submitted the campaign |
| Needs re-approval - a scheduled campaign outgrew the approval it holds and will not send until it is approved again | Everyone who can approve campaigns in that workspace |
| An alert triggered or resolved (Monitoring) | Everyone who can view settings in that workspace |
| An automatic event tracking incident (events stopped or dropped) and other system alerts, such as low coupon stock | Everyone who can view settings in that workspace |
| A security notice about your own account - password changed, two-step verification or a passkey added or removed, a sign-in from a new device, an API key or AI agent connection you created or removed (details) | You |
| A team or security change in your organization - a new admin, a member's access changed, a member removed, suspended or joined, API keys, single sign-on, the sign-in policy (details) | Owners and admins (not the person who made the change); for API keys, single sign-on and the sign-in policy, also your security contacts |
| Billing, operations and workflow notices - payment and wallet, sending domains, failed campaigns, journeys and data streams, approvals for journeys, finished exports and imports (details) | See the list |
| Joryio support replied to your ticket, resolved it, or is waiting for your reply - click to open the case | The person who opened the ticket, when it is linked to their account. Someone who only emailed support gets the email only |
The first time you open the bell after this change, alerts older than a day arrive already read, so you only see what is new.
Emails Joryio sends you
| Sent to | |
|---|---|
| Your Joryio accounts ("Email me my accounts" on the sign-in page) | The address that asked |
| Reset your password (link valid 15 minutes) | You |
| Your account was temporarily locked | You |
| You're invited to your organization (also Resend invite) | The invited person |
| Approval needed / Approved / Changes requested / Needs re-approval | The same people as in the bell, above |
| Alert triggered / Still firing / Resolved | The members on the alert rule, and its outside addresses once they have confirmed (details) |
| Event tracking incident | Owners and admins, and members who can change settings in that workspace |
| A reply to your support request - reply to the email (it goes to the support team, with the case number in the subject) or open the ticket in the app | The person who opened it |
| We received your email - when your email to [email protected] starts a new request: a short note with its case number (not sent for replies or automatic replies) | The address that wrote |
| Billing, operations and workflow notices (details) | See the list |
Every email has the same layout and ends with a line that says why you received it and a link to your account settings. Security and team notices (below) and the account emails above cannot be turned off. The others you can turn off per channel in your notification settings. An email sent to an outside address also has a one-click unsubscribe link. A button or link in an email opens the organization and workspace the notice is about: if you are in another workspace of the same organization, Joryio switches to it; if you are signed in to a different organization, Joryio offers to sign you in to the right one and then opens the link. If you do not have access to it, the page says so.
Where emails come from
All of these come from Joryio's own notification address. They never go through your workspace's email provider, so they do not use your sending reputation or quota, and they arrive whether or not you have set one up.
If the mail service does not accept a message the first time, Joryio tries again a few times over about half an hour. A password reset link is only retried within its 15 minutes.
Language
Emails are written in the language you use Joryio in - the language picker in the header. Joryio learns it the next time you sign in and use the app; until then, emails are in English. Hebrew and Arabic emails read right to left. Details you typed yourself, such as an alert or campaign name, stay as you wrote them.
Demo workspaces
In a demo workspace whose external connections are closed, alert emails are not sent; the alerts still show in the bell. Invitations, password resets and other account emails are sent as usual. Security and team notices are sent as usual too - they are about real people's accounts.
The same goes for operations notices - sending domains, branded link domains, WhatsApp, syncs, failed campaigns and journeys, data streams: in a closed demo they appear in the bell only. Your demo ends on is the exception and is always emailed - telling you is its purpose.
Your notification settings
Each person chooses what reaches them on Settings → Notifications (/settings/notifications). The page is a grid: one row per category - Security, Team, Billing, Operations, Workflow, Account and Weekly digest - and one column per channel - Email and In-app (the bell). A cell shows "-" where the category has nothing on that channel; the weekly digest, for example, is email only.
Your choices are your own: turning a channel off for yourself changes nothing for anyone else in the organization.
Defaults
Everything is on, so nothing changes until you change it. The one exception is the weekly digest, which is off until you turn it on.
Always on: security, team and account
The Security, Team and Account rows are locked on and cannot be changed. They tell you about your own account and about who can get into your organization - a password change, a sign-in from a new device, a new admin - and a notice that could be switched off is exactly the one an intruder would switch off first. See Security and team notices.
Critical notices always keep one channel
Some notices are too important to miss altogether. You can turn off one channel for them, but not both: if you turn off both Email and In-app for their category, they still reach you by email.
- Billing: Payment failed, Confirm the card payment, Invoice overdue, Sending pauses on a date, Sending is paused, Event collection is paused, Messages are not being sent: the wallet is empty.
- Operations: Email authentication is failing, On an email blocklist, Branded link domain stopped answering, Campaign did not send, Your demo ends on a date.
- Workflow: A privacy request from Shopify (it can carry a legal deadline).
Every other notice in these categories, and everything else in Workflow and Weekly digest, follows your choice exactly.
Rows you do not see
The page only shows the categories you can receive:
- Team - owners and admins only.
- Billing - owners and admins, and members who are a billing contact.
Security, Operations, Workflow, Account and Weekly digest are shown to everyone.
Notification contacts
Owners and admins can name who else receives some notices, under Notification contacts on the same page. There are three kinds:
| Contact | What they receive |
|---|---|
| Billing | Billing notices. These go to the billing contacts and the organization's owners. While no billing contact is set, they go to owners and admins. |
| Security | Organization security notices - API keys, single sign-on and the sign-in policy - in addition to owners and admins. |
| Operations | Operations notices, in addition to the people who already receive them. |
Each kind holds up to 20 entries. An entry is either a member, picked from your people, or an outside address you type in - a shared mailbox or a distribution list such as [email protected] works too. An address that belongs to a member of your organization is treated as that member.
Members receive contact notices by email and in the bell, following their own notification settings. Outside addresses receive email only, and only after they have confirmed.
Outside addresses must confirm
An address outside your organization - a notification contact or an alert rule recipient - receives nothing until the person who reads it confirms they want it. This keeps Joryio from sending mail to people who never asked for it.
- When you add the address, Joryio sends it an email titled "Confirm notifications from a Joryio workspace", with a Confirm button. The email is fixed Joryio text: your organization's name appears only in quotes inside a sentence, shortened to 60 characters, with every dot, @, slash and colon in it replaced by a space (so nothing in it can become a link), and the only links are Joryio's own. It also says that if they do not recognise it, they can ignore it and will receive nothing.
- Confirm opens a page in Joryio. Nothing happens on just opening the link - some mail scanners open links on their own - the reader has to click Confirm on that page. No thanks on the same page refuses, and the organization cannot ask that address again.
- Until then the address is shown as pending and receives nothing.
Confirmation emails are limited to one per address per organization per day, and 20 per organization per day (and no address gets more than three a day from all organizations together). If a confirmation was lost, send it again with Resend next to the address, on the alert rule or in notification contacts. If it was not sent (for example a limit was reached), the address shows Not sent now - try again later.
Every email Joryio sends to an outside address has a one-click Unsubscribe link. Unsubscribing - or clicking No thanks - removes the address from all of that organization's alert rules and notification contacts, and it cannot be added again.
The confirmation email also has a Never send me these requests again link (and a one-click unsubscribe in the mail client). It blocks the address for every Joryio workspace: no workspace can send it a confirmation or any notification again. Other workspaces are not told: nothing about the address changes in what they see, it just receives nothing. If someone blocked Joryio requests, inviting them as a member of your organization lifts the block (once they accept the invitation). Names and descriptions that your team typed (organization, workspace, alert rule) are cleaned the same way in every email to an outside address: dots (except inside numbers such as 1.5%), @, slashes and colons become spaces, and long text is shortened. Each recipient must be a single email address; lists such as [email protected], [email protected] are refused.
Alert rule recipients
The email recipients of an alert rule are members, picked from your people, plus outside addresses, which must confirm as described above. Members never need to confirm.
Rules created before this change kept their addresses: an address that belongs to a member of your organization became that member, and every other address became an outside address waiting to confirm. Joryio did not email those addresses when the change arrived, so they receive nothing yet. Such a rule shows a banner - "N outside addresses have not confirmed yet - they receive nothing until they do" - and Send confirmation sends them the confirmation email.
Weekly digest
An optional weekly email that sums up last week in a workspace. It is off by default; turn on Email in the Weekly digest row of your notification settings.
- It arrives on Monday at 09:00 in the workspace's time zone and covers the previous week, Monday to Sunday, in that zone.
- You get one email per workspace you can access, up to 10.
- It shows the campaigns sent that week (how many, and up to five names), messages delivered, unique opens and clicks, alerts fired and resolved, and approvals waiting for campaigns and journeys. Opens and clicks are counted as on the dashboard: bots are excluded, and a person who clicked an email counts as having opened it.
- A workspace with none of this activity that week sends no digest.
Security and team notices
Joryio tells you when something changes on your account, and tells your organization's owners and admins when something changes in the team or its security. These arrive by email and in the bell, and cannot be turned off.
About your own account
| Notice | When |
|---|---|
| Your password was changed / Your password was reset | You changed it in your account settings, or used a reset link |
| Two-step verification was turned on / off | On your account |
| A passkey was added / removed | On your account |
| New sign-in from a device we have not seen | See New sign-ins |
| API key created / rotated / revoked | You did it |
| AI agent connected / disconnected | You approved an AI agent (such as an MCP client) or disconnected one |
Each one says when it happened, and where it can, the device and browser, the approximate location and the IP address. Times are shown in the time zone of the sign-in's location when it is known, otherwise in UTC, and the zone is always named.
Joryio has no change-of-email-address flow today, so there is no email-change notice.
About your organization (owners and admins)
| Notice | When |
|---|---|
| New administrator | Someone was invited as an admin, or their role was raised to admin |
| Access changed | A member's role or access was changed |
| Member removed / Member suspended | A member was removed or suspended - their sessions and AI agent connections end |
| Member joined | An invited person accepted and set up their account. The person who invited them is told too, even if they are not an admin |
| API key created / rotated / revoked | Anyone in the organization did it, or it was done with an API key |
| Single sign-on changed | Single sign-on was set up, removed, made required or made optional |
| Sign-in security policy changed | For example two-step verification required, failed sign-ins before lockout, password rules, allowed IP addresses or session timeout. The notice lists each setting with its old and new value |
The person who made the change does not get the organization notice - they either did it themselves or got the personal version above. Several changes to the same member within a couple of minutes arrive as one email per person.
Notices about API keys, single sign-on and the sign-in policy also go to your organization's security contacts.
New sign-ins
A sign-in counts as new when its combination of browser, operating system and country (from the IP address) has not signed in to your account before. Joryio stores only a fingerprint of that combination - not the browser details or your IP address.
- A sign-in from a device you chose to remember ("Trust this device") never sends this notice.
- Your account's first sign-in after this feature arrived is recorded quietly, so nobody gets a flood of emails.
- A browser update is not a new device; signing in from another country is.
"This wasn't me"
Every notice about your own account has a This wasn't me button. If you did not do what the email describes:
- Press the button. It opens a page in Joryio - nothing happens until you confirm there, because some mail scanners open links on their own.
- Confirm with Sign me out everywhere. Joryio then:
- signs your account out on every device and browser, including this one;
- forgets your trusted devices, so the next sign-in asks for your second step again;
- for a new-sign-in notice, forgets that device too;
- disconnects your AI agents.
- Reset your password (the page links to it) - someone may know it - and tell your administrator.
The link works once and expires after 24 hours. If it has expired, reset your password, use Sign out everywhere in your account settings, and tell your administrator. Every use of the link, accepted or refused, is recorded in the sign-in audit log.
Billing, operations and workflow notices
These arrive by email and in the bell, except where a row says otherwise. Each problem is told once per incident: a domain that stays broken for a week is one email, not seven. Where it makes sense, a second email says the problem is over. You can turn off email or the bell for each category in your notification settings; the critical ones still reach you by email if you turn off both.
Billing
Sent to the organization's billing contacts and owners. While no billing contact is set, they go to owners and admins.
Billing notices start once your organization is on paid billing - a paid subscription with an account at Joryio's payment provider. Until then they are not sent, by email or in the bell. The exception is Credit added: it is the receipt for credit you bought, so it is sent whenever you buy credit by card - but never to a demo organization.
| Notice | When |
|---|---|
| Payment failed | A payment did not go through. Sending continues during the grace period; the email says when it ends. For a card, the email has an Update your card button and states the amount, period and status of the invoice |
| Sending pauses on a date | Three days before the grace period ends, if the invoice is still unpaid |
| Sending is paused | The grace period ended unpaid. Sign-in, your data and exports stay available |
| Event collection is paused | The invoice stayed unpaid long enough that events from your apps and website are refused |
| Payment received | The invoice was paid after any of the above, and everything works normally again. It carries the payment: the amount, the period, the payment method and the tax invoice (or where it will be) |
| Your Joryio plan is ready - add your card (or your billing details and card) | Joryio staff set up a plan paid by card (or switched yours to card) and no card is saved yet: the plan, its start date and the first charge. The button opens Settings → Usage & Billing, asks for your billing details first if there are none, then opens the card form. Never for a demo organization, a plan paid by bank transfer or invoiced separately, or when a card is saved. See paying by card |
| Reminder: add a card (or your billing details and a card) | Once, 7 days after a card-paid plan started, if there is still no card - with the same button. Not sent once a card is saved, or for a cancelled plan |
| Upcoming card charge on a date | Only when upcoming-charge reminders are switched on (they are off by default): a few days before a card subscription's invoice is charged automatically, with the amount. Never for invoices paid by bank transfer or invoiced separately. See paying by card |
| Confirm the card payment | Your bank asks you to confirm a card payment (3-D Secure). The Confirm payment button opens Settings → Usage & Billing in Joryio, where you confirm it |
| Payment received: an amount | An invoice paid by card or bank transfer was paid. The amount, the period, the payment method and the status - the only email about a successful charge, as there is no separate "new invoice" email for card subscriptions. Not sent when the same payment ended a past-due state - the Payment received row above says that, with the same payment details |
| Credit added for your organization - an amount | You bought messaging credit by card. The credit added, any prepay bonus, the VAT (customers in Israel), the total paid, your new balance and the tax invoice-receipt (or where it will be). Credits added by Joryio (a goodwill credit or a correction) send no email |
| Your Joryio plan ends on a date | Joryio staff cancelled your plan at the end of the current billing cycle. It stays active until its last day, and that cycle is invoiced as usual. See cancelling your plan |
| Your Joryio plan has been cancelled | The plan was cancelled - immediately, or at the end of the cycle. Its last day, and that anything still due is billed on a final invoice. Sent even though the plan has ended |
| Payment request, Credit note or Tax invoice-receipt and its number | A legal document that no other email carried: the payment request for an invoice paid by bank transfer or invoiced separately, a credit note (a cancelled invoice, a plan-change credit), or the invoice-receipt for a part payment. With the amount and, for a payment request, the due date. See legal invoices and receipts |
| Payment reminder: due on a date | An invoice paid by bank transfer, or invoiced separately, is due in 7 days (by default), with the amount and due date. See paying by bank transfer |
| Invoice overdue: an amount | The invoice was not fully paid by its due date. The subscription is past due; the email says the amount still due and when sending pauses |
| Messaging credits are running low | The messaging wallet holds less than about a week of your recent SMS, WhatsApp and Viber spending, and never less than $10. Once until it is topped up |
| Messages are not being sent: the wallet is empty | A message was skipped because the wallet could not pay for it. Skipped messages are not sent later. A second email says when credits were added |
| Free AI credit used up | This month's free AI credit is spent. AI agents keep running and are paid from the wallet |
There is no email or bell item when your engaged profiles pass your plan. Your usage so far and the estimated price are on the Your plan card in Usage & Billing.
Billing emails never link our payment provider's invoice pages, PDFs or receipts. Your legal documents (payment requests, tax invoice-receipts) are issued by our invoicing system: when one has been issued for the invoice, the email links it (a reminder links the payment request). Without one, a Payment received email says Your tax invoice will be available in Settings - Usage & Billing - Invoices., and an email sent before payment has no tax-invoice line, since none exists yet. See legal invoices and receipts. Your billing email address (in billing details) also receives Payment received, Credit added and the legal-document emails, with the document attached as a PDF - a very large document, or one that cannot be read at that moment, is linked instead. Like Credit added, a legal-document email is sent whenever a document is issued, but never to a demo organization.
Operations
Sent to owners, admins and members who can change settings in the workspace, unless a row says otherwise. They also go to your organization's operations contacts.
| Notice | When |
|---|---|
| Email authentication is failing | The daily check found that SPF, DKIM, DMARC or the bounce MX record of a sending domain stopped passing. A lookup that did not answer does not count |
| On an email blocklist | The daily check found a sending domain on a blocklist |
| Branded link domain stopped answering | A branded link domain that was working stopped answering in an hourly check (two failed checks, half a minute apart). The check only tells you - it does not switch your links to another domain; pressing Verify on the domain does. Sent to owners and admins |
| WhatsApp is disconnected | Joryio could not renew a WhatsApp account's access token |
| Warehouse sync is failing | A warehouse sync failed three runs in a row, or has not succeeded for three of its intervals. Email only - the bell already shows it |
| Segments are not rebuilding | The nightly rebuild of a segment has failed for over 48 hours. Email only - the bell already shows it |
| Campaign did not send | A campaign stopped with the status Failed. Also sent to the person who created it |
| Journey cannot start people | People could not be started into a journey. Also sent to the person who created it. Resolved after an hour with no failed start |
| Data stream is failing | Events for a data stream, such as a webhook, were dropped after every retry |
| Your demo ends on a date | Seven days and one day before a demo account ends. Sent to owners and admins |
Each problem above has a matching resolved email when it clears - except a failed campaign (use Retry on the campaign) and the demo notice.
Workflow
| Notice | Sent to |
|---|---|
| Approval needed for a journey | Everyone who can approve journeys in the workspace, except the person who submitted it |
| Journey approved / Changes requested | The person who submitted the journey |
| Your export is ready (or failed) | The person who started the segment export |
| Your import has finished (or failed) | The person who started the import |
| Privacy request completed (erasure or data export) | The member who filed the request. The person the request is about is never emailed by Joryio about it |
| Shopify asked for a customer's data / Shopify asked to erase a customer's data / Shopify store disconnected | Owners, admins and members who can manage settings in the workspace connected to the store. See Privacy requests from Shopify |