EnterpriseCAQ
← Modules

Feature · Partner portal

Suppliers work with you, not just for you.

8D reports by email, Excel attachments in version 7, “final_final” in the file name – that is what supplier communication looks like without a portal. EnterpriseCAQ gives partners their own, strictly separated workspace for exactly the cases that concern them.

Strictly separated, deliberately shared.

The portal is a service of its own with its own data – partners never see the internal system.

  • A standalone portal service with its own database – entirely separate from the internal QMS
  • Releases per case and partner with graded rights: read only or comment
  • NDA gate: confidential content is pushed only where an agreement is in force, personal data stays protected
  • Partner replies go into an internal review – nothing reaches the official case unchecked
A partner’s workspace – cases, tasks and documents in one place

A real workplace for partners.

Not a silo of forms: partners get tools they can actually work with.

  • Onboarding by invitation – local accounts, no access to the company network required
  • Document reader with previews for images, PDF, text, Excel and Word – movable, full screen, without downloading
  • File upload for replies and records, task assignments with status
  • The internal QMS warns when the state held by the partner is out of date

Screenshot: document reader in the portal (to follow)

Privacy by design

No personal data, no customer data.

The portal push transfers no personal data and no customer data. That is not a policy promise but is anchored technically in the architecture:

A curated field contract instead of synchronisation

The push never mirrors whole records. Each object type has a fixed transfer contract that names every transferred field individually – case data such as title, status, part number or 8D content. Whatever is not listed there, the system cannot technically transfer.

Data classification with an NDA gate

Every quality object carries a data class. Content classified as “internal” cannot be pushed at all; confidential classes pass the server-side gate only where a matching agreement (NDA/NNN) is in force – independently of any other release, and backed by automated tests.

Two systems, two databases

The portal is a service of its own with its own database. It has no access whatsoever to the internal QMS database – customer master data, personnel data and internal ratings are simply out of its reach.

Every push a deliberate, audited act

There is no automatic full sync: each release is an explicit single act with a snapshot in the tamper-evident audit trail – it remains traceable who gave which revision to which partner and when, and it can be revoked at any time.

See it for yourself?

Start the live demo