Summary: This release tightens who can administer integrations, scheduled jobs and logs in the Integration Hub, and fixes duplicate mapping values in multi-shop setups and queue items getting stuck during large imports.

- Clear separation between iHub Users and iHub Administrators

Regular iHub users now only see the scheduled jobs and server actions that belong to an integration. Enabling or disabling an integration, opening its settings, running a scheduled job manually and marking log entries as checked are reserved for iHub Administrators. Integration logs, queue items and field configurations are no longer visible to every internal user; the iHub User or iHub Administrator group is required .

But Also...

- iHub Administrators can now create and rename scheduled integration jobs without needing full system administrator rights. Editing the code behind a job remains a system administrator task.

- Mapping values created during an import are now linked to the correct integration, so re-importing the same data in a multi-shop setup no longer fails with duplicate mapping errors.

- Queue items no longer get stuck active without an error reason, and endlessly retried, when a large import runs while someone clicks "Process Item" on the same record or two processes handle the same item at once. Failed items are archived with their error reason as expected.

- The "Enable Integration", "Disable Integration" and "Integration Settings" buttons on the integration form are hidden for users who are not iHub Administrators.

- The "Run Manually" button on the scheduled jobs list is only shown to iHub Administrators, and the settings restriction now applies to every integration type.

  Summary: 2 new features for improved data handling and visibility

  - Data Neutralization Support

  Add SQL script to handle data neutralization during staging rebuild

   process, ensuring clean data state for integrations

  - Enhanced Mapper Visibility

  Integration ID now visible in mapper views, making it easier to

  track and configure which integration each mapper belongs to

  But Also...

  This is now easier to track mapper-integration relationships with

  direct visibility in the interface