External integrations

Manage connections to external systems and webhooks.

External Integrations

The External Integrations screen is where your IT administrator controls whether Product Fruits — the in-app guidance service that powers interactive walkthroughs, onboarding tours, and help hints inside Priverion — is active for your organisation. It is a deliberately focused screen: one card, two status fields, one action. But the decision it governs has a platform-wide effect: when Product Fruits is switched on here, every user in your organisation sees the guided help experience; when it is switched off, those features disappear for everyone simultaneously. This screen belongs to the IT Settings section of Priverion, which is the control centre for all organisation-wide technical configuration.

How to open it

In the left-hand navigation, expand the IT Settings section, then click External Integrations. The screen loads immediately — there are no sub-tabs to navigate.

Who can access it: You need at least one of two read permissions to reach this screen. If you hold neither, navigating to the page will show a "403 Forbidden" error instead of the content. If you can see the screen but the Edit button appears greyed-out, your account has read access but not edit access — contact your system administrator to request the edit permission if you need to make changes.

What you see

When you arrive at External Integrations, the main content area is framed by the IT Settings sidebar navigation on the left, with the External Integrations item highlighted as your current location. At the top of the content area, a breadcrumb trail shows your path: IT Settings (a clickable link back to the IT Settings home), then External Integrations, then Product Fruits Help as the final, non-clickable label. Embedded in the breadcrumb are small left and right arrow buttons that let you page between different integration categories if your organisation has more than one configured.

Below the breadcrumb sits a single white card. Its header reads Product Fruits Help in blue semibold text, with an Edit button in the top-right corner of the card. The card body contains exactly two labelled rows — Status and Allow the use — each showing a label on the left and its current value on the right. These two rows give you an instant, read-only summary of the integration's current state. No charts, no tables — just the two facts you need to know.

Working with this screen

Enabling Product Fruits for the first time

If your organisation has just set up Priverion and you want new compliance staff to benefit from the built-in guided tours and onboarding hints, this is where you start. When the integration has never been configured, both rows will show their default values: Status: Inactive and Allow the use: No.

On the Product Fruits Help card, click the Edit button in the top-right corner. You are taken to the edit form, which opens as a new page — not a pop-up. You will see two toggle switches stacked vertically on the left side of the form.
Click the Integration Enabled toggle. It turns light blue to indicate the integration is now switched on at the platform level. This is the master switch that makes Product Fruits available inside your Priverion environment.
Click the Allow the use toggle. It also turns light blue. This second switch controls whether the guidance features — walkthroughs, hint bubbles, onboarding checklists, and help pop-ups — are actually visible to your users. Both toggles must be on before anyone in your organisation sees the Product Fruits experience.
Click Save. A green success notification confirms the change has been saved. You can click the back arrow at the top of the form to return to the read-only view, which will now show Status: Activated and Allow the use: Yes.

From this point forward, every user in your organisation will see the in-app guidance features the next time they load or reload the application.

Disabling Product Fruits to meet a data governance or security requirement

Some organisations need to ensure that no third-party services are active in their compliance platform — for example, if your information security policy prohibits third-party in-app analytics, or if a legal review requires you to turn off external integrations temporarily.

Open the External Integrations screen. The card will show Status: Activated and Allow the use: Yes.
Click Edit. On the edit form, click the Integration Enabled toggle to turn it off. It turns grey.
Notice that the Allow the use toggle also switches off automatically and becomes unclickable. This is by design: it is not possible to allow users to interact with Product Fruits if the integration itself is disabled. The system enforces this dependency for you.
Click Save. Both rows on the read-only card will now show Inactive and No respectively. Product Fruits guidance features will disappear from the application for all users immediately after saving — no further action is needed.

Suspending user-facing guidance while keeping the integration active

There is a third, more nuanced state: the integration can be on at the platform level while user-facing features are hidden. This is useful when, for example, an IT administrator wants to review new Product Fruits walkthrough content before it goes live, or when you need to temporarily pause the experience without fully disconnecting the service.

Click Edit on the Product Fruits Help card.
Leave the Integration Enabled toggle in the on (blue) position.
Click the Allow the use toggle to switch it off (grey). This hides the guidance features from all users without disconnecting the integration itself.
Click Save. The read-only card will now show Status: Activated and Allow the use: No — meaning the service is connected, but users cannot see it yet.

When you are ready to expose the guidance features again, return to this form, switch Allow the use back on, and save.

Reviewing the integration status during a compliance audit

If you are a DPO or auditor checking whether third-party in-app services are active in the organisation's DPMS, you can get the answer from this screen in seconds — no edit permission required.

Navigate to IT Settings → External Integrations.
Read the two rows on the Product Fruits Help card:
Status: Activated means the Product Fruits service is connected to your Priverion instance.
Status: Inactive means it is not.
Allow the use: Yes means users can see and interact with the guidance features.
Allow the use: No means they cannot, regardless of the integration status.
If you need to document this for an audit, note both values directly from the screen. If a change needs to be made, you will need to involve a colleague who holds the edit permission for this area.

Field reference

The two data rows on the read-only card, and the two toggle switches on the edit form, all refer to the same underlying configuration values:

Status / Integration Enabled — Controls whether the Product Fruits service is connected to your Priverion environment at the platform level. When active, displays as Activated on the read-only card; when inactive, displays as Inactive. This is the parent setting. Turning it off automatically forces the second setting to off as well. If the integration has never been configured, this defaults to Inactive.
Allow the use — Controls whether end users across the organisation can actually see and interact with Product Fruits walkthroughs, hints, tours, and help widgets. Displays as Yes or No on the read-only card. This toggle is only clickable on the edit form when Integration Enabled is switched on. If the integration has never been configured, this defaults to No.

How this connects to the rest of DPMS

The Product Fruits configuration set on this screen has a global, organisation-wide effect. There is no per-user, per-department, or per-role control for this feature — it is a single on/off switch for the entire organisation. Any change you save here takes effect for every active user session.

When both Integration Enabled and Allow the use are on, the in-app guidance layer becomes available throughout the entire DPMS interface — not just on one screen. This means new compliance officers, privacy coordinators, and data protection administrators will see contextual help, onboarding tours, and interactive walkthroughs wherever Product Fruits content has been configured. When either setting is off, those features are absent for all users simultaneously, including anyone who might be in the middle of an onboarding tour.

The change takes effect immediately after saving — there is no delay, no deployment required, and no need to restart the application. However, users who are already logged in may need to reload the application in their browser to see the effect, since their current session may have loaded the previous configuration on startup.

This screen is reached through IT Settings, and there are no other parts of the application that link directly into it. If you need to make a change here as part of a broader IT configuration review, a natural next step after finishing is to check the other categories in the IT Settings sidebar to ensure the rest of your organisation's technical configuration is also up to date.

Tips & common pitfalls

Heads up: Turning off Integration Enabled automatically switches off Allow the use with no warning and no undo step. If you turn the integration back on later, you will also need to re-enable Allow the use separately — it does not restore itself automatically.

Heads up: The Edit button is visible to users who only have read access, but it cannot be clicked. There is no tooltip explaining why. If you see a greyed-out Edit button, ask your IT administrator to check your role permissions and add the edit permission for this area if appropriate.

There is no confirmation dialog when you click the back arrow on the edit form. If you made a change to one of the toggles and then click the back arrow instead of saving, your changes are silently discarded. The configuration remains unchanged. Always click Save before navigating away.
This is an organisation-wide switch, not a per-user setting. Disabling Product Fruits removes the guidance experience for every single user in your organisation at once — including DPOs, privacy coordinators, and anyone who is actively mid-tour. If you only want to hide guidance from users temporarily while you test something, use the Allow the use toggle rather than the Integration Enabled toggle.
Users already logged in may need to reload their browser. Saving a change here updates the global application configuration immediately, but users whose sessions started before the change was made may not see the new state until they reload the page.
If neither field has ever been set, both default to off. A freshly created organisation account will show Inactive and No until an IT administrator explicitly visits this screen and enables the integration. Product Fruits does not activate itself automatically.

External integrations