What is a Documentum named seat and how is it measured

A Documentum named seat is a license tied to one specific, identifiable person who is authorized to use the system. The definition sounds simple, but how OpenText measures named seats in an audit is where the simplicity ends and the exposure begins.

Understanding the named seat metric matters because it is the unit that most Documentum findings are built on. If you know precisely what a named seat is meant to represent, you can see exactly where an audit count departs from it, and that gap is the heart of any defense.

What a named seat represents

A named user, or named seat, grants the right of one identified individual to access the Documentum repository. The license follows the person, not the device and not the moment of use. This is different from a concurrent model, where a pool of licenses is shared and the limit is the number of people using the system at the same time. With named seats, the question is simply how many distinct, authorized individuals are entitled to use the product.

Because the metric is about distinct authorized people, the correct count is a curated list of humans, not a raw extract of every account that exists. That distinction is the single most important thing to hold onto, because the audit measurement starts from the opposite end.

How OpenText measures named seats in an audit

Rather than asking for a curated list of authorized people, an audit measures named seats by extracting account objects from the repository, group memberships from the connected directory, and login records from the system, then treating the combined population as named users. This is efficient for the vendor and conservative in their favor, because it captures everything and leaves you to subtract.

The measured population therefore includes more than authorized humans. It includes duplicate identities for the same person across repositories, service accounts that are not people at all, dormant accounts for individuals who have left or moved on, and accounts whose access type may not amount to a full named seat. Each of these is examined in our broader analysis of how Documentum named user counts inflate an audit finding.

Where the measurement departs from the definition

Counting accounts instead of people

A single person can hold several account objects across an estate. The named seat metric should count the person once. The audit counts each object. Reconciling objects back to people is the first correction.

Counting machines as people

Service and integration accounts authenticate like users but are not individuals. They do not meet the definition of a named seat. We separate them, as set out in service and dormant accounts counted as Documentum consumers.

Counting access that is not a full seat

Some accounts only consume content in a limited way. Whether limited access maps to a full named seat or a lighter right depends on the entitlement, not the vendor default, a point we develop in Documentum read only users and the consumer definition.

How we measure it correctly under the four Rs

Respond. In the seven day notice window we control the channel and ensure the raw account extract does not become the agreed seat count before it has been curated.

Reconstruct. We rebuild the named seat count from the definition outward: distinct authorized humans, reconciled across repositories, with non human and dormant identities removed and access types matched to the right entitlement. The documentation behind this is described in how to document Documentum named users for a rebuttal.

Rebut. We present the corrected seat count against the vendor extract, line by line, with directory and log evidence behind every removal.

Resolve. We settle on the corrected count and, where it serves you, convert forward into an OpenPass agreement with the seat metric and any perpetual or term positions clearly defined, a topic we cover in Documentum perpetual versus term license positions.

What the correction is worth

Because the named seat is the multiplier in the remedy, correcting it cascades through every stacked charge: list price, back maintenance, first year maintenance, and audit cost recovery. In our anonymised insurance engagement, case file E-01, a Documentum seat finding opened at $7.2M and settled at $1.6M, a 78 percent reduction, once the seat count was rebuilt to distinct authorized people.

Named seats compared with other Documentum metrics

Named seats are only one of the ways Documentum can be licensed, and confusion between metrics is itself a source of overcharge. It helps to see the named seat in context. A concurrent model licenses a shared pool and limits the number of simultaneous users rather than the number of named individuals, so the same activity can produce very different counts depending on which model applies. Applying a named seat reading to a concurrent entitlement, or the reverse, can shift a finding by a wide margin.

There is also a difference between a full named seat and a lighter consumer right. Some users author, manage, and administer content, while others only retrieve or view it. Where the entitlement recognizes a reduced right for limited consumption, charging every such user as a full named seat overstates the position. The boundary is not always crisp, which is exactly why it should be argued from the agreement rather than conceded to the audit default.

Finally, the named seat sits on top of a perpetual or term foundation, and that foundation affects how a shortfall is priced and how back maintenance is calculated. A perpetual license already paid for behaves differently in a remedy than a term license, and the distinction can change both the size of the charge and the shape of the resolution. Knowing which foundation each seat rests on is part of measuring the metric correctly, not a separate exercise.

The practical lesson is that a named seat count cannot be read in isolation. It has to be read against the model the agreement specifies, the rights each user actually exercises, and the perpetual or term basis of the underlying licenses. An audit that flattens all of this into a single full price seat number is presenting a position to be tested, not a fact to be accepted.

Where to go next

For the complete method behind a Documentum seat finding, read our complete OpenText audit defense playbook for 2026 and our ECM and Documentum audit defense track. If you need your named seat count measured correctly before the audit version hardens, open a case through the contact form.