A tenant portal app residents actually open.
A tenant portal app has three jobs, and residents judge it on all three within the first month: paying rent without a surprise on the receipt, reporting a problem and seeing what happens next, and finding the lease when a question comes up. Everything else, amenity bookings, announcements, package alerts, is decoration on top of those three. This page is the tenant side of the software: rent, maintenance requests and documents. The owner and board side, dues, violations and meeting notices, is a different job, covered under HOA and community association apps.
Below: the fields and rules each job needs, the rent payment fee schedule one major platform publishes, what a public housing authority portal asks of its residents, and where the AppFolio and Buildium portals stop and building your own starts.
See the three jobs a tenant portal has to doThe short version
Rent, requests, documents. In that order.
A tenant portal app needs a ledger the resident can read, every payment method with its fee shown before the money moves, a maintenance request form that captures enough to act on and a status the resident can check, and a document folder scoped to one lease. Off-the-shelf portals from AppFolio and Buildium do all three for managers already on those platforms. Owners under a vendor's unit minimum, operators with an unusual billing model, and anyone whose request workflow does not match the vendor's status set end up building their own. The rest of this page is what that portal has to contain.
The three jobs
What a tenant portal app has to do.
A resident opens the portal for one of three reasons. The portal that handles each in under a minute gets used; the one that hides the balance behind an announcement feed gets replaced by a phone call to the office.
Job one
Rent: the ledger comes before the pay button.
Most portal complaints are not about the payment failing. They are about a balance the resident cannot explain, a fee that appeared on the receipt, or an autopay that pulled a number nobody agreed to. The fix is the order of the screens: ledger first, amount due second, then the methods with their fees, then the button.
- A ledger the resident can read: every charge with its date, every payment, the running balance
- The next amount due and the date, on the first screen, before any payment button
- Bank transfer (EFT or eCheck), card, and a cash option at a retail counter for residents without a bank account
- The fee for each method, shown before the resident confirms, not on the receipt afterwards
- Autopay with a cap the resident sets, and a written rule for what happens when the balance is higher than the cap
- Partial payments allowed or blocked, decided once in the lease and enforced by the app
- Late fees posted as their own line, tied to the lease clause that created them
- A receipt for every payment, and a ledger export the resident can hand to a housing program or a lender
The fee disclosure is the piece worth copying from the incumbents. AppFolio's own portal help puts it plainly: transaction fees apply when paying online, and the resident is notified of the amount before submitting the payment. That sentence is the whole rule. Whatever the fee is, it is on the screen before the confirmation, and the resident cannot reach the confirmation without seeing it. Read AppFolio's Online Portal help
What one platform publishes for incoming payments
| Buildium plan | Plan price | Incoming EFT | Credit card |
|---|---|---|---|
| Essential | from $62 a month | $2.35 per transaction | 2.99% per transaction |
| Growth | from $192 a month | $1.35 per transaction | 2.99% per transaction |
| Premium | from $400 a month | First 12 months free, then $0.60 | 2.99% per transaction |
Figures from Buildium's pricing page, checked 21 September 2026. Plan prices are "starting at" figures; the page tells portfolios over 5,000 units to call for pricing. Outgoing EFT is a separate $0.99 per transaction on every plan.
Try it
What does paying rent online actually cost?
Set the monthly rent and pick a method. The figures are the incoming-payment fees Buildium publishes on its pricing page, checked 21 September 2026, before any convenience fee a manager adds on top.
EFT, Essential plan
$2.35
per payment
$28.20
per year, 12 payments
0.16%
of each month's rent
The same rent on a card would cost $538.20 a year. Flat fees favour higher rents; percentages punish them.
Who pays it is a setting the manager chooses, so decide that before a resident sees a payment screen, and show the answer on the screen.
Job two
Maintenance requests: a status the resident can read.
The request form is the easy half. The half that decides whether residents keep using the portal is what they see afterwards. If the answer to "is anyone coming?" is a phone call, the form was pointless. A request needs to capture this much on the way in:
- The unit and the resident on the lease, taken from the login, never typed
- A category: plumbing, electrical, heating and cooling, appliance, pest, locks and doors, common area, other
- What is wrong in the resident's own words, plus photos or a short video
- An emergency flag with the definition on the screen: no heat in cold weather, an active leak, no water, a gas smell, a lockout
- Permission to enter if nobody is home, and whether a pet is inside
- Preferred time windows, and a phone number a technician can call from the door
- A timestamp on every status change, and the scheduled window as soon as there is one
- Completion notes and photos from the technician, then the resident's confirmation before the request closes
The emergency flag deserves its own rule. It should route around the queue to a phone that is answered, and the definition should be on the form so residents do not have to guess whether a dripping tap counts. A flag with no definition gets set on everything, and then it means nothing.
A status set that answers the question before it is asked
| Status | What the resident sees | What moves it forward |
|---|---|---|
| Submitted | Received, with the time it was sent and the photos attached. | Someone in the office acknowledges it, ideally the same business day. |
| Acknowledged | A person has read it and it has an owner. | A vendor or in-house technician is scheduled. |
| Scheduled | The date, the window, and who is coming. | The technician arrives and starts work. |
| In progress | Work has started. | Finished, or paused because a part or access is missing. |
| Waiting on part or access | Why it is paused and what happens next. | The part arrives or a new window is agreed, back to Scheduled. |
| Completed | The technician's notes and photos, and a button to confirm. | The resident confirms, or the confirmation window expires. |
| Closed | Locked, in the request history with the full trail. | Nothing. A recurrence is a new request that links back to this one. |
Two details matter more than the names. A closed request is locked, so the trail cannot be tidied up after a dispute starts. And the resident's confirmation sits between Completed and Closed, so "fixed" is something the person living with the problem said, not something a technician ticked in a van.
Job three
Documents: the lease, the notices, the proof.
The document folder is where a portal earns trust slowly and loses it in one afternoon. The rule is scope: a resident sees everything attached to their lease and nothing attached to anyone else's. Inside that scope, these are the files people come looking for:
- The signed lease and every addendum, with the signature dates
- Notices the manager sends: rent changes, entry notices, renewal offers, each with the date it was delivered
- Move-in and move-out inspection reports, with photos, which is where damage disputes are won or lost
- Renters insurance: the upload, the carrier, the expiry date, and a reminder before it lapses
- Payment receipts and a ledger export
- For public housing and voucher households, the recertification packet and each verification document it asked for
The inspection reports are the ones to get into the portal early. A move-in report with dated photos, produced by whoever walked the unit with a property inspection app, is the baseline every deposit conversation comes back to. If the resident can open it from day one, the move-out conversation is short. Notices need a delivered date for the same reason: a rent change the resident never saw is a rent change that did not happen, and the portal timestamp is the evidence either way.
Public housing
Signing in to a PHA tenant portal, and what it asks of you.
A lot of people searching for a PHA tenant portal sign in app are residents of a public housing authority trying to find the right door. The confusing part is that the portal is not the authority's own software. Authorities run their resident portal on a vendor's platform, so the sign in app is the vendor's app, and the only reliable pointer to it is the authority's own website.
- 1Start from your housing authority's own website.Find its resident or tenant portal link there. Search results for a PHA portal show other authorities' portals, which look identical and will not have your account.
- 2Register with the details on your notice.If the authority issued a registration code, use it: that is what ties the login to your tenant file.
- 3Use the same login in the app the authority's page names.The app is the vendor's app, branded for the authority. The authority's page tells you which one; the app store cannot.
- 4Check the record before you pay.The unit, the head of household and the rent on screen should match your lease. If they do not, call the office first; a payment against the wrong record is slow to unwind.
- 5Turn on notifications for reexamination notices.The annual packet is the deadline that matters most, and it arrives on the authority's schedule, not yours.
The annual reexamination is the part the portal exists for.
Rent and work orders are the same job in public housing as anywhere else. What is different is the recertification. Under HUD's public housing rules, for a family paying income-based rent the authority must reexamine family income and composition at least annually and adjust the rent after verifying the information. Families on a flat rent get their composition reexamined annually and their income at least once every three years. A family can also ask for an interim reexamination when income or household changes, and the authority must handle it within a reasonable period, though it may decline one for an income decrease under ten percent of annual adjusted income. Read 24 CFR 960.257
That rule shapes the document side of a PHA portal. Each reexamination is a packet with a due date, a list of the verification documents the authority asked for, an upload slot for each one, and a status per document: received, verified, needs a better copy. A resident who can see which item is still missing does not get a late notice they could not have prevented. Voucher households have their own reexamination rules, but the portal mechanics are the same.
Off the shelf
AppFolio's tenant portal app, Buildium's Resident Center, and building your own.
Both incumbents ship a resident portal as part of their management platform rather than as a product you can buy on its own, which is the first thing to understand about the appfolio tenant portal app or Buildium's Resident Center: you get them by running the whole business on that platform. Here is what each publishes, and where a custom build sits next to them.
| AppFolio Online Portal | Buildium Resident Center | Custom-built portal | |
|---|---|---|---|
| Built for | Managers running AppFolio Property Manager | Managers running Buildium | Your process, whatever shape it is |
| How it is priced | Quoted per business; 50-unit minimum and a minimum spend on Core (pricing page, 21 September 2026) | Bundled with plans from $62 a month; Resident Center on every plan (pricing page, 21 September 2026) | An app builder subscription, plus your time defining fields and rules |
| Rent payments | eCheck, card and electronic cash; the fee is shown before the resident submits | EFT and card, with a published per-transaction fee schedule | The methods and fee policy you decide, wired to a payment processor |
| Maintenance requests | Submit and check status in the portal | Maintenance features on every plan; the resident-side detail is not on the pricing page | Your categories, your emergency rule, your status set |
| Documents | Shared documents, renters insurance upload, e-signed leases | Not detailed on the pricing page | Whatever you choose to show, scoped per lease |
| Resident app | Online Portal app for iOS and Android | Not stated on the pricing page | A native app published under your own name |
| Who maintains it | AppFolio | Buildium | You |
AppFolio column from its pricing page and Online Portal help; Buildium column from its pricing page. Both checked 21 September 2026. AppFolio's pricing page no longer prints a per-unit price at all; every plan says minimum spend and unit minimums apply and points to a quote.
One boundary worth drawing early: prospects are not residents. Tours, applications and the follow-up after a showing belong in an open house app with its own login model. Mixing the two flows into one portal is how a prospect ends up with a view of a building they do not live in yet.
When to build your own
When an off-the-shelf portal does not fit.
The usual reasons are not about features. A twelve-unit owner is under AppFolio's 50-unit minimum. A co-living operator bills by the room and splits utilities in a way no ledger template expects. A nonprofit housing provider needs a reexamination packet with per-document status, which is a public housing workflow, not a market-rate one. A manager wants the request statuses the technicians already use, not the vendor's. In each case the process is fixed and the software has to bend, and that gap, a workflow no packaged portal quite fits, is what Newly is for: describe the portal you actually run, the ledger, the request categories, the statuses, the documents each lease can see, and it builds a real native app around your rules rather than the vendor's.
Be clear about what that is and is not. Newly is an AI app builder, not property management software: it costs $25 a month with no free plan, it compiles your iOS build and submits it to App Store Connect where you finish the listing under your own Apple Developer account, and its current version does not produce Android release builds, which matters for a resident-facing app, so plan the rollout with that in mind. The accounting, the bank connection and the screening stay wherever they live today.
Decide these before anything is built
- 1Payment methods, and who pays the fee on each, written down before anyone sees a payment screen
- 2Request categories, the emergency definition, and who gets paged when the flag is set
- 3The status set, in order, and which transitions are allowed
- 4Which documents residents see, per lease, and which stay on the manager's side
- 5One login per person, tied to a lease, with an end date the day they move out
- 6What triggers a notification: a status change, a posted charge, a new document, and nothing else
The first item is the one that turns into real engineering. Showing a balance is a screen; taking the money is a payment processor, a fee policy and a reconciliation step, and that is its own decision, covered in collecting rent and payments in your app. Settle the six items on paper first; they are cheap to change before a resident has logged in and expensive after.
Sources
Where the specifics came from.
Every price, fee and rule on this page comes from one of these four pages, all opened on 21 September 2026:
FAQ
Tenant portal apps, answered.
A tenant portal app is the resident-facing side of a property's software: the place a renter pays rent and sees their ledger, submits and tracks maintenance requests, and finds the lease, notices and receipts. The manager's side holds the accounting and the unit records; the portal shows each resident only what belongs to their own lease.
Start with the ledger, not the login screen.
A tenant portal is judged on three screens: the balance, the request status, and the lease. Write down what each one shows and who can see it, then build the app around those rules in Newly.