video1.0<iframe src="https://www.loom.com/embed/85246c80bd7042fb88c3ede4e80a676a" frameborder="0" width="1920" height="1440" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>14401920Loomhttps://www.loom.com14401920https://cdn.loom.com/sessions/thumbnails/85246c80bd7042fb88c3ede4e80a676a-a914e30df45e6e6d.gif90.926This Loom explains how to archive residents and users in the system, including the notification and access implications. It notes that archiving via the three dots will notify the resident and remove access, with confirmation once they are archived. It also covers a key edge case: if an imported resident is archived while still active in the partner platform, they may be reactivated and then sync overnight; in that case, they must be archived in the partner platform first. Finally, it mentions you can do this in bulk using multi-select and the archive option, and that manually added users can be manually archived, including API-imported users.