Documentum mobile and web client access counting

A single Documentum user may reach the repository through a desktop client, a browser, and a phone, all in the same week. An audit that counts each channel separately turns one person into three, and the finding swells with seats that no headcount could ever support.

Documentum is reached through several clients. The traditional desktop application, the web based interfaces, the D2 client, and the mobile applications all connect to the same repository, and a person who works across devices touches more than one of them as a matter of routine. The licensed unit, in almost every Documentum contract, is the person, not the channel. A named user is entitled to access the content through whatever client is appropriate, and counting the clients rather than the people is one of the more avoidable forms of overstatement in a Documentum finding. Yet it happens, because a self assessment script can read access by interface and a finding can present those interface figures as if each were a separate licensable seat. Since the OpenText EULA places compliance on the licensee, the buyer is the party who must show that the channels collapse back to a single person.

How Documentum client access is measured

A Documentum repository records sessions and access by client type. Those records are useful operationally, showing how people work and which interfaces carry load. They are not, however, a license count. The licensed metric is the named user, defined by the entitlement, and one named user remains one user no matter how many clients they use to reach the content. The measurement question is therefore not how many client connections exist, but how many distinct people those connections represent. Resolving the connections back to people is the work that separates an honest count from an inflated one.

The principle to hold to is that the license follows the person, and the person is entitled to the access the contract grants regardless of device. A mobile session and a desktop session by the same individual are the same licensed user exercising the same entitlement. Counting them twice charges the buyer for access that the single license already covers.

Where multi client access inflates a finding

The same person counted per interface

The most direct overstatement is treating each interface as its own seat population and summing them. A person who uses both the web client and the mobile application appears in two interface counts, and an unreconciled finding charges for both. Resolving identities to a single directory removes the duplication, the same reconciliation that underpins how to challenge a Documentum repository headcount.

Anonymous or shared web access read as named seats

Some web access is anonymous, pooled, or read only, and does not map to a named user at all. Counting those sessions as named seats misreads the access model. The boundary between a chargeable consumer and a non chargeable reader is set out in Documentum read only users and the consumer definition.

D2 and specialised clients counted on top of base seats

The D2 client and other specialised front ends connect to the same repository as the base clients. Whether they represent additional licensable access or simply another way for an existing user to reach the content is a question of the entitlement, examined in Documentum D2 client licensing and consumer counts.

Defending a client access finding 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 and ensure the access data is captured in a form that links sessions to people, so the count is not built from interface totals.

Reconstruct. We build the effective license position independently. We resolve client and session records back to distinct named users against the directory, identify anonymous and shared access that maps to no named seat, and establish how specialised clients relate to the base entitlement. The reconstructed count is a count of people, not channels.

Rebut. We challenge the finding line by line. Where the same person has been counted per interface, we show the single identity. Where anonymous or read only web access has been treated as named seats, we reclassify it. Where specialised clients have been stacked on base seats, we read the entitlement. Each correction rests on the access records and the named user definition.

Resolve. We settle on the corrected count and, where it serves you, convert forward into an OpenPass agreement that records the named user as the licensed unit across all clients, so the next audit cannot rebuild the finding from interface totals.

An anonymised outcome

The reason client double counting is costly is the standard remedy. 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 duplicated channel multiplies through four charges. 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. That engagement turned on disqualifying ineligible accounts from the seat count, and resolving multi client access back to single people is the same discipline applied to the way access is recorded rather than the way accounts are provisioned.

Count people, not channels

The lasting lesson is that a Documentum finding built on client access is only correct once the channels are resolved to people. Modern working patterns guarantee that users will touch several interfaces, and an audit that reads interface totals as seat totals will always produce a number larger than the workforce. The reconciliation back to named individuals is the buyer's evidence, and it is decisive: it converts a list of connections into a count of licensed users, which is the only count the contract supports.

For a buyer, the practical step is to ensure access and session data can be tied to individual identities in the directory, so a client based finding can be answered with people rather than channels. To prepare that reconciliation, read how to reconcile Documentum entitlements before an audit, and to see how client access fits the wider defense, read our ECM and Documentum audit defense track. If a finding has counted the same people across several clients, open a case.

Where to go next

For the full method behind a Documentum finding, read our complete OpenText audit defense playbook for 2026. To understand how the base named seat is defined before clients are considered, read what is a Documentum named seat and how is it measured.