Login
Sign in with a test admin or owner account and validate authentication before production release.
Internal testing before production
Rental Owner Hub support validation environment.
This subdomain is used internally to test code, database changes, file handling, permissions, admin workflows, owner workflows, vendor access, and support updates before moving changes to the live production site.
Validation shortcuts
Use these links to test the most common Rental Owner Hub workflows in the support environment. Update the URLs below if your support routes are different from production.
Admin Dashboard
Review dashboard counts, active properties, tickets, work orders, owner holds, inspections, and housekeeping alerts.
Admin Tickets
Validate ticket creation, assignment, categories, owner visibility, owner approvals, attachments, comments, and statuses.
Property Calendars
Test reservations, owner holds, maintenance blocks, management holds, onboarding holds, and iCal-related calendar behavior.
Cleaning Photos
Validate reservation-linked and non-reservation cleaning photos, work order photos, owner visibility, and month filters.
Document Uploads
Test owner statements, general documents, file storage, file access, and business/property scoping.
Support Tickets
Review internal support tickets and confirm support workflows are working correctly in the validation environment.
Code validation checklist
- Confirm all pages require the correct login role before showing data.
- Confirm every query is scoped by business_id where business data is involved.
- Confirm owners only see assigned properties and owner-visible records.
- Confirm vendors only access token-based work order pages intended for them.
- Confirm uploaded files save to the expected storage location and are retrievable.
- Confirm tickets, work orders, cleaning photos, inspections, damages, and documents do not cross business accounts.
- Confirm date and time displays use the property timezone where applicable.
- Confirm no production-only test changes are promoted until validated here.
Before moving code to production
Use this process so support changes are verified before they impact live users.
- Test the change on support.rentalownerhub.com.
- Validate admin, owner, and vendor workflows impacted by the change.
- Check PHP errors, SQL errors, permission issues, and file access.
- Confirm database table changes are present in the support database first.
- Document what changed and which pages were tested.
- Only then move the validated code to production.