Buildings On/Off Mock

A clickable mockup of a new Settings page where any customer user turns buildings on or off and picks which modules run at each one. Built from the Situs Group onboarding call on 2026-09-29.

2026-09-29 · mockup for logic and flow, not final styling · waiting on 5 decisions (bottom of page)

Mockup · logic and flow only, not final styling · example data from Situs Group's AppFolio list
Settings
Buildings

Choose which buildings are in Propflow and what Clara does at each one. Anyone on your team can change this.

Your plan

These are the modules your company has. A building can only use modules that are in your plan. Talk to us to add one.

BuildingUnitsIn Propflow LeasingRenewalsMaintenanceCollections NotesStatus

Recent changes

No changes yet. Each change is listed here with who made it, and you can undo it.

Details: the three states, where else the switches appear, and 5 questions to settle

The three states a building can be in

StateOn the dashboardClara knows itClara acts thereExample
OffNoNoNo446 Galapago, "DO NOT USE" entries
Dashboard onlyYesYes, can answer "we don't handle that here"NoLowry Flats, 6838 Lowell (run by the owner)
On, with modulesYesYesOnly for the ticked modulesBryant Gardens with Leasing + Maintenance

"Dashboard only" is simply a building that's on with no modules ticked. There's no separate dashboard switch.

The same switches show up in three other places

Top of each building's own settings page
Bryant Gardens ApartmentsOn · Leasing, Maintenance
In Propflow
Onboarding: "Pick your buildings" step

Same table, same junk warnings, and everything starts off. What they pick here is exactly what they see later in Settings.

Propflow staff: the company's admin page

The same table, so staff see what the customer sees. Staff can also change the plan.

Behind the scenes (not a screen)

Every part of Clara checks one question before acting: "is this module on for this building?" That covers calls, emails, texts, AppFolio changes and background jobs.

Questions to settle before building

  1. New buildings added in AppFolio later. This mock brings them in off with a "New from AppFolio" tag, so someone has to turn them on. Or should they arrive on?
  2. Who controls the plan. This mock has Propflow staff set the plan, because it's tied to billing. Customers can only choose within it. Toggle "View as Propflow staff" at the top to see the difference.
  3. Turning a building off. This mock keeps its past conversations and work orders visible and only stops new activity. Or should they be hidden too?
  4. Notes. Each building has an optional notes thread (the "+ Note" link in each row). Notes show who wrote them and when, and both sides can reply. A new note from the customer shows a dot for Propflow staff. Should a new note also ping us in Slack?
  5. Dashboard. This mock treats "on with no modules" as dashboard-only. Or do you want a separate Dashboard checkbox?

Turn off building?

Past conversations and work orders stay visible. You can turn it back on anytime.

Notes

Visible to your team and the Propflow team. We read every note.

PropFlow Docs