Documentum D2 client licensing and consumer counts

Documentum D2 is a configurable client that sits over the Content Server, and how its users map to the licensed consumer count is one of the quieter ways a Documentum finding inflates. An audit that treats D2 access as a separate chargeable layer, on top of the underlying repository license, is counting the same activity twice.

D2 is an interface. Users work through it to reach content that lives in the Content Server repository, and the license that matters is the one governing access to that repository and its named users or consumers. The trap appears when an audit lists D2 users as though the client itself carries a distinct entitlement separate from the repository access they already hold, or when every account provisioned in D2 is counted as an active consumer regardless of whether it performs any chargeable action. Because the OpenText EULA places compliance on the licensee, it is the buyer who must show how D2 access maps to the licensed unit, and doing so carefully is where the overcount comes apart.

How D2 access relates to the licensed unit

The licensed unit in a Documentum environment is the named user or the consumer as the entitlement defines it, measured against the repository. D2 is the means by which a user reaches that repository, so a D2 user is, in license terms, a repository user counted under the existing consumer or named user definition, not a new and additional license category. The defensible position treats the repository entitlement as the governing meter and asks, for each D2 account, whether it represents a genuine consumer under that definition. Accounts that exist in D2 but never perform a chargeable action, service identities that drive D2 configuration or integration, and duplicate accounts that map to one person are not additional consumers simply because they appear in the D2 user list.

The principle is that the interface does not create the license, the repository access does. Counting D2 separately from the repository it fronts is counting the door as well as the room behind it.

Where the D2 count overstates

Provisioned but inactive accounts

D2 user lists accumulate accounts that were set up and never used, or used once and abandoned. These are not active consumers, and the evidence that disqualifies them is usage data, the same approach described in reducing a Documentum finding with usage evidence.

Service and integration accounts

D2 configuration and integrations run under accounts that belong to processes, not people. Counting them as consumers repeats the error covered in service and dormant accounts counted as Documentum consumers.

Read only and duplicate access

D2 access that is read only does not meet a chargeable consumer definition, the line drawn in Documentum read only users and the consumer definition, and duplicate D2 accounts that resolve to one identity should be reconciled as set out in how to challenge a Documentum repository headcount.

How we defend a D2 consumer count 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 D2 user list is captured together with the underlying repository extract and usage logs, so the mapping between client access and repository license can be reconstructed accurately.

Reconstruct. We build the effective license position by mapping every D2 account back to the repository consumer definition, removing inactive, service, read only, and duplicate accounts, so the count reflects genuine consumers rather than the raw D2 roster.

Rebut. We challenge any line that charges D2 as a separate layer or counts provisioned accounts as active consumers. The finding falls by the value of every account that the repository definition, properly applied, does not support.

Resolve. We settle on the reconstructed consumer count and, where it serves you, convert forward into an OpenPass agreement that records how D2 access maps to the licensed unit, so future reviews do not reopen the same double count.

An anonymised outcome

The reason the mapping is worth getting right 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. 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 by holding the count to genuine repository consumers rather than the inflated roster the extract produced.

Count the repository, not the client

The lasting lesson is that D2 is an interface to a licensed repository, and the license lives with the repository, not the client. A buyer who insists that D2 users be counted under the existing consumer definition, with inactive, service, read only, and duplicate accounts removed, prevents the finding from charging twice for one access right. To set up that position, 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 D2 user list is driving your finding, open a case.

Keeping the D2 mapping defensible over time

A D2 consumer count is not a one time exercise, because user lists grow as projects come and go and configuration accounts are added and forgotten. The mapping between D2 access and the repository consumer definition has to be maintained, or the next review will start from the same inflated roster. We recommend recording, at the point of the settlement, how D2 users map to the licensed unit and which categories of account, inactive, service, read only, and duplicate, are excluded and why.

That record turns the work of one defense into a standing position. When the next audit arrives, the buyer is not reconstructing the mapping under a seven day clock but presenting an agreed basis. The approach mirrors the wider discipline of a Documentum entitlement reconstruction, where the goal is always to leave the organization with a documented, defensible count rather than a one off argument.