<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/c7d9b200f9894af39cb7e73c4e7c2f87&quot; frameborder=&quot;0&quot; width=&quot;1784&quot; height=&quot;1338&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>1338</height><width>1784</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>1338</thumbnail_height><thumbnail_width>1784</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/c7d9b200f9894af39cb7e73c4e7c2f87-6af9bd1b95ea1009.gif</thumbnail_url><duration>371.78</duration><title>Multi-Factor Authentication Setup</title><description>This Loom explains the move to multi-factor authentication (MFA) for all CrisisWorks users starting 31 July 2026. It notes that MFA will be checked at every sign-in for username and password logins, while councils using SSO should have the MFA step handled during the council sign-in process so CrisisWorks will not ask for an additional code. MFA uses a password plus either an SMS code to a verified mobile number or a one-time code from an authenticator app, and CrisisWorks recommends setting up both as backup. The Loom also says users with privileged access should still configure CrisisWorks MFA, and that users without configured MFA or required access will not be able to sign in after the deadline.</description></oembed>