Skip to main content
The platform sends email automatically at major loan lifecycle events. Notifications are scoped to the person responsible for the file. If a loan is assigned to a specific staff member, only that person is notified. If the loan has no owner yet, the event fans out to everyone who holds the stage capability for that stage (loans.adjudicate, securities.review, or loans.disburse).

​
How routing works

Assigned loan

Only the assigned staff member receives the notification. Once you claim a file or are assigned one, you are the single point of contact for every stage event on that loan.

Unassigned loan

The event fans out to everyone holding the stage capability: every Adjudicator, the whole Securities team, or the whole Disbursement team.

Claiming a loan

Claiming a loan for yourself does not trigger an email. Claiming is a self-service action. Only an explicit assignment by a Credit Manager or Branch Manager sends an “assigned to you” notification.

​
Notification event table

​
Member notifications

Emails to borrowers are off by default. They are controlled at the deployment level by the ILOAN_MEMBER_EMAILS_ENABLED environment setting, not by a screen the Administrator manages. Until that setting equals true, member recipients are filtered out before any email is enqueued. When it is switched on, members receive emails for two events only:
  • Loan declined. The declined-decision email tells them the application was unsuccessful and includes the rationale.
  • Disbursement executed. A confirmation that funds have been released.
Members never receive internal workflow notifications such as Information requested or Ready for Disbursement. Those are staff-facing events.
Your credit union’s name and branding appear in every email the platform sends, to staff and members alike. The from-name on the email comes from your credit union’s configured sender name, and your primary brand color accents the loan link button. Branding is snapshotted at the moment the email is queued, not re-read at delivery, so the email always reflects the settings in force when the event fired.

​
Assignment notifications

When someone uses the Assignment panel to route a loan to a specific person, that person receives an “a loan needs your attention” email immediately, as long as the loan is actionable. This is separate from the event-based notifications in the table above. Directing any loan to a specific person uses the loans.assign capability, which Credit Managers, Branch Managers, and Administrators hold. That is not the only path: a Credit Officer can route their own draft to an adjudicator with loans.submit, and a stage worker can reassign a loan within their own stage by holding that stage’s owning capability, for example an Adjudicator with loans.adjudicate handing a file to another Adjudicator. One exception: assigning a loan that is still in DRAFT does not send the email. A draft pre-assignment is treated as routing intent only. The adjudicator gets the notice later, when the loan is submitted and routes to Adjudication. Assignment notifications fire for:
  • Direct assignment or reassignment to a specific person, by anyone permitted to assign that loan
  • Reassignment from one person to another
They do not fire when you claim a loan yourself. Self-claiming is logged in the audit trail but does not generate an email.

​
Scoped versus broadcast

Once a loan has an assignee, stage-team events go only to that person instead of the whole capability pool. The comparison below shows the difference between a fully unassigned pipeline and one where loans are actively assigned. Assigning loans promptly, either through the Assignment panel or by claiming, keeps your team’s inboxes manageable and makes it clear who is accountable for each file.

​
Loan filed routing

The fan-out for Loan filed is not driven by whether the loan is assigned. It is governed by the global ILOAN_SCOPED_NOTIFICATIONS setting:
  • Default (scoped notifications on). Only the Credit Officer is notified. Senior staff track filed volume from their dashboards rather than from inbox blasts.
  • Scoped notifications off. The legacy wider fan-out is restored: the Credit Officer, all Credit Manager (reports.view) holders, and the Branch Managers whose branch matches the loan’s branch (via loans.read.branch). Branch Managers at other branches are never included.
If you are not getting notifications you expect, check two things. First, confirm with your Administrator that your role is configured with the right capabilities. Second, check whether the loan is assigned to someone else. If it is, that person is the only one receiving stage notifications for that file.