Clearer Messaging for Residents Who Already Have an Invitation
Community release notes, 11 August 2026, Web Portal Version 8.11.2026. Published on frontsteps.com/release-notes.
Web Portal Version 8.11.2026
What’s New?
Clearer Messaging for Residents Who Already Have an Invitation
Residents who try to self-register when their management company has already invited them now see that an invitation is waiting, and that invitation is automatically resent.Feature Overview:
Community previously treated two different situations as the same thing. A resident who had been invited by their management company but had not yet accepted, and a resident who had submitted their own access request, both received the message “You have already requested access, please check your email for confirmation.”
That message was wrong for invited residents — they had not requested anything — and left them with no way to move forward. The two states are now handled separately:
- Invited, not yet accepted. The resident is told an invitation has already been sent and that they need to accept it, and the invitation email is automatically resent so they have a current link.
- Self-requested access. The resident continues to see the existing already-requested confirmation message.
Applies to resident self-registration on the web.
Benefits:
- Residents are not misled: Invited residents are no longer told they requested access themselves.
- No support ticket required: The invitation is resent automatically instead of the resident needing to ask someone to send it again.
- Registration can be completed: The resident is pointed at the action that actually unblocks them.
What’s Improved
Email Metrics Now Match Email History
Campaign metrics report the number of emails actually sent, matching the campaign’s Email History.
Previous Behavior: Campaign metrics could disagree with a campaign’s own Email History about how many emails were sent, and the Overview tab and the Emails tab could disagree with each other. Managers reviewing Resident Engagement campaign performance could not always trust the sent count.
Resolution: Emails Sent is now counted the same way everywhere a campaign reports it, from the record created when each email is sent rather than from delivery notifications that can arrive late, arrive twice, or not arrive at all. The Overview tab, the Emails tab, and Email History now agree. Open, click, and bounce rates are unchanged.
Screen Reader Access to Resident Engagement Dialogs
The Select Communities, Audience Selection, and Recurrence dialogs are now available to screen readers.
Previous Behavior: The three Resident Engagement campaign dialogs were hidden from assistive technology even while open and visible on screen. A screen reader user could tab into the dialog but nothing about it — that it had opened, or what its controls were — was ever announced.
Resolution: The dialogs are now identified as modal dialogs and exposed to assistive technology while open, so a screen reader announces the dialog and its controls (search, community checkboxes, Cancel, Apply) as they’re reached. There is no change to how the dialogs behave for anyone else.
Fewer Error Pages Across Accounting and Community Records
A single bad record or a temporary accounting-system outage no longer replaces an entire page with a generic error.
Previous Behavior: Several situations across Architectural Requests, Financials, Work Orders, and accounting document downloads and previews could replace an entire page with a generic error instead of showing the rest of a manager’s or owner’s information.
Resolution: Each of these now fails in place instead of taking the page down: an unreadable date shows as an empty value in that one field, a document that can’t be displayed is listed by name with a note, and a failed download or preview returns the user to the page with a message instead of an error page. This coverage now extends across accounting-related actions in violations, work orders, common-area work orders, architectural requests, invoices, financials, and folders.