QueryTek™

Documentation / QueryTek Review glossary / Client Admin

Client admin

In Short

A client admin is the person at a customer organization who manages that organization's people and access inside a review service. Client users submit documents and retrieve results; the client admin decides who those users are, sees across the organization's work, and acts as the provider's primary contact.

Client Admin concept diagram

Definition

Every customer of a managed review service needs someone who answers for the account. The client admin is that person, and the role is easiest to understand next to the one it governs.

Client users are the people who do the day-to-day work: uploading documents, choosing a module, accepting quotes, and downloading completed reviews. They see the work they are entitled to see.

Client admins do everything a client user can, plus three things users cannot.

  • Manage the team. Admins add colleagues, change their access, and remove people who leave. Access that is never removed is the most common way former staff keep reaching sensitive material.
  • See across the organization. Admins have visibility into the organization's submissions as a whole — volume and status — rather than only their own.
  • Speak for the account. The provider contacts the admin about onboarding, billing questions, and anything that affects the organization rather than a single document.

Both roles live inside the customer's tenant. Neither has any reach into another organization, and neither is a reviewer: the provider's review staff are a separate population whose access follows assignment.

Why It Matters

An account with no clear admin drifts. Nobody notices when a departed employee still has access, nobody can answer "what did we send last quarter", and provider communications go to whoever submitted most recently. Naming the admin role gives each of those questions an owner.

How QueryTek Uses It

QueryTek Review gives each customer tenant client users and client admins. Admins manage their organization's users and see across its submissions; users submit, accept quotes, and retrieve completed work. Role permissions are scoped to the tenant and enforced by the platform rather than by convention.

Related Terms