Multi-company and multi-site by design
Every record in Swat iQua Suite belongs to a site, and each user works under one active site at a time. Switching site is a header action, and every switch is logged. Each site has its own localisation — country, currency and time zone — its own password policy and its own e-signature settings, while roles are defined once and assigned per site.
Shared, chosen-site or site-owned masters
Formulas, process masters, product definitions and specifications can be global, shared with chosen sites, or site-owned. Shared masters are read-only at the receiving site; when a site needs a local variation, it forks a site-owned copy that goes through its own approval. You decide what is harmonised across the network and what stays local.
Client-specific specifications
Specifications are versioned, approved by three different people and frozen as snapshots. A specification can be shared across sites for a global client and stays read-only there, so every site tests against the same approved version — and any local change is a controlled fork, never an untracked edit.
Batch records for many clients’ products
Each batch snapshots its own approved product, formula, process and specification versions, so batch records for many clients’ products sit side by side without ever borrowing each other’s masters. Product definitions carry a per-site manufacturing configuration — integrated, bulk then pack, packaging only, or API — with effective dates, which suits sites that run different scopes for different programmes.
Segregation where a client needs it
Where a client programme needs strict separation, it can run as its own site or company: data, role assignments and the audit trail are then scoped to it, and protection against reading other sites’ records applies throughout reports and exports.
We do not publish client counts or network sizes we cannot stand behind. Ask us in a demo how your own site and company structure would map.
