portierX connects to an Interflex IF-6040 over the OpenAPI REST interface your IT publishes. Setting it up needs the Organisation Admin or Access Manager role in portierX and a service account on the IF-6040, so it is done together with IT. It starts under Integrations, on the Available tab, with the INTERFLEX tile.
Also called: Interflex, IF-6040, INTERFLEX, badge, zone, access profile.
Your IT publishes the IF-6040's OpenAPI interface so that portierX reaches it over HTTPS, usually behind a protection layer (Cloudflare Access, VPN or fixed headers).
The base URL of the interface, for example https://if6040.example.de/api, and the sign-in path on it that issues the token, for example /Login. IT names both; portierX does not guess the path.
A service account on the IF-6040 with username and password, holding the rights and licences for what portierX reads and writes.
Where needed, the sign-in language, for example en-US, and the server certificate as PEM when the IF-6040's certificate is not publicly trusted.
The headers the protection layer in front of the interface requires.
The Organisation Admin or Access Manager role in portierX.
Open Integrations and stay on Available.
On the INTERFLEX tile, click Configure.
Enter a name under Connection name.
Enter the base URL under OpenAPI base URL and the sign-in path under Sign-in path.
Enter the service account under Service account username and Service account password.
Where needed, enter the language under Sign-in language and paste the PEM certificate under Server certificate (CA). Otherwise leave both empty.
Under Network protection, choose how portierX reaches the interface and enter its headers.
Click Test connection. portierX signs in, discards the token and writes nothing.
After a passing test, click Activate.
portierX encrypts the username and password before storing them. After activation the first run starts, and the connection's page opens under Connected with the tabs Summary, Configuration, Sync Log and Notifications. How to read the Summary is on What the connection screen is telling you.
On every run portierX reads from the IF-6040 the persons, the badges, the zones, the access profiles and the names of the time profiles. A person is matched by personnel number and linked to an existing person in portierX by email address where that address is unique. A badge becomes an access credential held by its person. A zone becomes an access point with no space; you place it in the space it serves, say the Serverraum in Werk Nord. Each badge is linked to the access points of the zones it opens, through its person's profiles and through direct grants.
An access profile becomes a people group at its first read, with everyone who holds it. From then on the group belongs to portierX: a change to its name or members made in the IF-6040 is recorded as drift and not applied. Each zone records which profiles reach it. Door events, time recording and visitor data are never read.
portierX writes to the IF-6040 what changes about a person and their badges in portierX: a person's first name, last name and email address; a badge handed to a person gains the link to that person in the IF-6040; a badge taken back has that link ended there, and a badge reported lost is blocked as well; a badge linked to or unlinked from an access point that is an IF-6040 zone gains or loses, in the IF-6040, its person's personal permission on that zone. Every push is listed on Sync Log under Push.
Not written back are a zone's name, a badge's label, the zones a profile contains and the members of a people group taken over from a profile. The Auto push switch on the Configuration tab governs these pushes; what it means is on the connection screen page.
The Security card on the Configuration tab has three blocks, each saved on its own; a field left empty keeps the stored value.
Under Base URL and Sign-in path, change the address; Save address applies it.
Under Username the service account is shown masked. A password under New password is applied with Rotate password; Test connection signs in as a check.
Server certificate shows Set or None. A certificate under Paste the new PEM certificate is applied with Replace certificate.
After each save portierX signs in as a check and says whether it succeeded. Only the Organisation Admin and the Access Manager edit the fields.
The Notifications tab holds this connection's one reminder, An Interflex request is not activated: a request approved in portierX that the responsible group has not activated in the IF-6040. Under When, enter at Still not activated after the days after approval; under Who gets an email, choose at Email everyone with a role, the Responsible person of the place or the company's Responsible person. The defaults are seven days and everyone with the Security Monitor role. Save applies the setting; without the right to configure integrations the form is read-only.
After activation the first run starts at once; after that portierX runs on its schedule and from the button on Summary.
Every run is listed on Sync Log as Success, Partial Success, Failed or Skipped. Skipped means another run of the same connection was in progress.
Summary counts this connection's people, spaces, access credentials, access points and people groups.
The log names, for every run, who was skipped: persons without a personnel number (the first 25 by name, the rest as a count), persons that could not be linked by email, possible duplicates, zones without a space, badges without a known holder and records the IF-6040 stopped listing.
When a run breaks off, the row names the step; what was written before it stays.
The address begins with https. portierX refuses an address without it.
The sign-in path is required; portierX assumes none.
A person without a personnel number in the IF-6040 is skipped and named. portierX never matches by name.
A zone arrives as an access point with no space. You assign the space.
A people group taken over from a profile belongs to portierX. Changes to the profile in the IF-6040 are recorded, not applied; changes to the members in portierX are not written to the IF-6040.
A run removes nothing. What the IF-6040 stopped listing is named on Sync Log.
A push the IF-6040 refuses for want of a right or licence is recorded and not repeated.
Door events, time recording and visitor data are never read.
The connection is not removed from its page.
The Organisation Admin and the Access Manager read the connection's settings; the same two change them.
Connected systems at a glance
