Skip to main content

Language Switcher (Custom HTML)

Currency: USD

The Relief Manager Arrives Tomorrow. Will Their Access End on Sunday?

Scroll Down To Discover
Three facility leaders walk a bright climate-controlled self-storage corridor while reviewing operating conditions.

Access should match the work, the place and the time. Governed editorial image; not evidence of the fictional example, an access-system configuration or a security result. Reused from the governed image library without changing the existing attachment metadata; the governing catalog does not assert a production method.

A relief manager arrives before opening to cover two shifts. The regular manager is out. The relief manager needs the office, the front gate, the climate-controlled building and the systems required to serve customers.

The fastest setup is tempting: copy the regular manager’s access, hand over a shared key ring and plan to clean it up later.

That shortcut answers the wrong question. The issue is not whether a credential works. It is whether this person has the right role, the right scope and the right access window for the work being assigned.

A working code, key, badge or account can still be wrong. It can open doors the employee does not need, reach another facility, expose administrative functions, begin too early or remain active after the assignment ends. A facility manager should be able to explain every grant in one sentence: who needs access, for which role, to what, from when until when, approved by whom and verified how.

Start with the job, not the closest existing user

Do not begin by asking, “Whose access should I copy?” Begin with the relief assignment.

Write down the work the person is expected to perform. A relief manager opening the office may need to disarm an approved area, enter the office, open the customer path, use the property-management functions assigned to the shift and reach one designated supply area. That does not automatically require access to every unit corridor, cash-control setting, camera administration page, employee record or portfolio report.

Role names are useful only when their meaning is current. “Manager,” “assistant,” “maintenance” and “regional” can hide different permissions at different properties. Use the role as a starting point, then name the actual duties for this assignment.

NIST Cybersecurity Framework 2.0 describes access permissions, entitlements and authorizations as items that should be defined in policy, managed, enforced and reviewed, with least privilege and separation of duties incorporated.[1] The framework is voluntary and does not define a self-storage relief-manager role. The practical lesson is simple: access should follow approved work, not convenience or familiarity.

Define scope in plain language

Scope has at least four parts at a storage facility:

  • Property scope: the exact facility, not a market, region or similarly named location.
  • Physical scope: the specific gate, building, office, cabinet or room.
  • System scope: the applications and functions needed for the shift.
  • Action scope: what the person may view, create, change, approve, export or administer.

“Office access” is incomplete if one credential also opens a maintenance room. “Property-management access” is incomplete if the account can also change rates, issue refunds or alter user permissions. “Camera access” is incomplete if the role can change retention or sharing settings rather than only view the approved feed.

Record exclusions as deliberately as inclusions. A clear grant might say: office and Building A staff entrance; customer-service and move-in functions; no cash adjustment, rate change, user administration, video export or access to the neighboring property.

NIST SP 800-53 Revision 5 defines least privilege as allowing only the authorized access necessary to accomplish assigned organizational tasks.[2] The publication is a federal control catalog, not a self-storage checklist or certification. It supports the operating principle; each company must translate that principle into its own approved doors, systems and actions.

Give temporary access an actual clock

“For the weekend” is not an access window.

Record the local start date and time, the time zone, the expiration date and time, and the event that should end the grant early. A relief assignment could end when the regular manager returns, the schedule changes, the property closes or the responsible owner withdraws the assignment.

The expiration should exist in the controlling system whenever the system supports it. A calendar reminder is useful for review, but it is not the same as a configured expiration. If a physical key cannot expire, the grant record needs a return deadline, custody owner and escalation rule.

Do not extend access by habit. If the relief assignment changes, review the role and scope again. An extension is a new authorization decision, not a clerical edit to make an alert disappear.

NIST SP 800-53’s account-management family includes controls for managing temporary and emergency accounts and for disabling or removing accounts under defined conditions.[2] That does not tell an operator which access platform feature is available. It reinforces the need for a defined end state instead of an open-ended temporary grant.

Issue one person one attributable credential

Do not give the relief manager another employee’s password, code, badge or mobile credential. Shared credentials obscure who entered, who changed a record and whether the original holder was present.

Use the organization’s approved identity-verification and credential-issuance procedure. Record the governed employee or workforce identifier, not unnecessary personal data. Bind the credential to the person who will use it. If the installed system cannot create a suitable temporary credential, route the limitation to the authorized system owner rather than improvising a permanent shared credential.

The Cybersecurity and Infrastructure Security Agency’s identity-and-access guidance recommends separating normal and privileged accounts, applying least privilege, auditing identities and removing unnecessary local identities.[3] The guide is aimed at administrators and enterprise identity environments. It does not prove that a particular self-storage platform supports a feature or prescribe a facility’s employment process.

Read back what actually works

Configured is not verified.

After the grant is created, test the intended path with the relief manager. Confirm that the credential works at the correct facility, during the correct schedule and only for the required doors or functions. Also test a small number of meaningful denials: another facility, an excluded room or an administrative function the role should not have.

Do not turn the test into exploration. The goal is to verify the approved grant, not to discover how far an overpowered credential can go. Record the test time, tester, intended successes, expected denials and any mismatch.

A mismatch means hold, not “close enough.” If the person can reach something outside the approved scope, restrict or remove the grant and escalate to the access owner. If required access fails, do not solve it by adding a broader role unless that broader role is independently approved.

Make shift handoff part of the access process

The next shift needs more than “Tessa is covering.” The handoff should show:

  • the relief role and facility;
  • the start and expiration time;
  • the approved physical and system scope;
  • the exclusions that matter;
  • the granting owner;
  • the verification result;
  • outstanding limitations; and
  • the person responsible for expiration, return or revocation.

If the assignment spans several days, review the grant at the start of each covered shift. Confirm the schedule still applies and no scope change is pending. At the end, verify the credential state in the controlling system and recover physical items. “Asked the employee to stop using it” is not revocation evidence.

Keep these states separate: assignment ended, logical credential disabled, physical key returned, shared device signed out and access record closed. One does not prove the others.

A fictional relief-shift example

The following facility, employee, identifiers, permissions, times and outcomes are entirely fictional.

Fictional Stonebridge Row Storage needs a relief manager for Saturday and Sunday. Fictional employee Tessa Morgan is assigned workforce ID FIC-WF-118. Her approved role is Relief Manager — Customer Service, not a copy of the regular manager’s full role.

The grant covers facility FIC-SRS-04, the office entrance, the staff gate schedule and the Building A staff door. In the fictional property system, it permits customer lookup, approved move-in steps and service-note entry. It excludes rate changes, refunds, user administration, video export, cash adjustments, the maintenance room and every other facility.

The window begins Saturday at 7:30 a.m. Eastern and expires Sunday at 6:30 p.m. Eastern. A named regional operator approves the grant. A separate system administrator creates Tessa’s individual credential. The manager and Tessa verify the intended doors and functions, then confirm that the maintenance room and another fictional facility remain denied.

At the Sunday close, the credential shows disabled, the temporary office key is returned and the shared office tablet is signed out. The regional operator reviews those three separate results before closing the access record.

This teaching example claims no real employee, facility, deployment, access-system capability, prevented incident, security improvement or compliance result.

Download the governed access records

Download the blank Relief-Shift Access Grant and Expiration CSV

Download the explicitly fictional Stonebridge Row example CSV

Use the Relief-Shift Access Grant and Expiration Card

The companion card gives a single-site manager a next-shift record without storing passwords, codes or secret values.

Gate Required record Hold condition
Role Assignment, duties, approving owner Role is copied from another person without review
Scope Facility, doors, systems, actions and exclusions Grant is described only as “manager access”
Window Local start, time zone, expiration and early-end event Temporary access has no controlled end
Credential Individual identity and approved issue method Password, code, badge or mobile key is shared
Readback Intended successes, expected denials, tester and time Scope mismatch or required path failure remains
Handoff Current state, limits, owner and next review Next shift cannot see who owns the grant
Closeout Disabled state, physical return, device sign-out and reviewer Assignment ended but one access path remains unknown

Access is not a favor attached to a person’s title. It is an operating decision attached to work. Define the role. Narrow the scope. Put an end time on the grant. Verify both access and denial. Then close every access path when the assignment is over.

Sources and limits

  1. National Institute of Standards and Technology, The NIST Cybersecurity Framework (CSF) 2.0, February 26, 2024; source refreshed November 20, 2026. PR.AA addresses identity, credential and access-management outcomes, including managed and reviewed permissions and risk-based physical access. CSF 2.0 is voluntary, cross-sector guidance and does not define a self-storage role or implementation.
  2. National Institute of Standards and Technology, NIST SP 800-53 Revision 5, Security and Privacy Controls for Information Systems and Organizations, including the current NIST Release 5.2.0 planning note; source refreshed November 20, 2026. AC-2 and AC-6 inform account management, temporary-account handling and least privilege. This federal control catalog is flexible and customizable; it is not a self-storage standard or a certification claim.
  3. Cybersecurity and Infrastructure Security Agency, Identity and Access Management: Recommended Best Practices for Administrators, official CISA guidance; source refreshed November 20, 2026. The guide addresses enterprise identity administration and does not establish a facility’s employment, physical-access or platform-specific procedure.

This article is operational education, not legal, employment, privacy, cybersecurity or physical-security advice. Company policy, qualified owners, employment requirements, installed-system capabilities and applicable law control.

Author

Jared Mastroianni is Chief Operating Officer of modSTORAGE and CEO and Founder of Facily.ai.

Assistance and claim disclosure

AI assistance supported source discovery, drafting, tool construction and editorial QA under human direction and review. Stonebridge Row Storage and every scenario detail are explicitly fictional. No customer, deployment, product entitlement, performance result, security outcome, revenue effect, certification, award or recognition claim is made.

Add Comment