Content Suite platform versus module licensing

OpenText Content Suite is not a single license but a platform with modules layered on top, and a finding inflates when an audit charges for modules that were never entitled, never deployed, or never used. Knowing where the platform ends and a separately licensed module begins is the difference between a defensible count and an overcharge.

Content Suite bundles core content management with a range of modules, records management, capture, workflow, and others, each of which may carry its own entitlement. The audit risk is twofold. First, the audit may count a module as in use because its components are present in the deployment, even though the organization never licensed or actively used it. Second, the audit may treat platform level access as entitling every module, then charge for the modules separately, double counting the same users. A defensible position separates the platform from the modules, then holds each to its own entitlement and its own evidence of use. Because the OpenText EULA places compliance on the licensee, it is the buyer who must draw those lines, and drawing them precisely is where the finding comes down.

How platform and module licensing differ

The platform license governs the core content management capability and the users entitled to it. Module licenses govern specific added functions and are counted against their own metrics, which may be users, volume, or deployment, depending on the module. The mistake an audit makes is to conflate the two: to assume that because the platform is licensed, every module present in the installation is also in scope and chargeable, or to count platform users a second time as module users. The correct approach treats each module as a separate question, present or not, entitled or not, used or not, and charges only where all three are true. Components that ship with the platform but are not activated, and modules that were entitled at one point but never deployed, do not belong in the count.

The principle is that presence in an installation is not the same as licensed use. A module that sits dormant in the deployment, unconfigured and unused, is not a chargeable module simply because its files are on disk.

Where the Content Suite count overstates

Modules present but not used

Installations carry modules that were never activated. Usage and configuration evidence shows which modules are genuinely in service, the same activity discipline set out in reducing a Documentum finding with usage evidence.

Double counted users

Platform users counted again at the module level inflate the total. Reconciling users across platform and modules to single identities is the headcount work described in how to challenge a Documentum repository headcount, and the metric detail sits in Content Suite license metrics and where audits overcharge.

Read only and service access

Module access that is read only or driven by service accounts does not meet a chargeable definition, the boundaries covered in Documentum read only users and the consumer definition and service and dormant accounts counted as Documentum consumers.

How we defend a Content Suite finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the channel and ensure the deployment inventory, the module configuration, and the usage data are captured together, so platform and module use can be separated cleanly.

Reconstruct. We build the effective license position by separating the platform from each module, mapping entitlement, deployment, and use for every module, and removing components that are present but not licensed or not used.

Rebut. We challenge every line that charges an unused or unentitled module or double counts platform users at the module level. The finding falls by the value of every module and user the entitlements do not support.

Resolve. We settle on the separated position and, where it serves you, convert forward into an OpenPass agreement that records which modules are in scope and how each is metered, so future reviews do not recharge dormant functionality.

An anonymised outcome

The reason the platform and module separation matters is the remedy behind the finding. On noncompliance the licensee is deemed to have acquired licenses at then current list price, owes back maintenance and support, owes first year maintenance on the new licenses, and reimburses the cost OpenText incurs performing the audit, so every unused module removed takes that fourfold charge with it. In our anonymised insurance engagement, case file E-01, a Documentum centred ECM finding fell from $7.2M to $1.6M, a 78 percent reduction, achieved in part by holding each component to its own entitlement and evidence of use rather than accepting a bundled count.

Separate the platform from the modules

The lasting lesson is that Content Suite is a platform plus modules, and a finding that bills the whole installation as if every module were licensed and live overstates the position. A buyer who separates the platform from each module, then proves entitlement, deployment, and use for each, removes the bundled inflation before the count is even contested. To prepare that separation, read how to reconcile Documentum entitlements before an audit, and to place it in context, read our ECM and Documentum audit defense track and our complete OpenText audit defense playbook for 2026. If a Content Suite finding is charging modules you never used, open a case.

Why bundled findings need to be unbundled early

A Content Suite finding that arrives as a single bundled figure is the hardest kind to contest, because the inflation is hidden inside an aggregate. The work of separating the platform from each module, and proving entitlement, deployment, and use for every component, is most effective when it is done before the count is accepted rather than after. Once a bundled number has been agreed in principle, unpicking it becomes a renegotiation rather than a rebuttal.

We therefore insist on a component level breakdown at the outset, so that each module can be examined on its own entitlement and its own evidence. That breakdown is also what makes a clean forward agreement possible, recording which modules are in scope and how each is metered. The same logic of holding every line to its own basis runs through our approach to reconciling Documentum entitlements before an audit.