Secrets Management for a Property Manager's Tenant Systems

Site-level staff turnover is normal in property management, and the easiest habit to fall into is reusing one login across every new hire at a property rather than creating individual accounts. Years later, that login has been known by people who no longer work there, and nobody can say with confidence who still remembers it.

The systems behind that shared login usually include a resident portal with payment information and a database of tenant personal details, both of which carry real consequences if exposed. The property management software itself may be reasonably secure; the risk is almost always in how loosely access to it has been controlled at the site level.

If your team maintains even a light integration layer, a script pulling maintenance requests into a dashboard, or a connection between your property management software and a rent payment processor, Doppler gives you a simple place to store those few credentials without building infrastructure you don't need.

Vault's dynamic secrets and self-hosted operational model solve problems that come with running your own infrastructure at scale, and most property management companies simply aren't running that kind of infrastructure. Unless you're building substantial custom software around your portfolio, the setup and maintenance burden of Vault outweighs anything it would add over a simpler tool.

Change any credential a departing site manager had access to on their last day, not at the next scheduled review. Keep a short list, by property, of who currently has access to what, and check it every time staff turn over at a site. This single habit closes the gap that causes the most real risk in property management technology.

When a site manager leaves, work through these steps:

• Change every credential the departing manager had access to on their last day, not at the next scheduled review.
• Keep a short list by property of who currently has access to what, and check it each time staff turn over.
• Move to individual logins per staff member where the software supports it, instead of introducing another shared one.
• Separate credentials by system rather than keeping them all in one shared note or spreadsheet tab.
• Find out who holds the building access system credentials and whether the installing vendor's default account is still active.

A common habit at the property level is keeping every password a site needs, the building's wifi, the alarm system, a vendor portal login, in one shared note or spreadsheet tab that any staff member can open. It's convenient, and it's exactly why a single departing employee can walk away with access to far more systems than their role actually required.

Separate credentials by sensitivity, not just by convenience: the wifi password isn't the same risk as a login that can view tenant payment history, and storing them identically treats them as though they were. Even a simple step, like a distinct, access-controlled note for anything touching tenant financial or personal data, meaningfully reduces what a single leak exposes.

Pick one property and, without looking at any existing documentation, list every system a current site manager can access: the property management software, the maintenance request app, the payment processor's dashboard, the building's alarm panel. Then compare that list against what the current staffing actually requires, and you'll usually find at least one system a departed employee's credentials could still reach.

Doing this exercise once, property by property, surfaces gaps a calendar-based review misses, because it starts from what access actually exists rather than from what you assume was already cleaned up. Repeat it whenever a site changes management, not on a fixed annual schedule, since staffing changes are what actually drive the risk.

Beyond the tenant portal and accounting software, a property manager usually has a smart lock system, a building access panel, or a video system with its own admin login, often set up years ago by whichever vendor installed the hardware and rarely touched since.

Find out who currently holds that credential and whether it's still the installing vendor's default account. If a maintenance vendor's technician still has standing access to a building's lock system from a job that ended a while back, that's a bigger exposure than most of the software credentials this decision is usually about.

Fold these physical-system logins into the same rotation and offboarding habit you apply to the tenant portal and property management software. They're easy to forget precisely because they're touched so rarely, which is exactly why they're worth checking first.

When you take over management of a new property, make a physical-system credential audit part of the transition checklist, right alongside setting up the tenant portal and the accounting software login.