1. Before you start
- Choose the Seedling workspace that should own the connection and confirm you are a current administrator if this will be a workspace connection.
- Enable or request Propertyware Open API access for the Propertyware account and portfolio you intend to connect.
- Obtain the System / Org ID, Client ID, and Client Secret from your organization's authorized Propertyware administrator or Propertyware representative.
- Confirm Propertyware API access is configured with all 13 read permissions listed in the integration guide.
- Do not send a Client Secret, customer record, financial data, tenant information, or document content by email or through an ordinary support ticket.
2. Connect Propertyware
- Sign in to Seedling and select the intended workspace.
- Open Apps or Connections, select Propertyware, and choose a workspace or personal connection as appropriate.
- Enter the exact System / Org ID, Client ID, and Client Secret.
- Leave Base URL blank to use https://api.propertyware.com/pw/api/rest/v1, unless the account uses a different HTTPS propertyware.com API host.
- Connect and wait while Seedling checks Propertyware health and verifies the account through the portfolio endpoint.
- For a workspace connection, configure the connection's member access by data type, portfolio, or property before expecting other members to read synchronized records.
- Allow the initial bounded synchronization to complete before evaluating coverage.
3. Credential and connection problems
- Propertyware rejected the credentials
- Recheck the System / Org ID, Client ID, and Client Secret without adding spaces. Confirm Open API is enabled for the intended Propertyware account.
- Wrong API host
- Remove a copied custom Base URL to use Seedling's default host, or confirm the custom URL with the administrator who issued the credentials.
- Missing read permission
- Restore the applicable Propertyware :Read permission. Seedling does not substitute write access or silently skip a required permission.
- Account already connected
- One active workspace connection per integration kind is supported in a Seedling workspace. Disconnect the existing Propertyware connection deliberately before replacing it.
- Connection requires new credentials
- Ask a Seedling workspace administrator or the personal connection owner to replace the credentials with a newly issued Client Secret.
4. Missing or delayed data
- Confirm the connection is active and the expected portfolio or property belongs to the connected System / Org ID.
- Confirm the relevant Propertyware read permission is enabled and that the endpoint is available for the account's licensed features.
- For workspace connections, confirm the affected member has an active declared grant for the data type, portfolio, or property. Workspace administrators and stewards do not receive a raw-content bypass.
- Remember that routine work-order task coverage prioritizes open and recently modified work orders; a configured deep scan may be needed for older closed work orders.
- Allow incremental synchronization and retry handling to complete. A temporary provider failure does not delete previously synchronized data.
- If the issue remains, contact support@tryseedling.ai with the Seedling workspace, safe timestamps, the System / Org ID, and non-sensitive Propertyware record IDs. Do not include credentials, record contents, tenant data, financial details, or documents.
5. Rotate credentials
Never use email or an ordinary support ticket to transfer the old or replacement Client Secret.
- Have the authorized Propertyware administrator issue or identify the replacement API credentials.
- In Seedling, open the exact Propertyware connection and replace its System / Org ID, Client ID, Client Secret, or Base URL as needed.
- Confirm the credentials still resolve to the intended Propertyware account and restore all required read permissions.
- After Seedling verifies the replacement, retire the old credential through your organization's Propertyware access process.