Integrations

The Integrations screen manages the connections that link Scrivio to external systems. It has two tabs: Certificates for the digital certificates used for secure billing and sending (VECOZO, UZI, Zorgmail), and Zivver for the SMTP credentials used to send letters securely through Zivver. The screen is intended for the organization administrator.

This screen replaces the outdated "Integrations" page from the old admin guide.

Overview

Route	/organization/integrations (open a specific tab with ?tab=certificates or ?tab=zivver)
Audience	Organization administrator
Required permission	integrations.manage

Two tabs sit at the top of the screen — Certificates and Zivver. The screen opens on the Certificates tab by default. The Zivver integration is only available with a FULL license.

How it works

This screen doesn't manage Scrivio data, but the trust relationship with external systems: the certificates that prove your organization's identity and the channel through which Scrivio sends secure letters. A wrong or expired certificate doesn't break this screen, but rather the processes that rely on it (billing, insurance checks, sending). That's why it helps to understand what each connection is for.

Certificates: who you authenticate to, and for what

A certificate is a digital proof of identity Scrivio uses to authenticate to an external party on behalf of your organization. Each type authenticates for its own chain:

Type	Authenticates to	Used for
VECOZO system certificate	VECOZO	Checking insurance eligibility (COV) and exchanging claims with health insurers.
UZI server certificate	SBV-Z and other healthcare integrations	Proving a valid care-provider identity on secure connections in the healthcare infrastructure.
Zorgmail	Zorgmail	Secure messaging in healthcare.

The certificate itself is a PKCS#12 file (.p12/.pfx) that holds both the key and its protection; when uploading you supply the passphrase the file is protected with. Scrivio uses this file to establish the connection on your behalf; Test connection checks whether that chain actually works.

Expiry lifecycle and the downstream break

Each certificate has an expiry date and moves through three statuses. The status isn't a cosmetic label — it predicts whether the chains above keep working:

Status	Meaning	Effect
Valid	The certificate is usable.	Billing, insurance checks, and sending work normally.
Expiring soon	The expiry date is approaching.	Still usable, but this is your cue to Replace it in time — before it expires.
Expired	The expiry date has passed.	The dependent processes (e.g. billing or a COV check via VECOZO) fail until a valid certificate is uploaded.

Because an expired certificate halts dependent processes without anything appearing "broken" on this screen, Expiring soon is meant as a generous warning margin: replace the certificate during that window instead of waiting for errors to surface in, say, the billing process.

Zivver as a sending channel

The Zivver tab is not a certificate but an SMTP channel: the username and password of your Zivver account that Scrivio uses to send letters securely. This configuration is the only channel for Zivver delivery — if you delete the configuration, letters can no longer be sent through Zivver. So only delete the configuration if you deliberately want to switch this channel off.

License and secret handling

The Zivver integration is subject to FULL-license gating: without that license the tab is visible but the form is unavailable. The Certificates tab is independent of this gating.

Secrets are handled write-only. The certificate passphrase and the Zivver password are stored securely and then never shown again: the form clears them after saving or deleting. When making a change you therefore always re-enter the password — Scrivio cannot pre-fill the existing secret for you.

Open the Certificates tab

Click the Certificates tab (or open the screen via /organization/integrations?tab=certificates). You see a list of your organization's uploaded certificates, each row showing the type, status, expiry date, and when and by whom the certificate was uploaded.

The status indicates whether a certificate is still usable:

Status	Meaning
Valid	The certificate is valid and usable.
Expiring soon	The certificate expires shortly; replace it in time.
Expired	The certificate has expired and must be replaced.

Open the Zivver tab

Click the Zivver tab (or open the screen via /organization/integrations?tab=zivver). Here you configure the SMTP credentials of your Zivver account that Scrivio uses to send letters securely.

Zivver is only available with a FULL license. Without it the tab shows a notice and the form is unavailable. Contact us to upgrade your subscription.

Configure a certificate

On the Certificates tab, click + New in the top right to upload a certificate. A dialog opens where you choose the type, select the certificate file, and enter the passphrase.

Field	Required	Description
Certificate type	Yes	UZI server certificate, VECOZO system certificate, or Zorgmail. When replacing an existing certificate the type is fixed.
Certificate file	Yes	A PKCS#12 file with the extension .p12 or .pfx. Drag the file onto the upload zone or click to browse.
Passphrase	Yes	The passphrase the certificate file is protected with.

For VECOZO: export the certificate from your browser as a PKCS#12 file (.p12) with a passphrase.

Click Upload to save the certificate. After uploading you manage the certificate with the actions in the list:

• Test connection — checks whether the certificate establishes a working connection.
• Replace — opens the same upload dialog to refresh the certificate file (the type stays fixed).
• Delete — removes the certificate after confirmation. This cannot be undone.

Configure Zivver

On the Zivver tab, enter the SMTP credentials of your Zivver account. The host and port are pre-filled with the Zivver defaults.

Field	Required	Description
SMTP host	No	The Zivver SMTP host. Defaults to smtp.zivver.com.
Port	No	The SMTP port. Defaults to 587.
Username	Yes	The Zivver-issued username (a UUID).
Password	Yes	The Zivver-issued password. It is stored securely and never shown; re-enter it to save the configuration.

Click Save to store the configuration. Two further actions then become available:

• Test connection — checks whether Scrivio can establish a connection to Zivver with the entered credentials.
• Delete — removes the Zivver configuration after confirmation. Letters can no longer be sent through Zivver afterwards.

For security, the password is cleared from the form after saving or deleting and is never visible.