Accounts in applications
Nmbrs to Adobe integration: Creative Cloud licences per function from Nmbrs, revoked on leaving
With an integration between Nmbrs and Adobe Creative Cloud, an employee from Nmbrs with a creative function automatically gets an Adobe user in the Admin Console, in the user group for their function and therefore with the right licence. If they change function or leave, the integration revokes the licence, while their files remain available for handover.
What the integration does
Organisations that have Nmbrs as their personnel system and buy Adobe licences for marketing, communications or design assign those licences by hand in the Admin Console. After a job change or departure the licence often stays taken, and at the annual renewal nobody knows who really uses it.
- You record which functions in Nmbrs get which Adobe user group. In the Admin Console the product profiles are attached to those groups.
- KoppelHet reads the employees of the designated companies in Nmbrs daily.
- An employee with such a function becomes a Federated ID in the Admin Console, with the country of their employer, and joins the group for their function.
- On a job change KoppelHet removes them from the old group and adds them to the new one, or to no group at all.
- After the end date they lose all groups and therefore their licences; the account remains for the handover of files.
What to watch for with Nmbrs and Adobe Creative Cloud
- Adobe requires a country when a Federated ID is created, and that country cannot be changed through the API afterwards. Nmbrs stores the home address with country, but a cross-border worker lives in Belgium or Germany. KoppelHet therefore uses the country of the Nmbrs company as employer, not the country of residence.
- In Adobe, licences belong to product profiles. KoppelHet does not put employees directly in a product profile, but in a user group per function to which the profiles are attached. Anyone who leaves the group loses those licences, without KoppelHet needing to know which Adobe products the group contains.
- Functions change in Nmbrs per payroll period. On the first day of that period KoppelHet removes the employee from the group of their old function, so a licence becomes free for a colleague straight away instead of staying taken until the annual clean-up.
- Adobe allows ten calls per minute per client, with at most ten users per call, and recommends syncing no more often than every two hours. Nmbrs changes per payroll period. A daily run in small batches fits that; on HTTP 429 KoppelHet waits the time in the Retry-After header.
- On leaving KoppelHet does not remove the user from the organisation and does not delete the account. With deleteAccount Adobe also deletes the files of an organisation account. KoppelHet only removes all groups; the licence becomes free and the manager can still hand over files.
- Nmbrs has a record for everyone employed, including people who never use Adobe. KoppelHet only creates an Adobe user for functions that have a group in the table. The rest of the staff do not end up in the Admin Console.
- A user with a private address cannot become a Federated ID on your domain. Besides the work email Nmbrs also stores a private address; KoppelHet only uses the work email and reports employees without one to payroll.
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
We already use the User Sync Tool or Entra ID for Adobe. Can this run alongside?
No, choose one source. Two syncs managing the same users undo each other's changes. If Entra ID already fills Adobe, Nmbrs to Entra ID is the better integration.
What if we have no federated directory?
Then the integration uses Enterprise IDs. They work the same way, but with a password at Adobe instead of single sign-on.
When is an account really deleted?
Not automatically. After the handover the Adobe admin deletes the account; automatic deletion after a fixed period can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Nmbrs is read through the Nmbrs REST API with OAuth 2.0 and read access only. In the SOAP EmployeeService (ending 1 March 2027) the sources are called PersonalInfoWithoutBSN and Function_GetCurrent; the country comes from the company data, not from Address_GetListCurrent.
- Adobe through the User Management API (UMAPI): POST to https://usermanagement.adobe.io/v2/usermanagement/action/{orgId} with createFederatedID (country required, option updateIfAlreadyExists), update (firstname, lastname, email), add and remove with group. At most ten users per call, ten calls per minute per client and a hundred per minute per application; testOnly=true validates without changes.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Nmbrs | Field in Adobe Creative Cloud | Notes |
|---|---|---|
EmailWork | user (e-mail) en email | Work email on the claimed domain |
Nickname of FirstName | firstname | |
Prefix en LastName | lastname | |
Land van het Nmbrs-bedrijf | country | Once on creation, not the country of residence |
Function | add group (gebruikersgroep) | Through a table per function |
Datum uit dienst | remove group all |
Related
ADP Workforce Now → Nmbrs
ADP Workforce Now to Nmbrs integration: the Dutch payroll group from ADP in the right Nmbrs company
AlexisHR → Nmbrs
AlexisHR (Simployer One) to Nmbrs integration: Dutch employees into payroll
BambooHR → Nmbrs
BambooHR to Nmbrs integration: Dutch payroll next to a global HR system
Bullhorn → Nmbrs
Bullhorn to Nmbrs integration: placements with hourly pay and end date in payroll