> For the complete documentation index, see [llms.txt](https://help.peoplevine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.peoplevine.com/products/integrations-overview/setup-opera-ohip.md). # Opera Cloud (OHIP) — Operator Manual ### Before you begin (Prerequisites) * **Peoplevine permissions**: You must be an **Administrator** or **Supervisor** to configure integration settings in the Control Panel. See: [How to Manage Users and Permissions](/products/control-panel-overview/admin-overview/manage-roles-permissions.md). * **Opera Cloud Foundation** subscription. * **Hotel chain information** gathered in advance: * Opera Cloud Admin contact (name and email) * Opera Cloud version * Property Code (displayed in Opera Cloud top-right corner) * Chain Code (found via Select Location > Hub search) * Opera Cloud URL for your property * **Integration partner user** registered with OHIP (generates Interface ID and Interface Key). See the Connect guide for the full registration process, including WSACCESS role assignment. * **Firewall whitelisting** — if your property has a firewall, whitelist Peoplevine's IP addresses: * Virtual IP: `40.70.147.2` * Outbound IPs: `13.68.114.115`, `13.68.114.136`, `40.70.63.81` * **Client ID and Client Secret** from the Oracle Developer Portal (provided by Peoplevine support). * **Business Events and External Systems** configured in Oracle for your property. See the Connect guide for setup steps. > For full Oracle-side setup (partner registration, WSACCESS role, business event configuration, external system setup, firewall whitelisting, and membership type creation in Opera), see [Connect Oracle OHIP and Peoplevine](https://docs.peoplevine.com/peoplevine-docs/peoplevine-connect) in Peoplevine Connect. The steps below cover the Peoplevine Control Panel side only. *** ### Setup 1. Contact your account manager or with your integration username. Peoplevine will create a connection to the production environment and notify you when it is ready. 2. Navigate to [**AUTOMATE > Integrated Platforms**](https://control.peoplevine.com/admin_authenticate.aspx). > **Note (Pro Dash):** Same path — **AUTOMATE > Integrated Platforms**. 3. Under **Property Management Systems (PMS)**, select **Oracle Opera Hospitality**. 4. In the **Connection Type** section, choose **Cloud/Modern via OHIP**. 5. Select the **Environment**: **Production** or **Non-Production (UAT)**. 6. Enter the following credentials: | Field | What to enter | | ---------------------- | --------------------------------------------------------------------------------------------------------- | | **Interface ID** | From OHIP partner registration (also called Integration User ID) | | **Interface Key** | From OHIP partner registration (also called Integration Password) — enter in the Interface Password field | | **External System ID** | Enter `PEOPLEVINE` | | **Hotel ID** | Your Property Code | | **Region** | Must match the region set for your environment | | **Client ID** | From Oracle Developer Portal (provided by Peoplevine support) | | **Client Secret** | From Oracle Developer Portal (provided by Peoplevine support) | 7. Leave **Gateway URL** blank — it is auto-generated after connection. 8. (Optional) In **Omit Customer**, enter any membership or profile to exclude from sync. 9. In **Attributes to Sync to Profile**, enter the attributes you want synced to Opera (one per line). These sync as a combined note to the profile. 10. Use the checkboxes to select which notes to sync. 11. In **Select Membership Program to Automatically Enroll into**, choose a temporary membership for non-member hotel guests (optional — see Front of House section below). 12. Enable **Sync both member and non-member reservations** if you want all Opera reservation data. Leave unchecked to sync member data only. 13. Click **CONNECT**. *** ### Day-to-Day: Front of House #### Member recognition at check-in Members synced to Opera are recognised during hotel check-in with their membership tier and preferences. Peoplevine pushes membership status, tier, notes, and profile attributes to Opera, so the front desk sees this information without leaving Opera Cloud. #### Temporary membership for hotel guests Non-member hotel guests can be automatically enrolled in a temporary membership on check-in, giving them access to club amenities during their stay. The temporary membership expires on check-out. To use this feature: 1. Navigate to **MEMBERS > Memberships > Manage Membership Programs** (Standard Dash) or **REWARD > Memberships > Membership Programs** (Pro Dash), then create a new program and select the **Temp Guest** type. 2. On the OHIP integration settings page (see Setup above), select this program in **Select Membership Program to Automatically Enroll into**. #### Reservations Reservation data flows from Opera to Peoplevine via Business Events. When a reservation is created, checked in, checked out, or cancelled in Opera, the event syncs to the member's Peoplevine CRM profile. Reservation metadata (such as food preferences or spa treatments) is also captured. > **Important**: Reservation sync requires Business Events configured in Oracle. Without them, reservation data will not flow to Peoplevine. See the Connect guide for setup steps. #### Room types Room types from Opera are automatically configured as schedulers in Peoplevine. *** ### Day-to-Day: Finance #### How PMS payments appear in Peoplevine Opera OHIP supports closing a payment to Peoplevine. PMS payments from Opera are displayed in Peoplevine transactions. Members can also pay via card on file through OHIP using the **Auto** tender type. #### Processor routing PMS charges route to the **PMS** processor slot. > For details on configuring processor slots, see: [How to Link a Payment Processor](/products/control-panel-overview/admin-overview/link-payment-processor.md). *** ### What Gets Synced | Data | Direction | Notes | | --------------------------------------------- | ------------------ | ------------------------------------------------------------------------------------------ | | Member profiles (name, email, phone, address) | Peoplevine → Opera | On creation and updates. Field mapping in Connect guide. | | Membership status and tier | Peoplevine → Opera | Uses SKU-to-Membership Type mapping — SKUs must match exactly | | Member notes and profile attributes | Peoplevine → Opera | Configurable — select which notes and attributes sync in integration settings | | Reservations | Opera → Peoplevine | Requires Business Events configured in Oracle (check-in, check-out, cancel) | | Reservation metadata | Opera → Peoplevine | Food preferences, spa treatments, etc. | | Room types | Opera → Peoplevine | Auto-configured as schedulers in Peoplevine | | PMS payments | Opera → Peoplevine | Displayed in Peoplevine. Members can also pay via card on file through OHIP (Auto tender). | | Temporary membership | Peoplevine → Opera | Non-member hotel guests auto-enrolled on check-in, expires on check-out (if configured) | #### Profile matching Profiles are matched using an `extended_id` — a combination of the first letter of the first name, the last name, and either the email address or phone number. This identifier is enforced bi-directionally: if the `extended_id` matches an existing profile, the profile name will not be updated. Ensure last names are entered correctly during profile creation so synchronisation can occur successfully. #### Membership assignment Peoplevine maps memberships to Opera using the membership SKU: * The membership SKU in Peoplevine must match the Membership Type in Opera exactly. * Create a `PPV` Membership Type in Opera as a catch-all for memberships without a matching SKU. * Memberships without a corresponding SKU and without a `PPV` type will sync the profile without a membership attached. *** ### Troubleshooting **Members not syncing to Opera:** Verify your Interface ID and Interface Key are correct. Confirm the integration user has the WSACCESS role assigned. Check that the External System code `PEOPLEVINE` is configured in Opera. **Reservations not appearing in Peoplevine:** Business Events are not configured in Oracle. Verify that the correct modules (Reservation, Cashiering, Profile) and events (Cancel, Check-in, Check-out) are set up and associated with the PEOPLEVINE external system. **Membership type showing as PPV instead of the correct tier:** The membership SKU in Peoplevine does not match a Membership Type in Opera. Add the matching Membership Type in Opera, or verify the SKU is set correctly on the Peoplevine membership program. **Duplicate profiles in Opera:** Profiles are matched using the `extended_id` (first letter of first name + last name + email or phone). If a member's last name was entered incorrectly during creation, the profile may not match. **Connected ID was modified — data stopped syncing:** If the Connected ID on a profile is changed, the system treats it as a different user and sync breaks. Do not modify Connected IDs after initial sync. **No data syncing for any members:** Verify that all login information is accurate on the OHIP integration settings page. *** ### Best Practice * **Set membership SKUs to match Opera Membership Types exactly** — Peoplevine uses the SKU to map members to the correct Membership Type in Opera. Create a `PPV` Membership Type in Opera as a catch-all for memberships without a matching SKU. * **Configure all relevant Business Events in Oracle** — at minimum, set up Reservation (Cancel, Check-in, Check-out) and Profile modules. Without these, reservation data will not flow to Peoplevine. * **Multi-property chains require separate External System codes** — when connecting more than one property, configure two separate external system codes in Opera for each Peoplevine location, along with separate external databases. * **Test with a single member first** — sync one member and verify their profile, membership type, and notes appear correctly in Opera before running a full member sync. *Last updated: 2026-05-24* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.peoplevine.com/products/integrations-overview/setup-opera-ohip.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.