HomeArticlesDocumentum read only users and the consumer definition
ECM & Documentum · Field Note

Documentum read only users and the consumer definition

Documentum read only users are one of the most reliable sources of audit overcharge, because a person who only views content is often counted as a full consumer. Whether that count is fair turns entirely on the consumer definition in your contract, and that definition is worth reading closely.

Large content estates always carry a long tail of users who do very little. They open a document occasionally, look at a record, or read something a colleague produced, and then leave. They never author, edit, or contribute. In licensing terms these read only users may or may not be chargeable as full consumers, and the answer is not obvious from the way the platform records access. Because the OpenText EULA makes compliance the sole responsibility of the licensee, the burden of distinguishing a genuine consumer from a casual viewer sits with the buyer, and an audit that counts every account with any access as a full consumer will overstate the finding.

What the consumer definition actually controls

The consumer definition is the contractual statement of who counts as a chargeable user of the platform. It is the hinge on which a large part of any Documentum finding turns, because it decides whether the long tail of light, read only access is inside the count or outside it. A narrow, precise consumer definition that ties chargeability to meaningful use protects the buyer. A broad reading that counts any access at all expands the finding dramatically.

An audit naturally prefers the broad reading, because every additional account it can classify as a consumer adds to the finding. The buyer's task is to hold the audit to the actual definition in the contract, and to support the classification of each light user with evidence of how they actually interact with content. This is the same evidentiary discipline that governs the wider population, described in how Documentum named user counts inflate an audit finding.

The trap

An account with access is not automatically a consumer. The consumer definition in the contract decides who counts, and a person who only views content may fall outside it. Counting every viewer as a full consumer is a classic Documentum overcharge.

Where read only users inflate a Documentum finding

Viewers counted as full consumers

The core overcharge is treating a read only viewer as though they were a full, contributing consumer. If the consumer definition distinguishes between levels of access, or ties chargeability to actions beyond simple viewing, then viewers should be classified accordingly. An undifferentiated count that lumps viewers in with authors overstates the consumer population.

Occasional access treated as active consumption

Some users touch the platform only rarely. Whether an account that is accessed a handful of times a year is a genuine consumer depends on the definition and on the usage evidence. Occasional access is often a sign of a light user who should be classified carefully rather than counted at full rate. The same logic helps separate live users from inactive ones, as covered in service and dormant accounts counted as Documentum consumers.

Indirect viewers counted directly

A person who views content only through another application, rather than by using a Documentum client directly, raises the indirect access question. Whether they are a direct consumer at all depends on how they interact with content, and counting them as direct consumers can be challenged on the same basis as other indirect users.

Read only roles in non production environments

Viewers in test or training environments may be counted as production consumers. Non production access is a separate question, examined in Documentum non production environments and license claims, and read only access there should not be swept into the production consumer count.

Defending the read only and consumer question under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. In that window we take over the channel so that a raw access list is not accepted as the consumer count. The consumer definition, not a database query, must govern who is in the count.

Reconstruct. We build the effective consumer position independently. We read the consumer definition precisely, classify each user against it, separate read only viewers and occasional users from full consumers, scope indirect and non production access, and assemble usage evidence for each contested classification. The reconstructed consumer count is what we defend.

Rebut. We challenge the finding line by line against the definition. Viewers who fall outside the consumer definition come out of the count. Occasional users are classified on usage evidence. Indirect viewers are tested against how they reach content. Each adjustment is grounded in the contract language and the activity record.

Resolve. We settle on the corrected consumer count and, where it serves you, convert forward into an OpenPass agreement with a clear consumer definition, so the read only question cannot be reargued at the next renewal.

An anonymised outcome

The financial stakes follow the usual pattern. 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 of the audit, so every viewer wrongly counted as a full consumer multiplies the bill. 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 classifying the long tail of light and read only users correctly rather than counting them all as full consumers. The consumer definition did much of the work.

Reading the definition that decides the count

The recurring lesson is that the consumer definition is not boilerplate to be skimmed. It is the single contractual term that decides whether your large population of light, read only users sits inside or outside the chargeable count, and the difference is often enormous. A buyer who reads the definition closely, understands exactly what it captures, and can classify its users against it holds a precise instrument for challenging an inflated finding. A buyer who accepts the audit's broad reading hands the vendor the most valuable classification it could ask for.

The classification work is evidentiary. It means understanding how each segment of the user base actually interacts with content, distinguishing those who author and contribute from those who only view, and supporting the distinction with activity records. Where the definition ties chargeability to meaningful consumption, the viewers and occasional users fall away, and the genuine consumer count is much smaller than the access list suggests.

None of this requires accepting that access equals consumption. A Documentum finding that counts every viewer as a full consumer is a claim built on a broad reading of a definition that may not support it, and it is a claim a prepared buyer can answer with the contract in one hand and the usage evidence in the other.

Where to go next

For the full method behind an ECM finding, read our complete OpenText audit defense playbook for 2026 and our ECM and Documentum audit defense track. To see how the consumer definition interacts with whole repository counts, read how to challenge a Documentum repository headcount. If a Documentum finding counts your read only users as full consumers, open a case and we will classify the population against your actual consumer definition.

If an OpenText or Micro Focus audit notice has landed, the first seven days weigh more than any week that follows. OpenText Audit Defense is an independent, buyer side practice founded in 2020 by former vendor compliance leadership. We have defended more than 200 audits, reduced the average finding by 68 percent, and mitigated more than $90M in claims against vendor positions. We do not resell OpenText software and we are not affiliated with OpenText Corporation. To open a case, use the contact form on this site.