This path is for the Organisation Admin who connects portierX to the systems IT runs: access control systems, Microsoft Entra ID for sign-in and provisioning, and the HR file. The job is to set those connections up, keep them running and know what each one brings into portierX. portier's introduction team trains you along these pages. The path then stays with you as a manual, and you can work through it alone at any time.
Tell the four kinds of connection apart and read a connection's page.
Find out why a run failed and fix the usual causes.
Connect SALTO, dormakaba MATRIX, ASSA ABLOY eCLIQ and Interflex IF-6040, and put a CLIQ domain under portierX.
Set up single sign-on and SCIM provisioning with Microsoft Entra ID.
Bring people in through the HR file and decide the runs that wait for you.
Add the users no directory brings in, and give every user their role.
You need the Organisation Admin role and a login to your own organisation. An Access Manager can connect and check the access control systems on this path as well. Only the Organisation Admin sets up Microsoft Entra ID and the HR file. For each connection you also need values from your IT, which the page of each system lists.
Your first day in portierX. You sign in and find where your work starts.
What your role lets you see and do. You know which roles see connections at all and which change them.
How connections work in portierX. You know the four kinds of connection and the wizard that creates them.
What the connection screen is telling you. You read on a connection's page whether the system can be reached and how its runs went.
A sync failed or brought nothing across. You find out why a run failed or brought nothing across, and fix the cause.
Connect your SALTO system. You connect a SALTO system with the values from your IT or your SALTO partner.
Connect dormakaba MATRIX. You connect dormakaba MATRIX over its REST interface.
Connect ASSA ABLOY eCLIQ. You connect ASSA ABLOY eCLIQ with its client certificate, and renew the certificate before it expires.
Put a CLIQ domain under portierX. You decide whether portierX takes over a CLIQ domain, and know what that changes.
Connect Interflex IF-6040. You connect an Interflex IF-6040 together with your IT.
Set up single sign-on with Microsoft Entra ID. You let your colleagues sign in with their Microsoft work account.
Provision people from Microsoft Entra ID. You let Microsoft Entra ID create and deactivate users in portierX.
Connect your HR system through a daily file. You let your HR system keep the people in portierX up to date.
Review, apply or undo an HR file run. You decide the HR file runs that wait for you, and undo a run when needed.
Where people records come from. You know which source keeps which detail of a person when several systems bring people in.
Add a user and set their role. You add the users no directory brings in, and give every user their role.
How portierX keeps your organisation's data separate and secure. You answer IT and procurement on how portierX keeps your organisation's data separate and secure.
Open Integrations, tab Connected, and open each connection to an access control system with See Details. On Summary, read whether portierX reaches the system and when it last synchronised (What the connection screen is telling you).
On a connection's Sync Log tab, find the last run that did not succeed, open it and match what it reports to one of the causes (A sync failed or brought nothing across).
If your organisation signs in with Microsoft, open the single sign-on connection and read on Summary the Sign-in Readiness and the cards Email Domains and Verified (Set up single sign-on with Microsoft Entra ID).
If SCIM is set up, find on the SCIM connection's Event log tab the calls whose outcome is Rejected, open one and read the reason (Provision people from Microsoft Entra ID).
If your HR system sends a file, open the last run on the HR file's Sync Log tab with Open run and read its counts and refused rows (Review, apply or undo an HR file run).
What does Connected on a connection's summary tell you, and what does it not tell you? (What the connection screen is telling you)
In which cases does portierX not try a failed run again? (A sync failed or brought nothing across)
What does a person need in portierX before they can sign in with single sign-on? (Set up single sign-on with Microsoft Entra ID)
What does Microsoft Entra ID create in portierX over SCIM, users or people? (Where people records come from)
What happens to the changes of an HR file run that go over the daily limit? (Connect your HR system through a daily file)
Next comes the path for the Security Monitor, who reads the audit log and the reports (Training path: Security Monitor).
