Identity and access management
AFAS to Omada integration: AFAS Profit as the authoritative source for Omada Identity
With an integration between AFAS Profit and Omada Identity, Omada reads every employee from AFAS as an identity, with job code, organisational unit, manager, employer and a status that follows from the end date. KoppelHet delivers one correct record per employee, so Omada assigns roles, revokes access and routes reviews to the right manager.
What the integration does
Organisations that use AFAS as their HR system and Omada for roles, access requests and recertification often have Omada import an export from AFAS that someone once built. When a field is added or a job name changes, the role in Omada is no longer right, and a departure only comes in when the export runs again.
- The AFAS administrator creates a dedicated app connector for KoppelHet, with only the GetConnector for this integration.
- KoppelHet reads employees, job lines and organisational units and determines the current job, unit and manager per employee.
- KoppelHet offers one record per employee on its own secured address, with a status that follows from the end date.
- Omada's REST collector reads that address as the authoritative source, and Omada assigns roles on job code and unit.
- After the end date the status becomes inactive and Omada revokes access according to its own policy.
What to watch for with AFAS Profit and Omada
- Omada rejects an identity without a business key, unique ID, name or status. AFAS has no status field that says exactly that. KoppelHet derives the status from the end date and stops delivering a leaver as active once that date has passed.
- Omada maintains an identity's status itself and advises against passing the status from the HR source straight through to the portal. We agree with you which side leads, so a block security sets in Omada is not lifted by an AFAS import.
- A job in AFAS has a code and a description. Roles in Omada should be based on the code, because HR sometimes changes descriptions. KoppelHet supplies both, so a new job name in AFAS does not make roles in Omada lapse.
- A job or department change is often entered in AFAS weeks ahead, with a start date. Omada only reads what the source supplies at the time of import. KoppelHet only passes on the new job from the start date, so Omada switches the role on the right day.
- In AFAS the employer sits on the contract, not on the employee. When someone moves to another company in the group, the employee number stays the same. KoppelHet supplies the employer of the current contract, so Omada keeps the same identity on that move and only switches the employer-specific roles.
- Omada's REST collector can fetch nested data, but then only uses the first element of a list. Someone with two job lines would get a random role that way. KoppelHet therefore selects the current job up front and supplies one flat record per employee.
- KoppelHet reads AFAS with a dedicated GetConnector that only contains the fields for Omada. BSN, salary and bank details are not in it, so the identity environment never sees them.
This integration is also part of joiner, mover, leaver.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Does Omada need rights in AFAS itself?
No. Omada only reads KoppelHet's address, with its own key. Access to AFAS stays with KoppelHet's app connector.
What if an import suddenly shows many leavers?
Then Omada stops if you have set a threshold for deletions. It is off by default; we recommend switching it on at go-live.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AFAS is read with a dedicated GetConnector under its own app connector (OAuth or token; the classic token expires on 31 August 2027), filtered on modification date, including job lines with start date and the tree of organisational units.
- Omada reads through the REST collector (Content: Identity data) with OAuth2 Client Credentials. Required identity fields Business key, Unique ID, Name and Status. Paging through a continuation token (JSON body only) or without a total until an empty set comes back. Thresholds for new, modified and deleted objects as percentages, default 0 (off); timeout 3600 seconds by default.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AFAS Profit | Field in Omada | Notes |
|---|---|---|
Medewerker (EmId) | Business key en Unique ID | Required in Omada |
Roepnaam, voorvoegsel en achternaam | Name | Required in Omada |
Datum uit dienst | Status | Required in Omada; derived by KoppelHet |
Functiecode | Functie voor rollen | Description is sent separately |
Organisatorische eenheid met pad | Afdeling | |
Leidinggevende | Manager | |
Werkgever van het geldende contract | Bedrijf | |
Datum in dienst | Startdatum |
Related
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
AFAS Profit → 4PS Construct
AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company
AFAS Profit → Adobe Creative Cloud
AFAS to Adobe Creative Cloud integration: users and product profiles from AFAS Profit
AFAS Profit → AG5
AFAS to AG5 integration: employees, employments and absence from AFAS Profit in the skills matrix