Propertyware integration

Last updated date:

How Seedling connects to Propertyware Open API, which read-only data it uses, and how workspace administrators control access and deletion.

1. Overview

The Propertyware integration brings authorized property, lease, maintenance, accounting, contact, vendor, inspection, and document information into a Seedling workspace. Seedling uses that information for source-backed search, operating context, verification, and customer-approved workflows.

Propertyware offers a two-way Open API, but Seedling requests and uses only read permissions. Seedling does not create, update, or delete records in Propertyware.

2. Connection and scope

Seedling verifies the credentials against the Propertyware health and portfolio endpoints before storing the connection. The System / Org ID is the external account identity; names and email addresses are not used to infer ownership.

Customer-managed API credentials
Your organization enables Propertyware Open API and supplies its System / Org ID, Client ID, and Client Secret through Seedling's encrypted connection form. A custom API base URL is optional and must be an HTTPS propertyware.com host.
Workspace connection
A current Seedling workspace administrator connects the authorized Propertyware account for shared workspace use. Access to synchronized records is assigned through connection-specific data-type, portfolio, and property grants.
Personal connection
A signed-in member may connect actor-owned credentials. Raw records from that connection remain visible only to that member in human-facing Seedling surfaces.

3. Propertyware data Seedling accesses

The exact records available to Seedling depend on the portfolios and features enabled for the connected Propertyware account. An accessible endpoint that returns no records is treated as an observed empty result, not proof that the organization does not use that feature.

Portfolio and property structure
Portfolios, buildings, units, leases, contacts, and supported custom fields, including active and deactivated records returned by the authorized API scope.
Maintenance and inspections
Work orders, work-order tasks, inspections, status, assignment, timing, and related property context.
Accounting
Lease transactions, vendors, bills, bill payments, vendor checks, general-ledger accounts and transactions, and owner transactions.
Documents
Document metadata and authorized file content when available. Seedling limits an individual downloaded document to 10 MB for this integration.
Connection operations
System / Org ID, encrypted API credentials, verified read permissions, API base URL, synchronization checkpoints, source scope, and bounded failure information.

4. Exact read-permission contract

Seedling rejects credentials that Propertyware cannot verify for the requested account. A connection can be partial when a specific authorized endpoint is unavailable; Seedling reports that condition instead of broadening permissions or deleting previously synchronized records.

  • PORTFOLIOS:Read, BUILDINGS:Read, and UNITS:Read — portfolio and property structure.
  • LEASES:Read and CONTACTS:Read — lease and contact records.
  • VENDORS:Read and BILLS:Read — vendors and accounts-payable records.
  • GL ACCOUNTS:Read and GENERAL LEDGER:Read — accounting structure and transactions.
  • WORK ORDERS:Read and INSPECTIONS:Read — maintenance and inspection records.
  • DOCUMENTS:Read — document metadata and authorized content.
  • CUSTOM FIELD:Read — supported custom-field definitions and values.

5. Security and access

  • Propertyware API credentials are encrypted in the Seedling workspace's tenant data plane, are never returned to the browser, and are excluded from logs and queue payloads.
  • Every source, sync, secret lookup, audience contribution, disconnect, and purge remains bound to the exact Propertyware connection that created it.
  • Propertyware does not expose sufficient principal-level access evidence for Seedling to reproduce native user permissions. Workspace access therefore fails closed until an owner or steward assigns an active member to an available data-type, portfolio, or property grant for that exact connection.
  • Trusted exploration may analyze eligible connection data, but raw personal-connection content remains owner-only and member-facing publication follows Seedling's separate review and sanitization controls.
  • Generated output cannot bypass Seedling's human review, verification, and approval gates.

6. Retention and deletion

Connected data
Synchronized Propertyware records remain while the connection is active and are removed through a durable integration purge after disconnect.
Credentials
The Propertyware Client Secret and other connection credentials are deleted from active Seedling systems as part of the connection purge.
Backups
Deleted information may remain in encrypted, access-restricted backups until expiry, ordinarily within 35 days after active-system deletion.