Administrators can now manage all Portal email settings from a dedicated Email Configuration area, separate from Brand Configuration. Email templates are presented in a scalable, grid-based layout, and the email domain, sender, and per-brand template content are all managed in one place.
Administrators can now configure each brand within a client tenant with its own dedicated authentication method. Brands can be set up independently with SSO with Pre-registration, username/password, or a combination of both on the same login screen.
The Custom CSS class reference has been updated to reflect the complete and authoritative set of supported classes. All 67 classes across 16 feature areas are now documented, with corrected friendly names for the Common, Documents, and related sections.
The Portal can now automatically send reminder emails to portal users who have not completed tasks in an open outreach stage. Reminders are configured directly on the Create Outreach Snapshot task in Journey Builder: enable the Enable Email Reminders toggle, then enter a comma-separated list of hour intervals in the Reminder Schedule field — for example, 24,168,720 sends reminders after 1 day, 7 days, and 30 days. Up to 10 intervals can be defined per task. A Reminder Email Template can also be selected per task. Reminders are sent only while the outreach stage remains open and incomplete, stop immediately when the stage is completed or cancelled, and reset if the stage is reopened. Only portal users linked to the entity who hold the role assigned to the outreach stage receive reminders.
A new Send Portal Email system task type is now available in Journey Builder. When executed, the task sends a selected portal email template to all portal users linked to the entity who hold at least one of the configured roles. The task can be placed in any internal or external stage, is not visible to portal users in the Portal UI, and supports multi-brand email resolution via the journey's brandUrl field. If a user holds multiple selected roles, only one email is sent per task execution.
Clients who manage their own email infrastructure can now receive a portal:reminderdue webhook event each time a portal reminder becomes due, rather than relying on Fenergo-managed email delivery. The event payload includes the event timestamp, recipient email addresses, reminder type, entity and journey context, the configured reminder template identifier, the scheduled send time, and correlation metadata. When an active webhook endpoint is configured for a tenant, Fenergo-managed reminder email delivery is suppressed to prevent duplicate communications. Webhook endpoints are registered via a service request with the Fenergo customer support team.
The brandUrl field used in multibranding journey configuration now supports resolution by Portal Name in addition to Portal URL. When the Enable MultiBranding toggle is on, the system first attempts an exact, case-sensitive match against the Portal URL column (existing behaviour). If no match is found, it falls back to a case-insensitive match against the Portal Name column. This allows journey configuration to be promoted between environments — dev, UAT, pre-prod, and production — without requiring brandUrl values to be manually updated, since Portal Names are stable across environments while Portal URLs are not. Existing configurations using Portal URLs are fully unaffected.
The supported custom CSS class library has been significantly expanded and now covers 67 classes across 16 feature areas. New areas include Footer, Login Screen, Entity Hub Datagroup accordions, GPI sub-elements (Journey Info, Journey Name, Process Container, Process Name, Task Item Container, Task Button, Task Name), Task Details, Product Task, E-Signature, Tooltip, Markdown, Checkbox List, Radio List, Form, and Button. Existing classes are unchanged. All classes continue to follow the .custom-css_ prefix convention and are subject to the same validation rules (blocked dimension properties, supported pseudo-classes only).
Journey notifications (in-app and email) now include the client's Legal Entity Name, so recipients can identify the client a task or journey relates to without navigating into Fenergo.
This applies to all six Journey notification types:
This feature is off by default. To enable, please raise a service request with Fenergo.
Portal users can now upload supporting documents per related party directly within the Standard Related Parties task in Portal. Controlled by a toggle on the task in Journey Builder, off by default.