Custom HelloID integration development
Appfront builds integrations with HelloID, the identity and access management platform from Tools4ever. Based on the HR system, HelloID creates accounts in target systems, assigns rights and revokes them on leaving, and it has many ready-made connectors for this. For a proprietary or less common system, we build the connector so that system takes part too: accounts created, rights per role, and access removed on the day someone leaves.
What is a HelloID integration?
HelloID is the identity and access management platform from Tools4ever. It uses the HR system as its source: when someone joins, changes role or leaves, HelloID creates accounts in the target systems, adjusts permissions or removes them. There are many ready-made connectors for this. For systems not on that list, a custom connector is needed, otherwise that system falls outside automatic management.
A system without a connector is maintained by hand. A new employee gets an account in every system except that one in-house application, where an application administrator sets it up days later. Someone changes department and keeps their old permissions. And when someone leaves, the account stays in that system because nobody thinks of it. In an audit, that is exactly what stands out.
We build custom connectors because every target system is different: which interface it has, how accounts and rights are structured, which roles apply per job, and whether data must flow back to the source. The connector matches how HelloID works with connectors, and is tested with real joiners and leavers before it goes live.
Your own system too
Accounts created and updated in your own or less common system, driven from HelloID.
Permissions per job
Roles and permissions that follow along when someone changes job or department.
Removed on leaving
Access revoked on the day of departure, and logged per action for audit.
How we build your HelloID integration
We start with the target system: which interface it has, how its accounts and rights are structured, which roles apply per job, and how things work today. Often the application administrator knows exactly which steps are still done by hand; that's the starting point.
The interface, accounts, rights, roles per job and the current way of working.
Creating, updating, disabling and deleting accounts, and assigning permissions.
Testing with real joiners, leavers and job changes.
Go-live, a log per action, and maintenance when HelloID or the target system is updated.
What a HelloID integration does in practice
The components below come up in almost every HelloID connector. Which ones you need depends on the target system.
Accounts
Creating, updating, disabling and deleting.
Permissions
Roles and permissions per job and department.
Job changes
Permissions that follow along when someone changes role.
Leavers
Access revoked on the day of departure.
Write-back
Data written back to the source where needed.
Audit log
What was done and when, per action.
Who we build HelloID integrations for
The integration is intended for organisations with systems outside HelloID's standard connectors.
Healthcare providers
Many systems and job changes. Timely removal on leaving is the core.
Schools and universities of applied sciences
Employees and students. Permissions per role matter most.
Municipalities
In-house applications alongside off-the-shelf packages. The audit is what's needed.
Software suppliers
A product that needs to integrate with HelloID. The connector is at the heart of it.
Technology and integrations
This page is about connectors for HelloID. For custom identity and access management, see our page on an IAM system; for Microsoft, our page on an Azure AD integration; and for HR as a source, our page on a Buddee integration. Read about our approach at custom software development.
For applications that want users managed through the open standard, see our page on a SCIM integration.
Why choose Appfront for your HelloID integration?
An account that survives after someone leaves is a risk and an audit finding. We build around that: your own system included in automated management, permissions that follow along, and access removed on time.
No manual work
Your own system follows the HR system too.
No outdated permissions
A job change adjusts the permissions.
Audit without worry
Every action is logged.
Security and privacy in a HelloID integration
The connector manages accounts and permissions, the keys to your systems. It only receives the rights needed to manage accounts, access details are stored encrypted, and every action is logged.
The connector runs in the environment that HelloID and your organisation require, with encrypted connections and daily backups.
Frequently asked questions about a HelloID integration
Questions IT departments ask before starting.
HelloID is the identity and access management platform from Tools4ever. It uses the HR system as a source to create accounts in target systems, assign permissions, and revoke access on leaving.
Yes, plenty. If your systems are on that list, you don't need a custom connector. A custom connector is for an in-house application or a system for which no standard connector exists.
The connector matches the way HelloID works with connectors, and on the other side it talks to your target system's interface. We look at which interface the target system has in the first step.
Then we look at other routes, such as a database or an import function, depending on what the system and the supplier allow. Sometimes a small extension to the system itself is the best way. What fits depends on the system and what the supplier permits.
You define, per job role and department, which roles someone receives in the target system. HelloID applies those rules, and the connector carries them out in the system. A change to the rules takes effect for everyone with that job role.
With real joiners, leavers and job changes in a test environment, before it goes live. Only once accounts and permissions are correct does the connector go live for real employees.
For organisations with a proprietary or less common system alongside the systems HelloID already supports, and for vendors who want to integrate their product with HelloID for their customers.
Your own system in automated management too?
Tell us which system you want to integrate, how its accounts and rights are structured, and how things work today. We'll show you what the connector would look like.