Skip to main content

Integration field capabilities

The Integration capabilities tab at /settings/integrationFieldCapability is a read-only reference matrix. It shows which property and listing (unit) detail fields from the booking-engine payload editor are supported for each connected marketplace integration, and whether a partner marks a field as required when publishing.

Use it when you are preparing Property & listing details (booking engine) content and need to know what a channel expects before you edit fields in Listings → Full integration pill. Credentials, toggles, and calendar rules still live on Integrations and per-unit Channels.

First-time workspace setup

Read this matrix during Getting Started — Recommended Setup Sequence steps 11–12 alongside Integrations and Tenant categories default for integrations before you link units on Listings → Channels in step 13 — full tab map: Recommended setup order. Finish steps 14–15 and Onboarding a New Property — Step 7. Partner payload reference: API Reference — Property & Unit Mapping. Workflow pairing after go-live: Account Settings — Setup sequence after go-live.

Direct access

Open Account Settings → System → Integration capabilities at platform.vivin.app/settings/integrationFieldCapability. Requires the same integration-related settings permission as the Integrations tab (account_settings.integrations). See Deep Links — Account Settings.

Pair with other Account Settings tabs

Read-only matrix — connect platforms on Integrations first, then link units on Listings → Channels using external IDs this matrix references. Month-end partner payload triage pairs with Portfolio KPI review — Step 7 and optional AI usage API (landlord_chat when AI Chat helped close field gaps). Section-to-doc pairing: Integration field capabilities section cross-reference. Hub tab matrix: Account Settings — Tab cross-reference.

Who can open it

Pair with other Integration capabilities sections

Same integration-settings permission family as Integrations — audit Users and roles — Role Permissions before sharing the matrix URL with channel coordinators. Full pairing matrix: Integration field capabilities section cross-reference.

The sidebar entry appears under Account Settings → System when your role includes integration settings access (same permission family as Integrations). Without it, the tab is hidden and the URL shows the standard permission state.

Filters

Pair with other Integration capabilities sections

Integration depth switches between partial calendar feeds and full outbound payloads — see Integrations & Distribution and API Reference — partial vs full feeds before narrowing columns. Full pairing matrix: Integration field capabilities section cross-reference.

Three controls narrow the matrix:

FilterPurpose
Integration depthFull integration — outbound full-feed payloads and property/listing details entities (with optional Details entity filter). Partial integration — calendar/listing pull surfaces; combines all detail layers and hides the entity filter.
IntegrationMulti-select marketplace columns (for example Uniplaces, Spotahome, Housing Anywhere). All shows every platform in the matrix.
Details entity(Full integration only.) All, Property details, or Listing details to limit rows to one payload layer.

The hint text under the filters explains how to read checkmarks and Req labels for the active depth mode.

Reading the matrix

Pair with other Integration capabilities sections

Amber warning cells mean a partner-required field is missing from Vivin's payload — fill gaps in Property & listing details (booking engine) or on Listings — Channels before publishing. Full pairing matrix: Integration field capabilities section cross-reference.

Each row is a field (and, when Details entity is All, the entity layer is shown in the first column). Each column is an integration platform.

CellMeaning
CheckmarkThe field is supported for at least one sync direction (inbound or outbound) for that platform in the current mode.
Req under a checkThe partner feed marks the field as required when publishing, and the field is present in the integration payload.
Warning icon (Full integration only)The partner requires the field, but it is not yet included in this integration payload — a coverage gap to address in product data or engineering.
Empty cell (Partial integration)Partner-required fields that are outside the partial payload may appear empty; switch to Full integration to see gap warnings and filter by entity.
Coverage gap (warning icon)

On Full integration, an amber warning triangle in a cell means the partner marks that field required for publishing, but the field is not yet present in Vivin’s outbound payload for that platform. Fix the data in Property & listing details (booking engine) (the Full integration pill on the property or unit) or escalate to engineering when the matrix shows a gap you cannot fill from Listings. Empty cells on Partial integration may hide the same issue — switch depth to Full and read the warning row.

Account Settings — Integration field capabilities (full integration), zoomed cell with amber warning icon for a partner-required field missing from the payload

Account Settings — Integration field capabilities (full integration) with platform columns, field rows, checkmarks, and Req labels

The capture above uses Full integration with all platforms and entities visible at desktop width (~1536px). Scroll horizontally when many integrations are selected.

Partial integration view

Pair with other Integration capabilities sections

Partial depth hides entity filters — pair calendar-style surfaces with API Reference — Listings & Availability and API Reference — iCal feeds when full-feed warnings are empty. Full pairing matrix: Integration field capabilities section cross-reference.

Partial integration lists fields supported on calendar-style or partial listing feeds, or flagged as partner-required for that depth. There is no Details entity filter — all layers are combined in one table.

Account Settings — Integration field capabilities (partial integration) matrix and depth filter

Property-only rows

Pair with other Integration capabilities sections

Property-layer rows match the Full integration pill on buildings in Listings — complete them during Onboarding a New Property before linking unit channel IDs. Full pairing matrix: Integration field capabilities section cross-reference.

On Full integration, set Details entity to Property details to limit rows to the property payload layer — the same fields you edit with the Full integration pill on a property in Listings (Profile & copy, Location & geography, Rules & host, and related tabs).

Screenshot freshness

Property entity filter and gap warning cell captures refreshed 2026-06-12 14:10 UTC (VIVIN_DOCS_BASE_URL=http://localhost:5173 VIVIN_DOCS_RECORD_API=$VITE_API_BASE_URL npx tsx tools/capture-settings-integration-field-capability-screenshots.ts).

Account Settings — Integration field capabilities filtered to Property details entity

Listing-only rows

Pair with other Integration capabilities sections

Unit-scoped rows align with Sales → Channel Manager sync actions and API Reference — Full listing feeds outbound payloads. Full pairing matrix: Integration field capabilities section cross-reference.

On Full integration, set Details entity to Listing details to focus on unit-scoped payload fields (the same layer you edit with the Full integration pill on a unit in Listings).

Account Settings — Integration field capabilities filtered to Listing details entity

Walkthrough: switch Integration depth between partial and full, then narrow Details entity to Listing details on the full matrix.

How this relates to other settings

Pair with other Integration capabilities sections

Credentials and calendar cutoffs stay on Integrations — set Tenant categories default for integrations and Emails audiences before high-volume channel imports assign segments automatically. Full pairing matrix: Integration field capabilities section cross-reference.

SurfaceRole
IntegrationsConnect platforms, API keys, markups, and account-wide calendar cutoffs.
Listings → ChannelsLink each unit to external listing IDs.
Booking engine detailsEdit the property/listing payload fields this matrix describes (the Full integration pill).
Sales → Channel ManagerDay-to-day per-listing channel status and sync actions.

The matrix data is maintained in the product codebase; operators cannot edit cells from this screen. If filters produce No matrix rows, widen Integration or Details entity, or switch Integration depth — empty results usually mean no rows match the current filter combination, not that integrations are disconnected.

Integration field capabilities section cross-reference

Use this table when one Integration capabilities topic naturally leads into another Account Settings tab, operator module, workflow, or API guide — each row links to the docs you should read before or after reading the matrix.

| Integration capabilities topic | Pair with these docs | | --------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Who can open it | Integrations, Users and roles | | Filters | Integrations & Distribution, API Reference — partial vs full feeds | | Reading the matrix | Property & listing details (booking engine), Listings — Channels tab | | Partial integration view | API Reference — Listings & Availability, API Reference — iCal feeds | | Property-only rows | Listings module, Onboarding a New Property | | Listing-only rows | Sales → Channel Manager, API Reference — Full listing feeds | | How this relates to other settings | Integrations, Tenant categories, Emails, Handling a Late Payment — Step 1, Notifications — Payment overdue alerts | | Lockout catch-up after password recovery | Resetting a Management User Password, Getting Started — Lockout catch-up, Common Workflows — Lockout catch-up | | Pending manual receipt approval | Integrations, Users and roles — Role permissions (Approve payments), Finance — Pending manual payments | | Reject/revert mistaken receipts | Payment Allocation — Correcting mistaken receipts, Processing a New Booking (duplicate-import triage) | | Notification row-click navigation | /notifications row-click after import field errors | Account Settings — Notification row-click navigation, Common Workflows — Notification row-click navigation, Notifications module — Notification row-click navigation | | Payment alert to receivables triage | payment overdue on partial partner payloads | Account Settings — Payment alert to receivables triage, Common Workflows — Payment alert to receivables triage, Handling a Late Payment — Step 1 | | Confirmation alert triage | Upcoming alerts on field-incomplete imports | Account Settings — Confirmation alert triage, Common Workflows — Confirmation alert triage, Processing a New Booking — Step 5b | | Finance debt receivables triage | Portfolio Top debtors / Debt Aging after settings on this tab | Account Settings — Finance debt receivables triage, Common Workflows — Finance debt receivables triage, Finance module — Finance debt receivables triage | | Finance Income status drill-down | Income → In debt vs Debt Aging after settings on this tab | Account Settings — Finance Income status drill-down, Common Workflows — Finance Income status drill-down, FAQ — Finance Income status drill-down hub | | Cash flow forecast drill-down | Cash flow forecast month bars vs Income segments | Account Settings — Cash flow forecast drill-down, Common Workflows — Cash flow forecast drill-down, FAQ — Cash flow forecast drill-down hub | | Portfolio segmentation by tenant category | Tenant categories — Default for integrations, Bookings — Other filters, Common Workflows — Portfolio segmentation | | API & companion guides | AI usage API (management JWT ledger — partner Bearer keys return 401) |


Pair with other Integration field capabilities guide sections

Related below links this Account Settings tab to modules, workflows, concepts, and escalation paths. Pair Documentation map & escalation with Account Settings hub — Documentation map & escalation; pair Upstream & downstream workflows with Account Settings — Tab cross-reference. Topic-to-section pairing in sections above: Integration field capabilities section cross-reference. Full hub matrix: Account Settings — Section cross-reference.

Documentation map & escalation

Upstream & downstream workflows

Pair with other Integration field capabilities guide sections

Deeper workflow reads

Pair with other Integration field capabilities guide sections

Workflow reads pair with Common Workflows hub subsection index and Workflow cross-reference. Each workflow sub-guide reciprocates with [Deeper workflow reads](./integration-field-capability.md#deeper-workflow-reads) anchors on Account Settings bullets — hub parity: Account Settings hub — Deeper workflow reads. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.

Pair with other Integration field capabilities guide sections
  • Integrations — Platform connections and credentials
  • Tenant categoriesDefault for integration-created tenants before channel imports assign segments automatically
  • Emails — Lifecycle emails fire for imported bookings once field-capability gaps are resolved
  • Preferences — In-app notifications — Account-wide integration or listing alerts after field-capability edits sync to partners
  • Services — Partner imports do not create portal service catalogue entries; configure separately

Operator modules

Pair with other Integration field capabilities guide sections

Deeper concept reads

Pair with other Integration field capabilities guide sections

API & companion guides

Pair with other Integration field capabilities guide sections

Lockout catch-up after password recovery

Pair with other Integration field capabilities guide sections

Operational backlog after sign-in recovery pairs with Resetting a Management User Password — Step 3 before you resume partner field triage on this matrix. Hub parity: Common Workflows — Lockout catch-up after password recovery. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.

Pending manual receipt approval

Pair with other Integration field capabilities guide sections

Receipt approval pairs with Integrations channel imports and Users and roles (Approve payments permission). Hub parity: Common Workflows — Pending manual receipt approval. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.

Reject/revert mistaken receipts

Pair with other Integration field capabilities guide sections

Portfolio segmentation by tenant category

Pair with other Integration field capabilities guide sections

Notification row-click navigation

Pair with other Integration field capability guide sections

Partner field requirements do not change /notifications routing — row-click import alerts into Bookings before fixing missing payload fields on this reference page. Hub parity: Account Settings — Notification row-click navigation. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.

Payment alert to receivables triage

Pair with other Integration field capability guide sections

Incomplete partner payloads may delay bookings but do not replace payment overdue triage — row-click alerts on live reservations first. Hub parity: Account Settings — Payment alert to receivables triage. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.

Confirmation alert triage

Pair with other Integration field capability guide sections

Field-capability gaps on imports surface as Upcoming Booking created alerts — finish confirmation Steps 5b / 6 before bulk field-mapping review. Hub parity: Account Settings — Confirmation alert triage. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.

Finance debt receivables triage

Pair with other Integration field capabilities guide sections

Required partner fields do not change Debt Aging buckets — triage receivables on Finance → Overview after import errors delay settlement. Hub parity: Account Settings — Finance debt receivables triage. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.

Handling a Late Payment collections

Pair with other Integration field capabilities guide sections

Required partner fields do not change Debt Aging buckets — triage receivables on Finance → Overview after import errors delay settlement Hub parity: Account Settings — Handling a Late Payment collections. Full pairing matrix: Integration field capability section cross-reference · Account Settings — Section cross-reference.

Finance Income status drill-down

Pair with other Integration field capabilities guide sections

Field-capability gaps do not explain Income segment drift — open segment drill-down when imports leave charges In debt. Hub parity: Account Settings — Finance Income status drill-down. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.

Cash flow forecast drill-down

Pair with other Integration field capabilities guide sections

Partner feed delays may skew Cash flow forecast month totals — confirm All payments lines after integration-check cron recovers. Hub parity: Account Settings — Cash flow forecast drill-down. Full pairing matrix: Integration field capabilities section cross-reference · Account Settings — Section cross-reference.

Key glossary terms

Pair with other Integration field capabilities guide sections

Module documentation hubs

Pair with other Integration field capabilities guide sections
  • Integration field capabilities — Read-only partner payload matrix (this page)
  • Utilities module — Bills Included ceiling model, Connections, AI bill upload, and tenant overage charges on payment plans (hub)
  • Operations module — Maintenance tickets, cash flows, check-in/out coordination, Draft ticket queues, and linked cash flows (hub)
  • Dashboard module — Post-login Today, Total debt, Vacant Units, and forecast KPI snapshot with bell notification triage (hub)
  • Analytics module — Month-range portfolio KPI charts (Overview, Revenue, Occupancy, ADR, RevPAR, Maintenance) with rankings and heatmaps (hub)
  • Listings module — Property wizard, Channels tab, Archived inventory, and unit management (hub)
  • Properties workspace — Legacy /properties URL redirects into Listings (hub)
  • Finance module — Portfolio ledgers (Overview, Income, Contract Values, Transactions, Payouts, Deposits) with payment approval and deposit settlement (hub)
  • Tenants module — Tenant directory, profile sidebars, With Debt segmentation, and table expand for linked bookings (hub)
  • Sales module — Portfolio availability, monthly rent editing, and channel manager connections (hub)
  • Inbox module — Portfolio-wide WhatsApp workspace with Dashboard bell Inbox sub-tab deep links (hub)
  • Notifications module — Full /notifications history with search, filters, and row-click navigation (hub)
  • AI Chat module — Vivin-internal AI Assistant using Landlord MCP tools for portfolio Q&A (hub)
  • Audit module — Portfolio-wide Manual Blocks and Discounts contract-value review (hub)
  • Account Settings — Workspace-wide financial policies, templates, integrations, and operational defaults (hub)
  • API Reference hub — Partner HTTP contracts, Swagger onboarding, and partial vs full feeds (hub)