A connection is the bridge between portierX and one system you run or use: an access control system, Microsoft Entra ID, the files of your HR system, or a master key plan from a file. The Organisation Admin and the Access Manager see every connection under Integrations. Either of them connects an access control system; the Organisation Admin connects Microsoft Entra ID, the HR file and a master key plan from a file.
Also called: integration, link, interface.
Integrations has two tabs, each with its count. Available shows one tile per system portierX can connect; Connected shows one tile per connection that exists, drafts included. The Categories open with All Applications, and Search applications... finds a tile by name, description or keyword.
On a tile under Available, See Details opens the system's description on the Information tab; Configure opens the Connect tab straight away. On a tile under Connected, See Details opens the connection. While no connection exists, Add Integration leads to Available.
An access control system, which is SALTO, dormakaba MATRIX, ASSA ABLOY eCLIQ or Interflex IF-6040, is reached by portierX over the system's own interface. portierX reads what the system holds on a schedule and writes back what changes in portierX; which data goes which way is on the page of each system. When Nordwerk Industries connects its SALTO system, the doors of Werk Nord become access points, its people become people and its cards become access credentials.
Microsoft Entra ID links portierX to your IT's directory, once for sign-in (single sign-on over SAML) and once for provisioning people and groups (SCIM). portierX calls no system here; the browser and Entra ID call portierX. These connections therefore have no network protection and no connection test, and Activate completes the setup on its own. The SCIM connection needs an active single sign-on connection with a verified domain.
The HR file is a folder portierX assigns to your organisation. Your HR system drops its exports there, and every morning portierX reads what arrived. An organisation has one such source; it has no network protection, no connection test and no draft, and only an Organisation Admin creates it.
A master key plan reaches portierX as the manufacturer's XML export: ABUS, CES, DOM, dormakaba, EVVA, KESO ASSA ABLOY, WILKA, WINKHAUS or portier's own XML format. The connection is made by uploading the file with Create Integration, and only an Organisation Admin uploads.
The Connect tab opens with the system's own guide, what it needs and what portierX exchanges with it, then the form. The fields come from the system: a name for the connection, the address of its interface, the credential and, depending on the system, a certificate or further settings. Required fields are marked. For an access control system, Network protection follows the form.
Test connection registers the connection as a draft and checks that portierX reaches the system with these settings and that the system accepts the credential. After a passing test the button reads Activate. portierX checks the connection a second time, sets it active, starts the first run and opens its page under Connected. Save as draft keeps the settings without a check. Cancel closes the wizard.
When a step fails, the form names the reason.
The address cannot be reached.
Credentials rejected.
That name is already in use. Choose a different name.
Complete the required fields before saving.
Couldn't secure the secret. Contact support.
Network protection tells portierX how it reaches the interface of an access control system. Public: the interface is reachable over HTTPS, and your firewall lets portierX through. Cloudflare Access: the interface sits behind a Cloudflare Access application, and portierX signs in with a service token whose values go under CF-Access-Client-Id and CF-Access-Client-Secret. VPN: a site-to-site VPN or ExpressRoute between your network and portierX, with nothing more to enter. Custom headers: the interface expects one or more fixed headers, entered with Add header as Header name and Header value.
On the connection's page the same choice is the Protection Layer card on the Configuration tab: Protection Type, the guide for the chosen kind, its fields and Save. A Cloudflare secret left empty keeps the stored one on Save, as long as the client id is unchanged. eCLIQ offers Public only.
The Security card on the Configuration tab shows the URL and, under Last Updated, the last change. Update Details opens the dialog for address and secret, and Save applies both at once. A running synchronisation may break off for a moment, and every change is recorded in the audit log. eCLIQ replaces its certificate here, and Interflex changes address, password and server certificate in blocks of its own; the page of each system describes it.
A draft is a connection that is registered and not activated. It comes from Save as draft or from a connection test that did not pass. The draft counts under Connected and carries the banner Draft, not yet active. with Continue setup. A draft does not sync. Continue setup opens the form with the stored settings; the secret stays empty and the name is fixed. Whoever changes the address or the credential enters the secret again: Re-enter the secret to save these changes.
An Organisation Admin or an Access Manager connects an access control system. Only an Organisation Admin connects Microsoft Entra ID, the HR file and a master key plan from a file.
A connection's name is unique in the organisation and fixed once the connection exists.
A connection becomes active only when its own check passes on Activate.
portierX encrypts secrets, passwords and certificates before storing them. No screen shows them again.
Network protection applies to access control systems. Microsoft Entra ID and the HR file have none; eCLIQ has Public only.
A draft does not sync and counts under Connected.
A connection to an access control system is not removed from its page.
The scheduled run is set for the installation, not per connection. What a connection's page shows is under Related.
