Every resident profile in ParkingPass includes six activity logs that together form a complete history of what's happened to that resident's account — who did what, when they did it, and what communications were sent. These logs are the system of record for accountability questions, dispute backup, and troubleshooting.
This article walks through each log: where to find it, what it captures, and when to use it.
Where the Logs Live
All six logs are tied to an individual resident's profile. To get there, open Residents, find the resident in question, and open their profile.
Three of the logs are accessed at the bottom of the resident profile:
View User History
View User Page Views
View Login Attempts
The other three are accessed through the Quick Actions dropdown at the top right of the profile:
View Email Log
View SMS Log
View Call Logs
User History
The single most useful log for accountability questions. User History records every meaningful action taken on or by the resident's account — account creation, application changes, vehicle additions, guest pass creation, payment events, and so on.
Columns captured
Timestamp — Date and time the action occurred.
Activity — A description of what happened (e.g., "Alisa Khaietska created their account successfully!").
Performed By — Who did it. This can be the resident themselves, a property management user, or the system.
Category — The functional area (User Account, Application, Payment, etc.).
Details — A View Details button that opens the full record for that activity.
Filters
Filter By Category — Narrow to a specific activity type.
Filter By Date Range — Narrow to a window of time.
Search — Free-text search across the log.
When to use it
"Who approved this application?" — User History shows the Performed By for the approval action.
"When did the resident actually register?" — Look for the account creation entry.
"Did a staff member edit this record?" — Performed By distinguishes staff actions from resident actions.
Dispute backup — If a resident claims they did or didn't do something, User History is the authoritative record.
User Page Views
Captures which pages the resident has viewed in their portal, along with technical details about the visit. Useful when you need to confirm whether a resident actually engaged with content the property published or sent.
Columns captured
Page — The page the resident viewed.
Referral URL — Where the resident came from (helpful for understanding whether they arrived from an email link, a portal navigation, etc.).
IP Address — The IP they viewed from.
Browser — The browser used.
Operating System — The OS used.
Timestamp — When the view occurred.
Filters and export
Filter By Date Range
Search box
Export Data option — Pull the data out for sharing or archiving.
When to use it
"The resident says they never saw the new policy." — Page Views confirms whether they opened the policy page.
"Did the resident actually log in and view their account?" — Confirms portal engagement and where they accessed from.
"They claim someone else accessed their account." — IP and browser details help establish whether a session was consistent with the resident's normal usage.
Login Attempts
A record of attempts to access the resident's account — successful and failed both.
Columns captured
Method — How the login was attempted.
Status — Whether the attempt succeeded or failed.
Login Using — The credentials used (e.g., email, phone).
IP Address — The IP the attempt came from.
Browser — The browser used.
Timestamp — When the attempt occurred.
When to use it
"The resident can't log in." — Login Attempts shows whether they're actually trying and what's failing.
Suspicious activity. — Repeated failed attempts, especially from unfamiliar IPs or browsers, can indicate someone trying to access the account.
Verifying account access. — Confirms whether the resident has actually logged in at any point.
Email Log
Every email sent to the resident's address through ParkingPass appears here, with delivery status.
Columns captured
Email Status — Delivered, bounced, or other delivery state.
Recipient — The email address it was sent to.
Subject — The email's subject line.
Timestamp — When it was sent.
View Email — A button that opens the full content of the email as it was delivered.
Filters
Filter By Date Range
Search box
Apply Filter / Apply Date Filter buttons
Retention
Email records are retained for 2 years and then automatically purged. Emails older than two years are no longer available for viewing. If you need a record of an old email for legal or audit purposes, capture it before it ages out.
When to use it
"The resident says they never got the renewal notice." — Email Log shows whether it was sent, whether it was delivered, and what it said.
"What exactly did we send them?" — View Email lets you read the message as the resident saw it.
Bounce diagnostics. — If emails to a resident keep bouncing, the log shows the pattern and timing.
Audit support. — For HOA boards or property leadership asking what was communicated to a specific resident, this is the source of truth.
SMS Log
A record of SMS text messages sent to or received from the resident.
Columns captured
Direction — Whether the SMS was sent to the resident or received from them.
From — The sending number.
To — The receiving number.
Message — The full text of the message.
Status — Delivery state.
Cost — The per-message cost (SMS is metered, so this matters for billing or volume questions).
Date Sent — When the message was sent.
Details — Additional information per message.
Filters
Filter By Date Range
Search box
Retention
SMS logs are provided by Twilio and are retained for approximately 400 days. Messages older than that are no longer available for viewing. Note this is a shorter window than Email Log's 2 years — long-running disputes that span beyond a year may lose their SMS context.
When to use it
"Did the resident get a text reminder?" — Confirms whether and when an SMS was sent.
Two-way SMS exchanges. — Direction lets you see both sides of any text conversation.
Verifying notification preferences. — If the resident has SMS notifications disabled, this log will be empty for the period.
Dispute backup. — Same role as the Email Log for SMS-channel communications.
Call Logs
Records of voice calls associated with the resident's account. The Call Logs interface mirrors the SMS Log structure (both are Twilio-backed) and shows the same kinds of columns — direction, from/to numbers, status, cost, timestamp, and per-call details.
Retention
The same ~400-day Twilio retention window as SMS applies.
When to use it
Verifying voice notifications. — If your property uses voice-channel notifications, this log shows what's been sent.
Troubleshooting unanswered calls. — Confirms whether the call was placed and whether it connected.
Cost or volume questions. — Voice is metered like SMS, so the cost column matters when reviewing usage.
How to Use These Logs Together
Most real investigations use more than one log.
Scenario: "The resident says they never got the new parking policy."
Open the Email Log — find the policy email, confirm it was delivered, click View Email to see what they got.
Open User Page Views — check whether they opened the email's policy link or visited the policy page in the portal.
If both show the resident received and engaged with the policy, the dispute claim doesn't hold up.
Scenario: "Did anyone at our office approve this application?"
Open User History — find the application approval entry.
Check the Performed By column — that's who approved it.
Click View Details if more context is needed.
Scenario: "The resident is claiming they never saw the violation warning."
Email Log — was a notification email sent? Delivered?
SMS Log — was a text sent (if SMS notifications are enabled)?
Login Attempts — has the resident logged into their account during the period in question?
Page Views — did they view the violation in the portal?
Scenario: "An HOA board member is asking what we've told a specific resident over the last year."
Email Log — pull the full year. Each subject line is a summary; View Email shows the body.
SMS Log — pull the same date range for text history (within the ~400-day Twilio window).
User History — for non-communication actions (approvals, edits, fee adjustments).
Export Page Views or screenshot what you need before retention windows start to come into play.
Scenario: "Someone says their account was accessed by another person."
Login Attempts — review IP addresses and browsers for the period in question.
Page Views — cross-check IP and browser data on what was viewed during the suspect sessions.
User History — look for actions taken during the suspect sessions to see what was changed.
HOA Accountability and Dispute Backup
The logs are especially valuable for HOAs because of the board oversight model. When a resident raises an issue at a board meeting, having the underlying communication and activity record available shortens the conversation considerably.
Practical use
Before a board meeting involving a specific resident, pull their User History and Email Log for the relevant period. Bring screenshots or exports to the meeting.
During a dispute review, reference the specific User History entry that documents the disputed action.
For PM turnover, the logs preserve institutional memory that doesn't depend on the previous PM remembering the case.
For audits, the logs provide a verifiable record of what the property communicated and when.
Retention Summary
Different logs have different retention windows. Plan around them:
Email Log — 2 years, then auto-purged.
SMS Log — ~400 days (Twilio-provided).
Call Logs — ~400 days (Twilio-provided).
User History, Page Views, Login Attempts — Retained for the lifetime of the resident's account. For long-term legal records, capture out of the system to be safe.
Common Questions
How far back do these logs go?
It varies by log — see the Retention Summary above. Email is 2 years, SMS/Calls are about 400 days, and the others are retained for the account's lifetime.
Can I export the logs?
Page Views has an explicit Export Data option. For other logs, use date-range filtering and screenshots, or contact ParkingPass Support if you need a structured export for a specific situation.
Can residents see their own logs?
Residents can see their own activity in their resident portal, but the property-side logs (with Performed By identifying staff users) are visible only to property management.
Are staff actions logged too?
Yes. The Performed By column in User History distinguishes between actions taken by the resident, actions taken by a property management user, and actions taken by the system (automatic notifications, scheduled events, etc.).
What if a resident's record was edited and I want to see the previous values?
User History records that the edit occurred and who made it. For the actual before/after values, open the specific entry's View Details if available. If that doesn't show what you need, contact ParkingPass Support — they may be able to retrieve historical state.
What if I think the logs are wrong or missing entries?
Contact ParkingPass Support with the specific resident, the action you expected to see logged, and the timestamp. Missing entries are rare but worth investigating.
Where do logs for guest vehicles or third-party DNT entries live?
Logs are tied to user accounts. For a guest vehicle, look at the host resident's User History. For DNT entries, the action would appear in the User History of whichever staff user added the entry, or you can look at the DNT list itself for the audit trail.
Important Notes
The logs are intended as records of activity, not as a real-time monitoring tool. They are most useful when reviewed in response to a specific question.
Retention windows differ across logs. The shortest is SMS and Calls at ~400 days; the longest are the lifetime-retained ones (User History, Page Views, Login Attempts).
The Performed By field is the key distinguishing feature between resident-initiated and staff-initiated actions. Always check it when accountability is at issue.
For long-running disputes or audits, capture relevant log entries outside the platform before retention windows close in.
These logs are confidential to property management. They include communication content, login activity, IP addresses, and access patterns — handle them with the same care you'd give any other resident data.