Quality Center named user definitions and traps

Quality Center named user definitions are where a testing tool finding is won or lost. The license counts named users, the individuals authorized to access the application, and an audit inflates the count by reading that definition as widely as it can, sweeping in occasional, dormant, and administrative logins that do not represent genuine standing use. The gap between every account on the system and the genuine named user population is where a Quality Center finding either holds or comes apart.

Quality Center, part of the broader ALM family, is typically licensed by named user, meaning each authorized individual consumes a license whether they log in daily or once a quarter. That model gives an audit a clear target: count the accounts. But not every account is a genuine named user. Disabled accounts left in place, service identities, duplicate logins for the same person, and users who were provisioned for a project that ended all swell the raw account list above the real population. Because the EULA makes compliance the sole responsibility of the licensee, the buyer carries the burden of showing which accounts are genuine named users, and the access and activity records that prove it belong to the buyer.

How the named user definition gets stretched

The named user count should reflect the individuals genuinely authorized to use Quality Center, but an audit can widen it in predictable ways. Disabled or locked accounts that remain in the user table are counted as if active. Service and integration accounts that exist for system to system access, not for a person, are counted as named users. A single person who holds two logins, perhaps from a migration or a role change, is counted twice. And users provisioned for a finished initiative who never had their access removed continue to appear. Each of these adds to the raw count without adding a genuine named user, and the defensible position removes them by showing what each account actually is.

This is the same discipline that governs concurrent counting, where the question is who is genuinely active rather than who has an account, explored in named versus concurrent user counting in ALM audits. The named model raises the stakes because every account on the list, active or not, is a potential charge unless the buyer demonstrates otherwise.

Where the named user count overstates

Disabled and dormant accounts

An account that is disabled, locked, or has not logged in for a long period is not a genuine named user, yet it sits in the user table and gets counted. The activity records distinguish a live user from a dormant one, and challenging a count on this basis is the work described in how to challenge an ALM concurrent user headcount.

Service and integration accounts

Quality Center integrates with other tools, and those integrations often run under their own accounts. How automated and integration access should be treated is examined in how ALM API and integration users are counted, because a system account is not a person and should not consume a named user license meant for one.

Read only and reporting access

Users who only view results or pull reports may not require the same named user treatment as full contributors, a distinction set out in Quality Center read only access and consumer counts. Counting every viewer as a full named user overstates the requirement.

How we defend a Quality Center named user finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take the single controlled channel and preserve the user table, the access logs, and the activity history, because the named user argument depends on showing the true status of each account before anything is shared.

Reconstruct. We build the effective license position by classifying every account, live named user, disabled, service, duplicate, or dormant, before any vendor measurement script runs, so the count rests on genuine individuals rather than raw rows in a table.

Rebut. We challenge every line that counts a disabled, service, duplicate, or finished project account as a named user. The finding falls by the difference between the raw account list and the genuine named user population the records support.

Resolve. We settle on the reconstructed named user count and, where it serves the buyer, convert forward into an OpenPass agreement that records how named users are defined, so the next review cannot quietly widen the definition again.

An anonymised outcome

The reason named user definitions deserve this scrutiny 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 account disqualified removes a fourfold charge. The pattern mirrors our anonymised insurance ECM case, where a seat count finding fell 78 percent from $7.2M to $1.6M after service and dormant accounts were disqualified as consumers; a Quality Center named user finding follows the same logic, because the inflation lives in the accounts that are not genuine users, and once those are removed the count drops to the real population.

Count genuine named users, not rows in a table

The lasting lesson is that the named user definition is the whole game in a Quality Center finding, and a buyer who classifies every account, separating genuine users from disabled, service, duplicate, and dormant entries, holds the count to the real population. To prepare that classification before a notice arrives, read reconciling ALM entitlements before an audit, and to see how the named model compares across the family, read ALM versus Quality Center licensing compared. For the full method see our ALM and LoadRunner audit defense track and our complete OpenText audit defense playbook for 2026. If a Quality Center finding has counted every account as a named user, open a case.