Skip to main content

Bulk Operations: What's Available Beyond the Resident Data Manager

A guide to the bulk operations available in ParkingPass — bulk invitations, bulk lease editing, bulk exports, and the residents-import queue — plus the operations that are not bulk and why.

Most property managers know the Resident Data Manager for bulk-importing a rent-roll. It's the largest and most-used bulk operation in ParkingPass — but it isn't the only one. This article walks through the other bulk-friendly tools available to PMs, where they live, and when to reach for them instead of doing things one at a time.

It also documents which operations are not bulk-friendly, so you don't waste time looking for buttons that aren't there.


The Big Picture

Bulk operations in ParkingPass cluster around resident lifecycle events — onboarding, updating, communicating, and exporting. Things tied to specific vehicles or individual enforcement actions are generally one-at-a-time.

The bulk-capable tools live in two places:

  • Residents sidebar — Import Accounts, Invite Residents, Export User Data, Pending Imported Residents.

  • Property-level features that occasionally surface bulk options — most recently, Lease Management Bulk Editing.


Resident Data Manager (Import Accounts)

The single largest bulk operation. Used for bulk-importing residents — name, contact info, unit, lease dates — typically from a rent-roll export.

When to use it

  • Initial property launch — importing an entire existing resident base before going live.

  • Major resident turnover events — apartment-style rolling move-ins where dozens of new residents arrive at once.

  • Aligning the platform with an updated rent-roll — replacing or updating the active resident set.

Where to find it

Residents → Import Accounts in the sidebar.

Related queue

After an import, residents land in the Pending Imported Residents queue (Residents → Pending Imported Residents) until they're activated. This is a useful place to confirm what was imported and to clean up any rows that had issues.

See Importing and Managing Resident Rent-Roll for the full RDM walkthrough.


Bulk Invitations (Invite Residents)

Sends invitation emails to multiple residents at once, so they can complete their own registration.

When to use it

  • After importing a rent-roll, when you want residents to set their own passwords and complete their profiles rather than configuring everything yourself.

  • Re-inviting a set of residents who never completed their initial registration.

  • Onboarding a new building or section of a property.

Where to find it

Residents → Invite Residents in the sidebar. There's also an Invite Residents quick-action button on the dashboard for client-side PM accounts.

Common follow-up

Track who has and hasn't accepted their invitation through the Resident Occupancy Rate widget on the dashboard. A low rate after a bulk invitation suggests the invitations didn't land, or residents didn't act on them.


Bulk Lease Editing

Recently added: bulk lease management, including editing leases and converting them to month-to-month, across many residents at once. (Announced via the dashboard's What's New feed.)

When to use it

  • End-of-period lease renewals where a large set of residents are being renewed at once.

  • Converting a group of expired leases to month-to-month rather than re-issuing fixed-term leases individually.

  • Correcting a property-wide lease-date error.

Where to find it

Look for Lease Management or related bulk-edit options in the Property or Residents submenu. Check the What's New announcements feed on your dashboard for the launch announcement and any release-note details.


Bulk Data Export (Export User Data)

Exports the resident/user data in bulk for use outside the platform.

When to use it

  • Sharing a current resident roster with property leadership, auditors, or HOA boards.

  • Reconciling the ParkingPass roster with a property's source-of-truth rent-roll.

  • Preparing for a property transition (new management company, ownership change).

  • Capturing data before a known retention window closes (helpful for old email or SMS history — see Activity History and Logs).

Where to find it

Residents → Export User Data in the sidebar.


Things That Are Not Bulk Operations

A few operations PMs sometimes look for as bulk that aren't:

Vehicle edits

The Vehicles sidebar offers queue-style review of Vehicle Change Requests and New Vehicle Requests, but each vehicle is approved or edited individually. There's no "select multiple, apply same change" interface for vehicles.

If you find yourself wanting to bulk-edit vehicles, the underlying issue is usually that the property's vehicle data is out of sync with its resident data. That's typically better solved by re-importing the resident set than by trying to bulk-update vehicles.

Do-Not-Tow entries

DNT entries are managed individually. Each entry includes its own vehicle details and expiration date, both of which the PM sets per row. See Permit Types Explained for the broader DNT lifecycle.

Guest passes

Guest passes are issued one at a time by residents (not by PMs). There's no PM-side bulk-issuance flow because the host-resident model assumes each pass is tied to a specific resident.

Citations, warnings, and tows

Enforcement actions are individual events tied to a specific vehicle and timestamp. There's no bulk-issue capability, and there shouldn't be — the patrol vendor records them as they occur in the field.

Patrol Holds

Holds are placed on a per-property basis for a specific period. If you need to apply a hold across multiple properties, that's a per-property action even if the dates and reason are the same.


When to Use Bulk vs. One-at-a-Time

Some general patterns:

  • If you'll do the same action more than about ten times, look for the bulk version first. Manually performing twenty similar actions wastes time and introduces inconsistency.

  • If the actions are similar but not identical — different lease dates, different vehicle details — the bulk import is still usually faster than individual entry, even with the post-import cleanup.

  • If you're correcting a property-wide error, the bulk approach is almost always right. Going one at a time risks missing rows and leaves the data inconsistent.

  • If you're doing something for the first time, run a small pilot batch (5–10 records) before the full bulk operation. Confirm the output looks right before scaling up.


Common Scenarios

"I just got a new rent-roll from accounting. What do I do?"

Use the Resident Data Manager (Import Accounts) to bulk-import the new roster. Review the Pending Imported Residents queue, then run Invite Residents to invite the new arrivals.

"Half my residents never registered."

Bulk-invite from Residents → Invite Residents. Watch the Resident Occupancy Rate widget on your dashboard to track acceptance over the following weeks.

"We're switching everyone in Building 3 to month-to-month leases."

Use the bulk lease editing feature. Confirm the target set is correct before applying, and verify the change in a sample of resident profiles after.

"Corporate wants a current list of all residents at this property."

Residents → Export User Data. Send the export.

"I need to add 15 new employees to the DNT list."

This is one-at-a-time. Set each entry's expiration date deliberately (and add a calendar reminder, since DNT doesn't notify before expiration). See Permit Types Explained.

"We're cleaning up vehicle records for the year."

Individual cleanup. If a large share of vehicles need the same correction, that may indicate an upstream data issue worth raising with ParkingPass Support before manually editing each row.

"A bulk operation I ran didn't do what I expected."

Check the Pending Imported Residents queue (for imports) for stuck rows. Review your User History for the actions logged. If something looks wrong, contact ParkingPass Support before re-running the operation.


Things That Sometimes Surprise PMs

The Resident Data Manager is the primary bulk tool

It's broad enough that most PMs assume it's the only bulk tool. The Invite Residents, Export User Data, and bulk lease features are all separate and worth knowing.

Vehicle data is downstream of resident data

Because each vehicle is tied to a specific resident permit, bulk operations on vehicles don't really make sense — the right unit to bulk-edit is the resident. If the resident is correct, the vehicle ends up in the right state.

"Bulk" doesn't mean "unaudited"

Every bulk operation is logged in the User History of affected accounts. If something looks wrong later, the audit trail is there.

Bulk imports can stall in the Pending queue

The Pending Imported Residents queue is where imported rows live until they're processed. Rows with missing or invalid data may stay here longer. Check this queue after every bulk import.

Bulk invitations don't guarantee bulk activations

Inviting 200 residents doesn't mean 200 will register. Plan for a follow-up cadence — typically a second invitation a week later — and watch occupancy rate over time.


Important Notes

  • Most bulk operations focus on the resident lifecycle. Vehicle, guest, DNT, and enforcement work remains one-at-a-time by design.

  • Bulk operations are powerful and irreversible at scale. A small pilot batch before a full import or invitation is rarely wasted time.

  • The Pending Imported Residents queue is the most common place where bulk imports surface issues. Make checking it part of your post-import routine.

  • Bulk lease management is a newer feature — confirm exact capabilities and any limits against the latest dashboard announcements.

  • If a bulk operation you need doesn't seem to exist, raise it through Provide Feedback — bulk capabilities have been added over time and may be added again.


Related

Did this answer your question?