Airtable is a strong foundation for property management because it can organize properties, tenants, leases, maintenance requests, payments, documents, inspections, and owner reporting in one flexible database. But once you need tenants, owners, applicants, or vendors to interact with that data, Airtable alone usually is not enough.

A property manager may need a public property catalog with a map, a tenant portal for maintenance and lease documents, a payment workflow for rent or fees, and an owner portal where property owners can review performance without seeing internal operations. miniExtensions lets you build those Airtable-powered experiences without custom development.

With miniExtensions, you can keep Airtable as the source of truth while giving each audience a focused interface: public visitors browse available properties, tenants manage their own requests and documents, and owners see the properties and reports linked to them.

What You Can Build

This setup can include:

  • A public property catalog with photos, availability, rent, location, and a map
  • A property inquiry form that saves requests or applications directly to Airtable
  • A tenant portal for lease details, maintenance requests, contracts, and payment history
  • A maintenance request workflow with photos, priority, status, and property/unit links
  • A payment or checkout form connected to Airtable and Stripe
  • An owner portal for property records, rent status, maintenance activity, and owner statements

The same Airtable base can support all of these workflows, while miniExtensions controls what each person can see and submit.

Recommended Airtable Base Structure

Start with these Airtable tables:

  • Properties: property name, address, location, photos, type, status, listing description, monthly rent, owner
  • Units: unit number, property, bedrooms, bathrooms, rent, availability, tenant, lease
  • Tenants: name, email, phone, current lease, current unit
  • Leases: tenant, property, unit, start date, end date, rent amount, lease status
  • Maintenance Requests: tenant, property, unit, issue type, description, photos, priority, status, assigned vendor
  • Contracts: tenant, property, unit, contract type, file attachment, status, start date, end date
  • Payments: tenant, property, unit, amount, due date, status, payment link, receipt link
  • Owners: owner name, email, properties
  • Owner Statements: owner, property, statement period, income, expenses, net amount, statement file
  • Inquiries: property, name, email, phone, message, desired move-in date, status

The key relationship is that tenant-facing records should link back to the Tenants table, and owner-facing records should link back to the Owners table. miniExtensions uses those linked records to show the right records to each logged-in user.

Step 1: Build the Public Property Catalog

Use a miniExtensions Interface for the public-facing property catalog.

  1. In miniExtensions, create a new interface. You could start with a Map Interface or Gallery Interface. Both are suitable starting points for browsing properties. You can always include the other in the same interface later, i.e. have a gallery and a map available to potential customers!
  2. Select the Airtable base that contains your property management tables.
  3. Select the Properties table.
  4. Choose the fields visitors should see, such as property name, address, rent, availability, photos, description, bedrooms, bathrooms, and listing status.
  5. Make sure to hide internal fields such as owner payout notes, internal status, management fees, vendor notes, and staff-only comments.
  6. Add filtering so the catalog only shows properties that are available, published, or ready for inquiry.
  7. Add a gallery, list, or map-style layout depending on how you want visitors to browse.
  8. For the map view, make sure each property record has location fields that can be used for mapping. If you don’t have latitudes and longitudes for properties yet, our Convert Address to Coordinates automation can turn all addresses in a table into GPS coordinates that can be used for the map view.
  9. Open the Share settings and copy the public link, embed the catalog on your website, or publish it through a custom domain if needed.

This gives visitors a browsable property catalog while keeping internal Airtable fields private.

Step 2: Add a Property Inquiry Form

Create a miniExtensions Form so visitors can inquire about a property without editing Airtable directly.

  1. Create a new Form extension.
  2. Select the same Airtable base.
  3. Select the Inquiries table.
  4. Add fields such as name, email, phone, desired move-in date, message, and property.
  5. If the form is launched from a property listing, prefill or pass the selected property into the inquiry when possible. Button fields can be used to add a simple “Apply now” button that opens the form from a listing in the property catalog.
  6. Add a confirmation message that tells the visitor what happens next.
  7. Share the form link from the property catalog, embed it on listing pages, or add it as the call-to-action for each property.

Every inquiry submitted through the form creates a new Airtable record, giving the property team a clean pipeline for follow-up.

Step 3: Create the Tenant Portal

Use a miniExtensions Portal so tenants can log in and see only the records linked to them.

  1. Create a new Portal extension.
  2. Select the Airtable base that contains your property management tables.
  3. In the Portal setup, select the first data table tenants should access. For many property management systems, this can be Leases,  Units, or Maintenance Requests, depending on what you want tenants to see first. You can add more tables later (see further steps below).
  4. Select the linked user field on that table that points back to the Tenants table. For example, if the first table is Leases, select the Tenant linked record field.
  5. Choose which fields tenants can view in each table.
  6. Make sure to hide internal fields such as staff notes, vendor cost, internal approval status, owner notes, Stripe IDs, and management-only comments.
  7. Customize labels so the Portal feels tenant-friendly, such as “My Leases,” “Maintenance Requests,” “Documents,” and “Payments.”
  8. Use the Share settings to send the tenant portal link or login links to tenants.

You do not need to set up an extra filter so each tenant only sees their own records. The Portal automatically shows records linked to the logged-in tenant based on the linked user field selected during setup.

Step 4: Add Maintenance Requests Inside the Tenant Portal

Maintenance requests are usually the most important tenant-facing workflow.

  1. In Airtable, make sure Maintenance Requests has a linked record field to Tenants.
  2. Add linked fields to Properties and Units if requests should be tied to a specific property or unit.
  3. In the tenant Portal, add the Maintenance Requests table.
  4. Allow tenants to create new maintenance request records.
  5. Configure the create form with fields such as issue type, description, priority, photos or attachments, preferred access time, property, and unit.
  6. Let tenants view (but not edit) status fields such as submitted, scheduled, in progress, completed, or closed.
  7. Optionally allow tenants to edit limited fields while a request is still open, such as adding photos or updating the description.

Records created from inside the Portal are automatically linked to the logged-in tenant. You do not need to add the Tenant field to the tenant’s create form just to connect the request to that tenant.

Step 5: Show Contracts and Lease Documents

The tenant portal can also act as a secure document hub.

  1. Store lease files, signed contracts, addendums, move-in documents, and policy documents in the Contracts table.
  2. Link each contract record to the related tenant, lease, property, or unit.
  3. Add the Contracts table to the tenant Portal.
  4. Show fields such as contract name, contract type, property, unit, status, start date, end date, and file attachment.
  5. Hide internal review notes, staff-only approval fields, and unrelated owner information.
  6. If tenants need to upload a document, add a Form or Portal create action that writes to a document upload table.
  7. Keep the upload form focused on fields like document type, attachment, notes, and related lease or unit.

This works well when Airtable is already the document record system. miniExtensions gives tenants a simple place to view and submit documents without exposing the Airtable base.

Step 6: Add Payments and Payment History

For payments, Airtable can track what is due, what was paid, and where receipts are stored. miniExtensions can provide the payment form or redirect flow, while Stripe handles the payment processing.

  1. In Airtable, create or update the Payments table with fields such as tenant, property, unit, amount, due date, payment status, payment link, receipt link, Stripe payment ID, and notes.
  2. Link each payment record to the related tenant.
  3. Add the Payments table to the tenant Portal.
  4. Show tenant-safe fields such as amount, due date, status, payment link, and receipt link.
  5. Hide internal fields such as Stripe IDs, reconciliation notes, internal accounting notes, and staff-only fields.
  6. If tenants should submit payment information through a miniExtensions Form, create a Form extension for the Payments or Payment Requests table.
  7. Select the Airtable base, then select the payment-related table.
  8. Add the fields tenants should complete before payment, such as name, email, property, unit, amount, or payment reason.
  9. Configure the Stripe integration with Airtable and configure the form to redirect to the correct Stripe checkout or payment URL after submission.
  10. Store payment status and receipt details back in Airtable so the tenant portal can show the latest payment information.

For a cleaner tenant experience, the Portal can show open balances and payment links, while the Form handles the checkout step.

Step 7: Create the Owner Portal

Owners need a different view from tenants. They may need property performance, maintenance activity, rent status, documents, and owner statements, but they should not see tenant-private notes or internal staff workflows.

  1. Create a second Portal extension for owners.
  2. Select the Airtable base.
  3. In the Portal setup, select the first owner-facing data table. This could be Properties,  Owner Statements, or another table linked to owners. You can add more tables later.
  4. Select the linked user field on that table that points back to the Owners table. For example, if the first table is Properties, select the Owner linked record field.
  5. Configure Users & Login using the Owners table as the user table, with the owner email field used for login.
  6. Add owner-facing tables such as Properties, Owner Statements, Maintenance Requests, and Payments.
  7. Show useful fields like property status, occupancy, rent collected, maintenance status, statement period, income, expenses, and statement files.
  8. Hide tenant contact details, staff notes, vendor negotiation notes, internal accounting notes, and private tenant documents unless owners are meant to see them.
  9. If owners should submit requests or notes, enable record creation for an owner request table.
  10. Share the owner portal link from the Portal Share settings.

Just like the tenant Portal, the owner Portal automatically shows records linked to the logged-in owner. If an owner creates a record from inside the Portal, that new record is automatically linked to the logged-in owner.

Step 8: Share and Launch the System

Once the catalog, forms, tenant portal, and owner portal are ready:

  1. Test the public property catalog as an anonymous visitor.
  2. Submit a test inquiry and confirm it creates the right Airtable record.
  3. Log in as a test tenant and confirm only that tenant’s leases, requests, contracts, and payments appear.
  4. Create a test maintenance request from the tenant Portal and confirm it is automatically linked to the logged-in tenant.
  5. Log in as a test owner and confirm only that owner’s properties and reports appear.
  6. Review hidden fields across every table before sharing links externally.
  7. Share the public catalog on your website.
  8. Send tenant portal login links to tenants.
  9. Send owner portal login links to property owners.

Testing with separate tenant and owner records is the easiest way to verify the record visibility before launch.

Why This Works Well for Property Management

Airtable gives property managers the flexibility to model their exact operations. miniExtensions turns that Airtable base into role-specific experiences for public visitors, tenants, and owners.

The public catalog helps generate inquiries. The tenant portal reduces back-and-forth around maintenance, contracts, and payments. The owner portal gives property owners visibility without inviting them into internal Airtable workflows.

Together, Airtable and miniExtensions can support a complete property management system without building a custom web app from scratch.