Run several companies, brands or client mandates in strictly separated workspaces with one login — each with its own data, permissions and reporting, and a single overview across all of them.
Anyone who runs more than one entity knows the tax it imposes. A separate login for each company, a separate installation or subscription, a separate place for documents, and a consolidated picture that only exists once a quarter in a spreadsheet somebody builds by hand.
The same applies to trustees, accountants and agencies managing client mandates — with an added obligation: the separation must be real, not a filter, because one client’s data appearing in another’s report is not an inconvenience but a breach.
IDup multi-tenant gives each company, brand, branch or mandate its own workspace with strictly separated data, its own permissions and its own reporting — while you switch between them in one click and see a single overview across the whole portfolio.
All in IDup — one login, no silos.
Each company, brand or client has its own isolated data, settings, numbering and reporting — not a shared database with a filter, which is what makes it acceptable when you hold other people’s data.
Switch between tenants in a click without logging out, without a second subscription and without a separate installation to maintain per entity.
Define exactly who sees and can do what in each workspace. A bookkeeper works in three mandates, a client sees only their own, an employee reaches one brand — all from one user model.
Status, deadlines, open items and figures across all tenants on one screen, so you manage a portfolio rather than a set of unrelated systems.

If you handle data for several clients, the question is not whether your system feels organised. It is whether you could demonstrate, to an auditor or a client, that one mandate’s information cannot reach another.
Shared spreadsheets, a single accounting file with departments, or folders named after clients do not survive that question. They rely on nobody making a mistake.
IDup answers it structurally. Each tenant is a separated workspace with its own data and permissions, every access is logged, and hosting is encrypted on secure servers worldwide under GDPR — so separation is a property of the system rather than of everyone’s carefulness.
One workspace per company, brand, branch or client mandate, with its own separated data.
People get access exactly where they need it, per tenant, from a single user model.
Switch in one click and keep one consolidated overview across the whole portfolio.

Strict separation solves the compliance problem and creates a management one: with everything correctly isolated, how do you see the whole picture?
IDup answers that with a consolidated view over the tenants you are entitled to see. Deadlines, open items, unpaid invoices, missing documents and key figures appear for every workspace on one screen, without breaking the separation underneath.
That is what turns multi-entity work from an administrative burden into a scalable business. Adding the next company or the next mandate costs a workspace, not a system — and you still know at a glance where attention is needed this week.
One login, ein Preis – keine versteckten Zusatzkosten.
Each tenant is its own workspace with isolated data, settings, numbering and reporting. Access is granted per tenant and every access is logged, which is what makes it suitable for holding other people’s data.
No. Multi-tenant workspaces are part of the platform, so you manage several companies, brands or mandates under one login without a separate installation or licence per entity.
Yes, with permissions defined per tenant. A bookkeeper can work in several mandates while a client-side user sees only their own workspace — all from one user model.
Yes. Deadlines, open items and key figures across all workspaces you are entitled to see appear in one overview, without weakening the separation underneath.
Trustees, accountants and agencies managing client mandates, and any group running several companies, brands, branches or countries — each with its own local settings and currency.
Minutes. Create your first tenants, invite the people who need access and assign their permissions — there is nothing to install per entity.