<mods:mods version="3.3" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-3.xsd" xmlns:mods="http://www.loc.gov/mods/v3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><mods:titleInfo><mods:title>How We Control Who has Access to What</mods:title></mods:titleInfo><mods:name type="personal"><mods:namePart type="given">Beck</mods:namePart><mods:namePart type="family">Locey</mods:namePart><mods:role><mods:roleTerm type="text">author</mods:roleTerm></mods:role></mods:name><mods:abstract>We use Aleph, Primo, Rosetta (both as a dark archive and a CMS), and a custom EAD tool. Aleph, Rosetta, and our EAD tool all contain restricted content. Where it gets tricky is that some patrons and staff can access restricted content on a limited basis. Most staff can always access this content and most patrons can never access this content. How we differentiate between delivery and delivery and enforce policy is the topic of this session.</mods:abstract><mods:classification authority="lcc">Primo</mods:classification><mods:originInfo><mods:dateIssued encoding="iso8601">2014-04-30</mods:dateIssued></mods:originInfo><mods:genre>Conference or Workshop Item</mods:genre></mods:mods>