Enterprise sign-on and identity for QueryTek products

In Short

Enterprises expect a new platform to join their existing identity estate, not add another password. QueryTek aligns approved identity providers and single sign-on with tenant workspace context, so people and integrations authenticate once and arrive in the correct customer environment across Review, Tapestry, and platform APIs.

Industry Context

Software portfolios almost never begin with one login model. HR, learning, document review, and integration partners each arrive with their own identity assumptions, and the accumulated result is a directory that no longer matches reality. Identity teams inherit the cleanup.

So the questions asked of a new vendor are specific. Will it federate with the corporate identity provider rather than maintaining a parallel user list? When a contractor's employment ends, does deprovisioning in the directory actually remove their access? Do API clients inherit the same trust posture as a person in a browser, or is machine access a separate system with separate rules?

The last question is the one most often skipped, and the one that causes the most trouble later. An integration credential that outlives the person who created it, and that carries no tenant scope, is the kind of quiet gap that surfaces during an audit rather than during onboarding. Authentication has to establish two facts at once: who is acting, and which customer context applies.

How QueryTek Applies It

Identity Provider: QueryTek federates with the organization's existing identity provider so the directory stays authoritative for who exists and who has left. Account lifecycle remains where the enterprise already manages it, rather than being duplicated per product.

Single Sign-On: Single sign-on lets a person authenticate once and move between QueryTek products without re-entering credentials at each surface. The practical benefit is fewer standing local accounts, which is also the security benefit.

Tenant: Authentication resolves to a tenant, not just to a user. Establishing workspace context at sign-on is what allows an operator working across Review and Tapestry to stay oriented, and what prevents an action from landing in the wrong customer environment.

API: Programmatic access follows the same model. Platform API surfaces are scoped to a tenant and traceable to a caller, so partner integrations inherit the trust posture that applies to people instead of running under separate rules.

Public documentation describes these outcomes. It does not publish SAML metadata recipes, token schemas, or vendor-specific configuration steps, which belong in authenticated onboarding material.

Related Glossary Terms

• Identity provider
• Single sign-on
• Tenant
• API

Further Reading

• Security overview — platform access controls, encryption, and operational monitoring
• Keeping identity and context together across systems — what happens to that context across product boundaries
• Integrating with QueryTek APIs — how programmatic access inherits the same posture