How do I get an account?
Use Request Access or an invitation link. A request does not create an account by itself; an authorized admin, owner, or supervisor must approve it before you can sign in.
PropertyWork
Searchable help
Search by word, role, category, or workflow. Use this when you need to figure out what a page is for, what to do next, or where a feature lives.
Use Request Access or an invitation link. A request does not create an account by itself; an authorized admin, owner, or supervisor must approve it before you can sign in.
Open Setup Guide, change any temporary password, confirm your role-specific checklist, then use Dashboard or Today as the daily starting point.
Basic allows up to 3 properties per plan year for $49.99 monthly or $499 yearly. Pro allows unlimited properties for $99.99 monthly or $999 yearly. Trials allow 1 property for 1 month and require a card once Stripe checkout is connected.
Yes. Platform admin can apply a temporary bypass date, a permanent/manual bypass, or a manual beta/internal status. Existing manual owner accounts are intentionally non-blocking.
The owner dashboard can focus on one active property for day-to-day work, while Portfolio Records still covers all properties in the business.
Open Rentals, add the rental type, vendor, cost, frequency, next charge date, optional reminder date, and return due date. Use next charge date for when it renews if not stopped.
Yes. Each rental can use in-site notifications, push-ready notifications, or both. Push will work after Firebase credentials are configured and the Android app has a token.
From Rentals, use Record renewal charge. It creates a money expense in the rentals category, links it back to the rental, and can auto-advance the next renewal date by the selected frequency.
Portfolio Records is the owner/accountant center for all-property expenses, payments, categories, proof status, tax review, exports, and sale/profit records.
Use account requests, invitations, or manual create only for controlled setup. Every user should have the correct role and property scope before doing work.
Use Work to create assignments, set due dates, assign workers, review submitted proof, request rework, and keep work status current.
Create or review supply requests instead of burying needs in texts. Requests can be approved, marked purchased, received, and converted to expenses when appropriate.
Use Time to review field check-in, check-out, and lunch activity for workers in your scope. GPS fields are event-based, not continuous tracking.
Supervisors can see rental records tied to properties in their scope, including renewal dates, return dates, reminders, and active/ended status.
Open Today or My Work. Read instructions, safety notes, deadline reasons, proof requirements, and next action notes before updating progress.
Update the work status and progress, add a completion note, and upload required proof through the web app/full site when needed. Completed work can be reviewed and approved or sent back for rework.
Create a supply request with the property/work context, estimated amount, priority, preferred supplier, and details. The request stays clickable and reviewable.
Only check in, check out, or record lunch when you are working and when the property/business requires field time tracking.
Linked messages keep conversations attached to a property, work item, payment, expense, or supply request so context is not lost.
Yes. Notifications can be opened, marked read, cleared one by one, or cleared all at once. Clearing the inbox does not delete the underlying work, supply, rental, or message record.
The Android app opens to the dashboard and keeps dashboard, messages, supply requests, notifications, and full site tabs in the requested order. Push requires Firebase credentials.
Stripe/Supabase setup is still required for live checkout, card collection, subscriptions, webhooks, customer mapping, and automatic enforcement. PropertyWork already tracks the plan rules and setup todo.
Use Deployment Check, Permission Audit, System Health, Backups, and Support View. Support View must show the banner and log the session reason.