Integration field capabilities

Ask AI Chat “Where do I open the Integration capabilities tab under Account Settings System (the System group next to Integrations — English tab label Integration capabilities at /settings/integrationFieldCapability — not the Integrations credentials tab, and not Listings Channels) to view the read-only partner field matrix for required versus supported marketplace payload fields?” — then open Settings → System → Integrations (ai-chat-product-context-integration-field-capability-reply.png, ai-chat-product-context-integration-field-capability-flow.mp4). Account Settings no longer lists a separate Integration capabilities sidebar item; the old /settings/integrationFieldCapability bookmark opens Integrations, where partner field coverage lives on the connection cards. The assistant may still say Settings → System → Integration capabilities or point you to a matrix inside a marketplace card; follow Settings → System → Integrations instead. Same grounding external MCP clients get from get-vivin-context-platform. Distinct from per-unit links on Listings → Channels.

AI Assistant — where to open Integration capabilities for the partner field matrix

Walkthrough: ask AI Assistant where to open Integration capabilities for the partner field matrix, then open Settings → System → Integrations (even if the reply names a separate Integration capabilities tab).

The Integration capabilities reference (bookmark /settings/integrationFieldCapability) explains the read-only partner field matrix for which property and listing (unit) detail fields from the booking-engine payload editor are supported per marketplace, and whether a partner marks a field as required when publishing. In the current Account Settings sidebar that matrix is reached via Integrations (connection-card coverage), not a standalone System tab.

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.

Finding your way in this guide

Use Filters to narrow by integration, then read Reading the matrix for required vs supported fields. Credentials still live on Integrations — see How this relates to other settings. Habit-specific shortcuts live under Related below.

Direct access

Open Account Settings → System → Integrations at platform.vivin.app/settings/integrations (partner field coverage on connection cards). The older bookmark /settings/integrationFieldCapability opens the same Integrations tab. Requires the integration-related settings permission (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). Hub: Recommended setup order.

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.

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.

Three controls narrow the matrix:

Filter	Purpose
Integration depth	Full 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.
Integration	Multi-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.

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.

Cell	Meaning
Checkmark	The field is supported for at least one sync direction (inbound or outbound) for that platform in the current mode.
Req under a check	The 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.

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.

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).

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.

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.

Surface	Role
Integrations	Connect platforms, API keys, markups, and account-wide calendar cutoffs.
Listings → Channels	Link each unit to external listing IDs.
Booking engine details	Edit the property/listing payload fields this matrix describes (the Full integration pill).
Sales → Channel Manager	Day-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.