Property Management
AppFolio and Yardi: self-guided tour access planning
Published by Phantom Workflow • Editorial contact: Kurt James
Last reviewed:
A self-guided tour workflow must verify software access, booking eligibility, visitor review, and property access as separate decisions. Confirm the supported AppFolio or Yardi integration route and the access-control vendor's capabilities. Identity verification alone does not authorize entry or eliminate fraud; staff-approved exceptions and recovery procedures remain necessary.
Planning guidance based on the sources below. These are proposed workflows, not completed Phantom projects or client results. Account access and suitability require separate verification.
Scope the buyer decision
A tour plan should document who approves entry, which property may be accessed, how the booking and access records relate, and how access is revoked. An identity result should be treated as one input to that procedure. Do not publish a promise that an identity check makes a visit safe or prevents an unauthorized stay.
What the documentation establishes
- AppFolio describes a partner application and review process for its Stack integration program. Source: AppFolio
- Yardi describes licensed interface access and a partner program with development and pilot testing steps. Source: Yardi
- Stripe documents Identity as a service for verifying identity documents and managing verification sessions. Source: Stripe
Proposed workflow and ownership
This table is a planning checklist. Confirm the account's supported access and the business's rules before implementation.
| Checkpoint | Decision to document |
|---|---|
| Booking | Confirm the property, appointment, and visitor eligibility. |
| Review | Apply the business's documented visitor and exception policy. |
| Access | Verify activation, revocation, and recovery with the access-control provider. |
Failure cases to review
Use these scenarios to define exceptions and staff ownership for this workflow.
- A canceled tour still has an active access credential.
- A visitor result is attached to a different booking.
- A provider outage leaves staff unable to grant or revoke access.
Pilot acceptance checks
Test cancellations, time-zone changes, failed verification, and access-provider outages. Confirm staff can see and revoke the relevant credential through a supported procedure.
Questions to resolve before a pilot
Does identity verification eliminate access risk?
No. The access decision also depends on booking eligibility, authorization, property controls, and staff review. Test the whole workflow and avoid guarantees about fraud prevention.
What should a pilot test?
Test cancellations, time-zone changes, failed verification, and access-provider outages. Confirm staff can see and revoke the relevant credential through a supported procedure.
Which documented options are relevant to this workflow?
AppFolio describes a partner application and review process for its Stack integration program. Yardi describes licensed interface access and a partner program with development and pilot testing steps. Stripe documents Identity as a service for verifying identity documents and managing verification sessions. Verify the permitted operations and account access for the intended pilot.
What should remain under staff control in this workflow?
Staff control access approval, exceptions, revocation, and outage recovery. Verify grant and revoke behavior with the access-control provider before allowing unattended tours.
Sources and scope
- AppFolio: AppFolio Stack partner program
Checked 2026-10-05. Documents vendor capabilities or a planning framework; does not verify Phantom delivery experience.
- Yardi: Become an Interface Partner
Checked 2026-10-05. Documents vendor capabilities or a planning framework; does not verify Phantom delivery experience.
- Stripe: Stripe Identity
Checked 2026-10-05. Documents vendor capabilities or a planning framework; does not verify Phantom delivery experience.
Review note: unsupported performance claims and unverified implementation examples removed on 2026-10-05.