
Rental-status unit keypads, perimeter gate and overstay logic, move-in and move-out codes, manager overrides and vendor routing across an unmanned site.
Self-storage facilities run largely unattended, so access has to express the rental agreement at the door: a tenant in good standing opens the perimeter gate and their own unit during access hours, an overdue account is handled by the written overstay policy rather than an informal code, and move-out automatically returns the unit to the pool. A self-storage access solution coordinates the gate, pedestrian core, aisle and unit so a credential cannot reach another unit, while managers hold a separate override role and vendors use dated service windows. Outdoor gates and roll-up doors demand weather-rated hardware and battery planning. The self-storage guide covers operations, the locker solution covers compartment banks, and the parking guide covers similar gated vehicle sites.
| Rental status | Gate and unit credentials follow account status, activating on move-in and withdrawn at move-out |
| Overstay logic | Delinquent access follows the written policy and notice schedule rather than shared gate codes |
| Unit isolation | A tenant credential opens only the rented unit, never neighbouring units or shared aisles beyond access |
| Unmanned entry | Tenants self-serve gate and unit entry during access hours, with a documented assistance path |
| Managers | Override and inspection roles stay separate and recorded rather than handed to tenants |
| Vendors | Maintenance and auction-window access uses dated, scope-bounded credentials |
| BOM shape | Perimeter gate, pedestrian controls, unit keypads by count, outdoor-rated spares |
Multi-unit operators choose rental-linked gates and unit keypads; a handful of outdoor containers may combine a gate keypad with managed padlocks.
| Dimension | Gate code plus tenant padlocks | Rental-linked electronic access |
|---|---|---|
| Move-in | Code given and padlock sold at desk | Gate and unit access active with the rental |
| Overstay | Hard to enforce without a visit | Access follows the written policy and notice steps |
| Move-out | Lock cut and code forgotten | Unit returns to pool automatically at move-out |
| Unit isolation | Shared gate reaches the whole yard | Credential limited to the rented unit and gate |
| After hours | Staff must attend the site | Self-serve entry with recorded assistance path |
| Typical fit | Very small container yards | Multi-unit unmanned and hybrid facilities |
The perimeter gate controls vehicles and hours; the unit keypad enforces rental status and isolation at each roll-up door.
| Opening | Typical door | Lock approach |
|---|---|---|
| Perimeter gate | Vehicle slide or swing gate | Rental-status codes with access-hour and overstay logic |
| Pedestrian core | Walk-in keypad entrance | Tenant entry separate from vehicles, vendors bounded |
| Unit door | Roll-up metal storage door | Unit keypad tied to the rental, isolated from other units |
| Office / kiosk | Manager office or rental kiosk | Manager and move-in workflows, never tenant-accessible controls |
| Service / vendor | Maintenance and delivery gate | Dated windows for repairs and inspection, tenant units blocked |
| Auction / vacate | Delinquent-unit handling doors | Scope-bounded access under the documented policy and notice |
This example illustrates a typical configuration, not a specific customer project. Unit count, gate type and climate mix drive the list.
| Component | Typical logic | Notes |
|---|---|---|
| Gate controls | Vehicle and pedestrian perimeter access | Rental-status and access-hour logic with weather rating |
| Unit keypads | One per rentable unit door | Activated and withdrawn with the rental automatically |
| Manager scope | Override and inspection credentials | Separate recorded role outside the tenant domain |
| Vendor windows | Maintenance and service-dated codes | Scope-bounded to the work, tenant units inaccessible |
| Outdoor spares | Gate and unit hardware rated for the climate | Held on site under the current MOQ policy with battery plan |
Gate and unit credentials are tied to the rental record: they activate at move-in, allow the gate and the rented unit during access hours while the account is in good standing, and withdraw at move-out so the unit returns to the pool. Overdue accounts follow the written overstay and notice policy — which may include warning notices and grace windows — rather than a manager informally sharing the gate code, and any final vacate or auction step is separately scoped and recorded. Defining this sequence in the operating policy before go-live keeps enforcement consistent and defensible. The pilot aisle deliberately includes a simulated overdue account and a move-out to verify the status changes trigger the doors exactly as the policy states.
No: a tenant credential is limited to the perimeter gate, the permitted access hours and the single rented unit, so it is rejected at every other unit door and at service areas. A tenant renting multiple units receives a credential scoped to exactly those units. Shared aisles need no separate permission because they carry no lock, but vendor and manager doors sit in entirely separate groups. This isolation replaces the traditional risk where a shared gate code admitted every tenant to the whole yard at any hour. Temporary crew access, such as a moving company helping on move-in day, uses a dated window arranged by the manager rather than the tenant sharing their code.
Tenants self-serve through the gate and unit during access hours, while a documented assistance path covers lockouts, low batteries and credentials that fail outside staffed hours, typically combining remote verification with a named on-call manager who holds the recorded override role. Gate controllers and unit locks hold their schedules locally so a connectivity loss does not bar a paying tenant or leave the gate uncontrolled, and battery servicing is planned on a route since units number in the hundreds. The assistance path and its hours are stated to tenants at move-in. The pilot runs a genuine after-hours assistance call to confirm a tenant can reach help without codes being shared verbally.
Perimeter gates use weather-rated operators and keypads sealed for rain and dust, unit locks fit the roll-up or swing door without defeating its latching, and exposed sites add cold or corrosion planning; battery service intervals reflect both the climate and the long walk around a facility. Gate power and fail-safe behaviour are coordinated with free egress so a vehicle or pedestrian is never trapped, and the gate safety edges and fire access remain independent of the credential system. Hardware selection starts from a site survey of each door type rather than applying one indoor lock across outdoor openings, and spare parts are held for the highest-use gate.
The BOM counts the vehicle and pedestrian gates, one keypad per rentable unit, manager and vendor controls, outdoor-rated spares and the battery service plan, with MOQ and lead time confirmed in writing per quotation. Operators usually pilot one aisle and the gate across move-in, an after-hours visit and an overstay case before facility-wide rollout. Send the unit count, gate type, access-hour policy and climate notes, and the quote maps each line to the gate-and-unit architecture rather than generic lock pricing.
Send the unit count, gate type and access-hour policy — receive a gate-and-unit BOM with written MOQ and lead-time terms.
Discuss your project (RFQ)Project configurationsLast updated: October 31, 2026 · Reviewed by the Smart Lock Factory editorial team