Notifications
Notifications are how your team and your partners find out that something happened: a lead arrived, a deal moved stage, someone was mentioned in a note. Journeybee ships with thirteen built-in notifications, and you can build your own rules on top.
Every rule answers four questions: what happened, does it qualify, who hears about it, and how they hear about it.
Where to find it: Go to Settings, then Notifications.
Who can use this: Admins and Partnerships team members.
The two lists
The page is split in two.
Built-in: the thirteen notifications Journeybee provides. You can turn them on or off and adjust who they reach, but you cannot delete them.
Your notifications: rules you have created yourself. These are fully editable and deletable.
Each row shows the notification's name, delivery channels and status.
Built-in notifications
All are switched on when your workspace is created, except New message from your team, which starts off — turn it on if you want partners emailed when your team writes to them:
New lead: a new lead is created. Email, both sides.
Lead accepted and Lead rejected: a lead is accepted or rejected. Email, both sides — the email includes the reason and the shared answers collected by your accept/reject forms, where that side can see them.
Lead assigned to you: someone is assigned to a lead. In-app and email.
Project assigned to you: someone is assigned to a project. In-app and email.
Task assigned to you: someone is assigned to a task. In-app and email.
Deal stage changed: a deal moves stage, notifying that deal's assignees on both sides. In-app and email.
New deal registered: a partner registers a new deal, notifying that deal's assignees on both sides. In-app and email.
Deal expired: a deal expires. Email to the partner.
You were mentioned: someone mentions you in a note, comment or message. In-app and email, both sides.
New message from your team: someone on your team sends a partner a message in Messages. Emails the partner contacts who have written in that conversation — or the partner's primary contact when nobody has yet. Off by default.
Certification awaiting approval and Certification awaiting approval (assigned users): a partner finishes a certification that requires approval, notifying your admins and the team members assigned to that partner. In-app and email.
Certification approved and Certification review rejected: a reviewer approves or rejects a completed certification, emailing the learner with the reviewer's note. Email only.
Partner invitation: the invitation email a new partner receives.
User invitation: the invitation email a new portal user receives.
On the partner side, these emails go to the contacts linked to the lead — a deal inherits its lead's contacts — and Lead accepted, Lead rejected and Deal expired also reach the partner who created it. When a built-in lead or deal notification finds nobody to email — a lead your team logged on the partner's behalf has no contacts yet — Lead accepted, Lead rejected, Deal stage changed and Deal expired email the partner's primary contact instead, so the partner still hears about it. New message from your team falls back the same way on a conversation no partner contact has written in yet. A partnership with no primary contact receives no partner email. Rules you build yourself are unaffected — they only ever go to the recipients you pick.
Workspaces set up earlier may still show a single combined Lead status update rule instead of the accepted and rejected pair — the split only applied where the rule had never been edited, so a customised rule stays as one.
If your company renames leads or deals under Settings → Company, the built-in lead and deal emails — their titles, text and buttons — use your names. A rule whose text you have changed keeps your wording instead; insert {{terms.lead}} or {{terms.deal}} into it from the Terminology group to make it follow your names.
With Co-selling on, a deal's supporting partners are emailed too — under the same built-in deal emails, and under any partner-facing rule you build on a deal event or a note on the deal. Each supporting partner is judged on its own tier, category and opt-outs, and emailed at its own contacts with the same primary-contact fallback. Partner variables name the partner the email is for, and the button links to the deal in that partner's portal. A note on an archived deal reaches no supporting partner, and a note is never emailed to a partner whose co-sell role does not let it read that note — including one your team addressed to another partner. Fields with Supporting partners can see switched off in Custom Fields are left out of supporting partners' emails. If deal value is hidden, they do not receive value-change emails; if expiration is hidden, they do not receive expiry or expiration-reminder emails. An update only to hidden standard fields sends them no update email. Your team, the primary partner and distributors are not affected by this restriction. A supporting partner contact who has already been emailed about the event, under any rule, is not emailed about it again.
What you can change on a built-in
Click a built-in notification to open its settings panel:
Enabled: turn the whole notification on or off for your company.
Notify: your team, partners, or both.
Channels: which channels are used. Partners always receive email; in-app reaches your team only.
Disabled for partnerships: search for specific partners and switch this notification off for them alone. Everyone else still receives it.
The two invitation notifications are transactional. Their audience and channels are fixed, because they carry a portal sign-in link and can only go to the partner by email. You can still disable them per partnership.
The per-partnership switch is the useful one in practice: a partner who has asked for less email can be quietened without changing anything for the rest of your network.
Create your own notification
Click New notification. The builder has two steps.
Step 1: Name and events
Give the rule a name, then tick the events that should fire it. Events are grouped by record type, and a rule can watch several at once. Available events:
Lead: created, updated (any field), deleted, status changed, assigned, unassigned.
Deal: created, updated, deleted, stage changed, value changed, expired.
Partner: created, updated, deleted, stage changed, tier changed, category changed, assigned, unassigned.
Collaboration card: created, updated, deleted, stage changed, assigned, unassigned.
Task: created, updated, deleted, status changed, assigned, unassigned.
Note: added, updated, deleted, mentioned.
Card comment: mentioned.
Message: sent, edited, mentioned. Message rules can be filtered by Sent by — whether the sender was your team, the partner, or another source such as a Slack-bridged reply — and can use
{{sender_name}}and{{message_excerpt}}alongside the partner variables.Resource access: granted, revoked.
Certification access: granted, revoked.
Certification: created, updated, deleted.
Certification enrolment: enrolment awaiting approval, enrolment approved, enrolment review rejected. These fire only on certifications that use Requires approval, and can use
{{certification_name}},{{learner_name}},{{review_feedback}}and{{reviewer_name}}. See Building Certifications.Payment: created, processing, completed.
Room: room goal completed, all room goals completed, room form submitted. The goal events fire when a partner ticks off goals in a Goals block in a portal room — one notification is sent per save even if several goals were ticked at once. Room form submitted fires when a partner submits a Form block. The variables include
{{room_name}},{{block_title}},{{goal_titles}},{{completed_count}},{{total_count}},{{form_title}}and{{submission_summary}}, alongside the partner variables.
Picking an event prefills a sensible title and body for you, which you can then edit.
To alert your team on every form submission without building a rule, use the Notify on submission setting on the Form block itself — see Custom Portal Rooms.
Step 2: Everything else
Step two is a set of collapsible sections.
Conditions
Conditions narrow when the rule fires. With none, it fires on every matching event.
Build filters against the record's fields, your partner taxonomy (type, tier, category, stage) and your custom fields. Operators cover equals, does not equal, greater than, less than, is one of, is not one of, contains, is empty and is not empty.
All conditions must be met. They combine with AND, not OR. If you need either of two situations to fire the rule, build two rules.
Setting a Partner type also filters the tiers, categories, stages and custom fields offered in the condition rows to that type, which makes the picker far easier to use.
Recipients
Two settings decide who hears about it.
Which side gets notified?
Your team
Partners
Your team + Partners
Recipients
Assigned / tagged users: the people assigned to the record, plus anyone newly @mentioned in it. Records that cannot be assigned themselves — a note, comment, message or payment — notify the assignees of the record they belong to instead.
The person who created the record: the record's creator — on a note, comment or message that is the author, and on a room form submission the partner who submitted it.
Partner Manager: the Partner Manager of the partner the record belongs to — the starred assigned user on the partner. This option is not offered when only Partners are notified. Nobody is notified when the partner has no Partner Manager.
Assigned distributor contacts: the distributor contacts assigned to the lead, or to a deal's lead. This option appears only when Partners is the side being notified, it sends by email only, and it works on lead and deal events. The email is written for the distributor: partner variables name the distributor, and only custom fields shared with partners are filled in. The rule's conditions still check the lead's own partner, not the distributor. If no distributor contact is assigned, nobody is emailed — there is no fallback to the distributor's primary contact.
These choices are honoured exactly. If nobody is assigned — or the only assignee is the person who made the change, who is never notified about their own actions — nobody on your team hears about it. There is no fallback to admins or the wider team.
When an Assigned distributor contacts rule emails a contact about an event, that contact receives only that email for the event, even if another of your rules would also reach them.
One rule you cannot work around: partners are notified by email only. In-app notifications and Slack delivery reach your own team. Selecting Partners as the audience greys out the other channels.
Delivery
Tick one or more channels.
In-app notification: the bell in Journeybee. Your team only.
Email: works for both sides.
Slack channel: posts into a Slack channel. Your team only.
Slack delivery
Slack delivery needs the Slack integration connected. Once it is, choose a channel from the list and use Send test to confirm it works before saving.
For a private channel, invite the Journeybee app to the channel in Slack first, then send the test. If a delivery fails later, the rule shows the error and you can re-select the channel or reconnect Slack and test again.
Message
Write the Title and Body the recipient sees. Both accept {{variable}} placeholders, and the builder gives you an Insert row of the variables available for the events you selected. Typical ones are {{first_name}}, {{lead_name}}, {{company_name}}, {{partner_name}}, {{stage_name}} and {{deal_value}}.
On lead and deal rules the Insert row also shows a Terminology group: {{terms.lead}}, {{terms.leads}}, {{terms.Lead}}, {{terms.Leads}} and {{terms.aLead}}, and the same set for deal. They always render the names your company uses — set under Settings → Company → Terminology — so a template written with them follows any rename automatically.
Email settings
An optional section that only affects the email version:
Header and Footer: extra text around the message. Both accept variables.
Button label and Button links to: the call to action. Pick the object type (lead, deal, partner, card or task) and Journeybee generates the correct link at send time, pointing your team at the app and partners at the portal.
Mention and message emails already link and quote for you: a mention opens where it happened, and a message email shows the message and adds a View conversation button, so they need nothing picked here.
Show branding: your company logo and brand colour on the email. On by default.
Do not try to hand-write the button URL. Because the same rule can notify both sides, the destination differs per recipient, and only the generated link gets that right.
Preview and test
Preview renders the email as the recipient will see it, with your branding and variables filled in from sample data.
Test dry-runs the rule: it evaluates your conditions and renders your templates against sample data and tells you whether the rule would have fired. Nothing is sent to anybody.
Use the test before you activate a rule with conditions on it. "Conditions did not match" at this point is far cheaper than silence for a fortnight.
Troubleshooting
A notification is not arriving
Check in this order: the rule is Active; the partner is not on its Disabled for partnerships list; the audience includes the side you expect; the channel is ticked — partners only ever receive email, so an audience that includes partners needs Email ticked; and the conditions actually match. Run test answers the last one directly. For an Assigned / tagged users rule, also check the record actually has assignees: nobody assigned means nobody notified. On the partner side, a built-in lead or deal email falls back to the partner's primary contact when there is nobody else to reach — a partnership with no primary contact gets nothing.
A distributor contact is not getting emails
Check that the rule uses Assigned distributor contacts with Partners as the side notified, and that the contact is assigned on the lead — a deal uses its lead's contacts. The lead must still be linked to that distributor: changing or removing a lead's distributor takes the former distributor's contacts off the lead. The distributor must be live and must not be on the rule's Disabled for partnerships list.
Partners are not getting in-app notifications
By design. Partners receive email only. In-app and Slack are for your own team.
The rule fires too often
An updated (any field) event fires on every edit to that record. Use a narrower event such as status changed or stage changed, or add conditions.
Slack delivery failed
The rule shows the last error. For a private channel, the Journeybee app has to be invited to it in Slack. Re-select the channel or reconnect Slack, then send a test.
One partner is getting too much email
Open the notification and add them under Disabled for partnerships. That switches it off for them only.
I need "either this or that" logic
Conditions on a rule all have to be met. Build two rules instead.
Good to know
Built-in notifications can be switched off but never deleted, so you can always turn one back on.
Partner notifications only reach live partnerships. An offline partner receives nothing.
A Lead needs review email still fires when the Salesforce, HubSpot, Attio or Pipedrive lead check holds a lead, and a Lead auto-rejected in-app notification fires when the check rejects one automatically. Both reach the lead's assigned users and partner managers, never your partners, and nothing is sent when nobody is assigned. They are always on and do not appear on this page — see Salesforce Integration, HubSpot Integration, Attio Integration and Pipedrive Integration, and Objects for the rules that decide it.
The email button link is generated per recipient, so the same rule sends your team into the app and partners into the portal.
Partner-facing emails only fill a Custom Field variable when the field is shared with partners and applies to the partner on the record. Other custom field variables are left blank.
A mention or message email links straight to where it happened: a note opens its lead, deal or partner, and a message opens the conversation itself. Partner links open their portal.
Set your notification rules before you invite real partners. A partner who submits a lead and hears nothing assumes it never arrived.
Submitting a deal together with a new lead in the partner portal sends one email — the new-deal one — rather than one for each record.
A bulk CRM import sends no notifications: imported partners, contacts, leads and deals simply appear. They can still trigger workflows and CRM sync as usual.
Updating a partner's per-partner settings (deal expiration, the partner-edit permissions, the visibility limit or auto-create users) sends no partner-updated notification.
A change that only updates a deal's CRM bookkeeping — the links to your CRM's records and the sync state stored on the deal — sends no deal-updated notification and fires no deal-updated workflow.
Related articles
Slack Integration: connecting Slack so channel delivery works.
Workflows: for acting on an event rather than announcing it.
Dynamic Content Variables: the variables available in partner-facing messages.