Quality Center read only access and consumer counts

Quality Center read only access is one of the most common ways a consumer count drifts above the population that genuinely uses the product, because a viewer who only reads a dashboard or a test result is counted as though they held a full working seat. Defending the count means separating people who merely view from people who actually do work, and showing where the entitlement draws that line.

Quality Center, the long established test management product now under OpenText through the Micro Focus acquisition, is often opened up beyond the core testing team. Managers want to see progress, business stakeholders want to read defect status, and auditors of the project itself want a window into quality. Those viewers are given read only access so they can look without changing anything, but to a measurement script an account with access is an account that counts. The result is a consumer count inflated by every observer, and because the EULA places compliance on the licensee, the evidence that an account is read only has to come from the buyer.

Why read only access inflates the consumer count

A measurement enumerates the accounts that can reach Quality Center and, by default, treats each as a licensable consumer. It does not distinguish the tester who authors and executes test cases from the manager who opens a report once a week to read it. Both have accounts, both appear in the records, and both read as full seats. The inflation is the entire population of viewers, observers, and stakeholders who consume nothing but a view, and who were never the users the working entitlement was sized for.

This is the test management version of a problem that runs through every consumer based license: the gap between access and use. The same disqualification logic that removes service and dormant accounts from a named user count, set out in defending an ALM named user overclaim line by line, applies to read only viewers, who consume the product in a fundamentally lighter way than working users. Establishing what the named user definition actually covers, the ground in Quality Center named user definitions and traps, is where the separation begins.

What separates a viewer from a working consumer

A read only account can open and read but cannot create, modify, or execute. A working consumer authors test cases, runs them, logs and updates defects, and changes the state of the project. The evidence that tells the two apart is the permission profile attached to each account and the activity behind it: a viewer shows only read events, while a working user shows creation and modification. Pulling the permission configuration and the activity logs, and presenting them cleanly, is the same discipline as documenting concurrent ALM users for a rebuttal.

How much the misclassification costs depends on the model and on how the entitlement treats viewer access. Under a named model every read only account wrongly counted as a working seat adds cost directly, and how named and concurrent counting interact is set out in named versus concurrent user counting in ALM audits. The product context matters too, because the way Quality Center is licensed differs from the broader ALM platform, the comparison drawn in ALM versus Quality Center licensing compared.

How we defend a read only consumer finding under the four Rs

Respond. OpenText gives seven days notice before an audit and the right to copy relevant records. We take over the single controlled channel and ensure the permission profiles and activity logs are preserved together, because telling a viewer from a working consumer depends on showing what each account could do and what it actually did.

Reconstruct. We build the effective license position against entitlements before any vendor script runs, classifying every account by its permission profile and activity and separating read only viewers from working consumers.

Rebut. We challenge every line that counts a read only viewer as a working seat, presenting the permission configuration and the read only activity for each. The finding falls by the full population that views without doing work, where the entitlement treats that access differently.

Resolve. We settle on the count that reflects genuine working use and, where it serves you, convert forward into an OpenPass agreement that records how viewer access is treated, so the next review cannot recount observers as full consumers.

An anonymised outcome

The reason it pays to separate viewers from working users 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 viewer miscounted as a working seat carries several charges at once. Our anonymised case files show how far classifying access correctly can go: an insurance ECM seat count finding was reduced from $7.2M to $1.6M, a 78 percent reduction built on disqualifying accounts that were never genuine consumers in the sense the finding assumed. A Quality Center read only finding responds to the same evidence, because a view is not the same as work.

Count work, not views

The lasting point is that a consumer count should reflect who does work in Quality Center, not who can open a report, and a finding that counts read only viewers as working seats can be taken apart with the permission and activity evidence each account leaves behind. A buyer who maintains clean permission profiles and can show the read only activity behind viewer accounts holds the finding to genuine working use. To build the position, read Quality Center named user definitions and traps and ALM versus Quality Center licensing compared, alongside reconciling ALM entitlements before an audit. 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 read only viewers as working seats, open a case.