Delegate yard ops without giving away the business

Growth breaks the owner-as-everything model fast. A second location, a part-time manager, or a family member running the gate — suddenly you need delegation without losing control of money, brand, or customer data.

The goal is not maximum access. It is scoped access: the right person can do the right job, and nothing else.

What site managers actually need day to day

Front-line operators typically need to:

• Update unit status after move-ins, move-outs, and cleaning
• Answer customer questions with accurate inventory
• Process reservations and waitlists according to your rules
• Adjust local settings that affect the yard — hours, hold length, abuse protection toggles you trust them to tune

They usually do not need:

• Billing to StoreAll, Stripe Connect, or platform subscription
• Ability to delete the organization or transfer ownership
• Raw export of your entire customer database to personal email
• Pricing strategy changes you have not approved

Split “run the yard” from “run the company.”

Sub-owners vs staff accounts

Sub-owners fit a trusted partner — sibling co-owner, regional manager, spouse who shares liability. They get broad Manage access under your org slug, still bounded by your tier and policies.

Scoped staff (future-facing pattern many operators want) should see only their location or module: inventory, reservations, customer messages — not your financial connectors.

When evaluating any platform, ask: *Can I add help without sharing my login password?* Shared owner credentials are a security incident waiting for a bad Tuesday.

Settings worth keeping at owner level

Keep these on the owner account until you have a documented handoff:

Document who can change what in a one-page internal policy — not because staff are untrustworthy, because clarity prevents accidents.

Onboarding a new site manager in one afternoon

1. Create their login — never share yours.
2. Walk the four statuses — available, reserved, occupied, unavailable — with real units.
3. Run a mock reservation from the public site through to Manage together.
4. Show waitlist workflow — add, notify, convert, remove.
5. Set escalation — who they text when gate codes fail, disputes arise, or inventory disagrees with the yard.

Day two, shadow them while they run the stand-up from Vacancy data your team will actually trust.

Multi-location: one brand, many yards

Adding a second facility multiplies coordination cost. Owners win when:

• Each location has a named responsible manager
• Inventory is location-scoped in the dashboard — no accidental cross-site status edits
• Public sites or embeds can highlight per-location availability without duplicate accounts

See Managing inventory across multiple locations for the operational playbook.

Signs delegation is working

• You stop being CC’d on every lock change
• Status updates happen same day without your reminder text
• Customer complaints about “website was wrong” trend down
• You spend owner time on acquisitions and rates, not data entry

Signs to pull access back

• Reservations linger unconfirmed past your SLA
• Promos appear on the website nobody approved
• Inventory audits keep finding the same mismatches on one shift
• Staff bypass the system with personal spreadsheets “because it is faster”

Fix process before blaming people — usually it is training or a UX friction point.

How StoreAll supports the model today

• Owner account owns billing, tier, Stripe, and org settings
• Sub-owner role supports trusted co-managers under /owners/{slug}/manage
• Customer-facing help stays scoped to your facility — renters never see platform admin paths
• Tier gates still apply — delegates cannot bypass plan limits you have not purchased

We are building toward finer staff scopes; even now, separate logins beat shared passwords.

Related reading

• Managing inventory across multiple locations
• Choosing the right StoreAll tier
• Vacancy data your team will actually trust
• Self-storage website best practices