Weekly Patch - September 27, 2026

#Permanently approve a trusted account

Sign-in security checks exist to keep bad actors out. Every so often they flag someone who's perfectly legitimate, and until now the only fix was a password reset. That unlocked the account right up until the next sign-in locked it again. Not a great loop.

Administrators with the Moderate Users community role can now permanently approve an account from the user's summary page. Once approved, that person won't be locked out or signed out because a sign-in looked suspicious. If they're already locked for suspicious activity, approving them clears the lock on the spot. No password reset needed.

1. Open the community user summary for the person you want to approve.
2. In the User account actions menu, click Permanently approve this account.
3. Read the confirmation message, then click Approve.
4. Check that the Sign-in risk detail now reads "Approved by [your name] on [today's date]." 🎉

Approval switches off exactly one thing. Every sign-in is still checked and recorded, so you keep full visibility into sign-in activity. Too many wrong passwords will still lock the account, and approving won't clear that kind of lock.

To help you tell the two apart, the user summary now names the cause of a lock. A suspicious-activity lock reads Account locked due to suspicious activity, and failed-password locks look the same as before. The sign-in message changed too. Someone locked for suspicious activity now gets a message asking them to contact support, instead of being told they made too many sign-in attempts.

Important note: Approval is permanent and can't be removed from the user summary. Treat it as a deliberate decision, not a toggle.

#Product Versions & Releases

#Publishing releases in big communities works again

What we fixed: In larger communities, the ones with lots of team members and a long history of content views, the Version/Release Preview page could fail with an error. Sometimes the page never loaded at all. When it did load, clicking Publish or Publish and Notify could still fail, so the release never went out. We tracked it down, and the Preview page now loads reliably and publishing finishes, no matter how big your community has grown.

See it in action:

1. Head to Product Versions in your project's admin area, then open an existing Version or create a new one and fill in the required fields.
2. Click Preview. The page should load without complaint, even in your busiest community.
3. Click Publish or Publish and Notify and watch your release go live. No more error pages standing between your participants and the new build. 🎉

Good to know: Nothing about the release itself caused this. It depended entirely on the size and history of the community, which is why smaller communities probably never saw it. If you'd been retrying publishes over and over, you can go ahead normally now.