Insights - How 4chems Secures Connected Data in Multi-Client IUCLID Environments

The question compliance directors at consulting firms ask most often — how do you make sure my client's data cannot reach another client's screen? The answer is architectural, not procedural.

· Oliver Philippsen · 2 min read

The question we get most often from compliance directors at consulting firms: how do you make sure my client’s data cannot reach another client’s screen?

The answer is architectural, not procedural.

One Client. One Instance.

Every client in 4chems gets a dedicated IUCLID installation — not a folder, not a workspace, not a permission set inside a shared environment. A separate running instance of IUCLID, isolated at the infrastructure layer. There is no query that can cross from one client’s environment to another, because they are not connected at all.

This is different from multi-tenant platforms where data separation is enforced by access rules. Rules can be misconfigured. Infrastructure isolation cannot.

Access Is Managed Inside IUCLID’s Native Interface.

Within each instance, your team works through IUCLID’s native user management: individual accounts, role-based permissions, the same interface they already know. 4chems manages the infrastructure those accounts run on — which means we hold the logs, the backups, and the system configuration. Your team holds the access decisions.

What the Audit Trail Looks Like.

IUCLID records every dossier change against the individual user who made it. Those logs are also isolated. When ECHA requests documentation of a change — who updated a specific section, what the previous value was, when — that information is available and client-specific.

At the infrastructure layer, 4chems maintains backup logs and system-level audit records independently. Two audit trails, not one.

What Stays with Your Team.

We manage the infrastructure: provisioning, updates, backups, system monitoring, dossier migration. Your team manages the dossiers and decides who in their instance can view, edit, or approve. Neither side has authority over the other’s domain.

One limitation worth naming: access management within IUCLID is only as rigorous as how your team configures it. We provide the environment. Deciding which consultant can access which substance portfolio is still your team’s call.


Oliver Philippsen is the founder and general manager of 4chems. He writes about IUCLID infrastructure, regulatory data management, and the operational realities of running compliance environments for consulting firms. Questions about multi-client setup — get in touch.

Related Posts