Choose which properties to sync

For: An ops lead whose PMS holds more properties than they want flowing into PropSocket.

You’ll accomplish: deciding whether to sync everything or approve properties one by one, turning individual properties on or off, and understanding what happens to a property’s data when you disable it.

PropSocket can see every property your PMS exposes to it. That’s not always what you want — maybe a portfolio has properties managed by a different team, or you’re piloting with a handful of communities first. You can control this per property, without touching anything in your PMS.

You don’t need to write any code for this.

---

1. Decide: sync everything, or approve properties first

When you connect an integration, you choose one of two starting points:

• Sync everything (the default). Every property your PMS exposes is enabled, and PropSocket starts pulling its units, residents, and leases right away. Choose this when you want all the properties your PMS account can see.
• Require property approval. PropSocket discovers the list of available properties on the first sync but does not pull any of their units, residents, or leases until you enable them one by one. Choose this when you only want a subset, or when you want to review the list before any data comes in.

This is the Require property approval before syncing setting, on the integration’s Edit Configuration form. Turning it on means “show me the properties, but don’t sync their data until I say so” — newly discovered properties stay paused until you approve each one.

If you’re not sure, start with require property approval on a large or shared PMS account. It’s easier to enable the properties you want than to clean up data from properties you didn’t.

2. Review the discovered property list

After the first connection and sync, PropSocket builds a list of every property it found in your PMS. For each one you’ll see its name and an Enabled or Disabled badge. Enabled properties also show a health indicator — Healthy, Degraded, Failing, or No Data — and, when something’s wrong, a short error message so you can spot a property that’s connected but not syncing cleanly.

This is your control panel for what syncs. A property in this list is either:

• Enabled — PropSocket syncs its units, residents, and leases on the normal schedule.
• Disabled — PropSocket ignores it. None of its child data is pulled or updated.

3. Enable or disable individual properties

1. Open the property list for the integration.
2. Find the property you want to change.
3. Click its Enabled / Disabled badge to flip it, and confirm when prompted.

Need to flip everything at once? Use the Enable All or Disable All buttons above the list to toggle every property in the integration in one step.

Changes take effect on the next sync, not instantly. If you just enabled a property and want its data now, see Run a manual sync rather than waiting for the next scheduled run.

When you enable a property that was off, its units, residents, and leases load in over the next sync or two — larger properties take a little longer to fully populate.

4. What happens to data when you disable a property

This is the part people worry about, so plainly:

• Disabling a property stops it from updating. PropSocket won’t pull new changes for its units, residents, or leases.
• The data already synced does not disappear on its own. It stays in PropSocket as it was at the last sync. It’s just frozen — not refreshed, not deleted.

So disabling is safe and reversible. Re-enable the property later and PropSocket picks it back up on the next sync, refreshing it to match your PMS again.

If you’re disabling a property because you’re leaving a PMS or winding down a relationship, read Pause, resume, or remove an integration for the full off-boarding path, including how to export your data first via an Automation.

---

If this didn’t work

If a property you expected isn’t in the list, a toggle won’t stick, or a property you disabled is still pulling data after a full sync cycle, we’ll help you sort it out.

Open a support ticket by emailing support@propsocket.io and include:

• Integration ID (the long ID in the integration page’s URL, e.g. …/integrations/3f9c2a1b-…/)
• The property name and whether you were trying to enable or disable it
• What you expected vs. what you saw
• A screenshot of the property list

You don’t need to send any data records or credentials — the integration ID and property name are enough for us to find it.