Accounts in your own systems from HelloID Permissions that move with the role Access removed on departure

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 permissions and revokes them on departure, 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, permissions per role, and access removed on the day of departure.

What is a HelloID integration?

HelloID is Tools4ever's identity and access management platform. 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 revokes them. Many ready-made connectors exist for this. Systems that are not on that list need a custom connector, otherwise they fall outside automated 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 permissions are structured, which roles apply per job function, and whether data has to be written back to the source. The connector follows the way HelloID works with connectors, and is tested with real joiners and leavers before it goes live.

Your own system too

Accounts in a proprietary or less common system, created and updated from HelloID.

Permissions per job function

Roles and permissions that follow along when someone changes role or department.

Gone on departure

Access revoked on the day someone leaves, with every action logged for the audit.

How we build your HelloID integration

We start with the target system: which interface it has, how accounts and permissions are structured, which roles apply per job function, and how things work today. The application administrator often knows exactly which tasks are currently done by hand; that is where we begin.

1
Mapping the target system

The interface, accounts, permissions, roles per job function and the current way of working.

2
Building the connector

Creating, updating, blocking and deleting accounts, and granting permissions.

3
Testing

Testing with real joiners, leavers and role changes.

4
Go-live and maintenance

Go-live, a log of every action, and maintenance when HelloID or the target system is updated.

What a HelloID integration actually does

The components below come back in almost every HelloID connector. Which ones you need depends on the target system.

Accounts

Create, update, block and delete.

Permissions

Roles and permissions per job function and department.

Role changes

Permissions that follow along when someone changes role.

Departure

Access revoked on the day someone leaves.

Write-back

Data written back to the source where needed.

Log

Per action, what was done and when.

Who we build a HelloID integration for

The integration is intended for organisations with systems outside HelloID's standard connectors.

Healthcare organisations

Many systems and many changes. Timely offboarding is the core.

Schools and universities of applied sciences

Staff 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 connect to HelloID. The connector is the core.

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. You can read about our way of working on building custom software.

For applications whose users should be managed via the open standard, see our page on a SCIM integration.

HelloID Provisioning HR as source system Target systems Accounts Roles and permissions Role changes Departure Write-back to the source Log per action

Why Appfront for your HelloID integration?

An account that outlives someone's departure is a risk and an audit finding. That is what we build against: your own system included in automated management, permissions that follow along, and access that is removed on time.

No manual work

Your own system follows the HR system too.

No outdated permissions

A role change adjusts the permissions.

Audits 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 receives only the permissions needed to manage accounts, credentials are stored encrypted, and every action is logged.

The connector runs in the environment that HelloID and your organisation require for it, with encrypted connections and daily backups.

Frequently asked questions about a HelloID integration

Questions IT departments ask before they start.

HelloID is Tools4ever's identity and access management solution. It uses the HR system as its source to create accounts in target systems, assign permissions and revoke them when someone leaves.

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 fits the way HelloID works with connectors, and on the other side communicates with the interface of your target system. 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 of the system itself is the best way forward. What fits depends on the system and what the supplier permits.

For each job role and department, you define which roles someone gets in the target system. HelloID uses those rules, and the connector applies them in the system. A change to the rules takes effect for everyone with that job role.

With real joiners, leavers and role 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 an in-house or less common system alongside the systems HelloID already supports, and for suppliers who want to connect their product to HelloID for their customers.

Want your own system in the automated management too?

Tell us which system you want to connect, how accounts and permissions are structured in it and how things work now. We'll show you what the connector looks like.

Edit content