Version 2026.08
Plain-language guidance for the Obedience ecosystem, company controls, support, procurement, legal terms and responsible use.
Understand what Global, QuantifyQS and Cloud each do before requesting access.
See how the company site, QuantifyQS product and Cloud account service divide responsibilities while sharing one trusted identity.
Match a business outcome to Global, QuantifyQS or Cloud before starting an evaluation or support request.
Send enough information for useful triage without disclosing credentials or project-confidential material.
Choose the right public contact, signed-in case or security-reporting channel so the request reaches an accountable queue.
Capture reproducible, privacy-conscious evidence that helps support diagnose a fault without receiving unnecessary project data.
Interpret live indicators, planned maintenance notices and incident updates without confusing a marketing badge with a service guarantee.
Separate a service complaint from an ordinary support case and ask for review by the appropriate accountable owner.
Use the public controls and evidence boundaries to assess the platform without relying on marketing shorthand.
Find the legal entity, service boundary and evidence needed to begin supplier review.
Find the current governed policy, understand its version and retain a reliable copy for review.
Assemble the company, security, privacy and product evidence a buyer normally needs without exchanging secrets by email.
Evaluate Obedience as a supplier using current, attributable evidence and a clear distinction between public and restricted material.
Structure early conversations around outcomes, users, controls, capacity and integration before a tailored proposal is written.
Understand scope, assumptions, capacity, services and validity before accepting an Obedience proposal.
Commission bespoke Firm or Enterprise panels through a reviewed component release rather than ungoverned customer code.
Treat published plan descriptions as a starting point and confirm price, capacity, services and customer-specific work in writing.
Use a time-bounded evaluation with closed registration, named participants and a clear conversion or closure decision.
Review consequences, export needs and any genuine retention offer before confirming cancellation.
Query an invoice, payment or account reference with enough evidence for finance to respond securely.
Check supplier details, line items, tax treatment, status and payment reference before processing an invoice.
Define a bounded evaluation that demonstrates a real workflow without presenting pilot activity as proven production performance.
Use a short, role-specific demonstration to show the product honestly while keeping unreleased and customer-specific areas out of view.
Move from demonstration to limited live use with named users, success criteria, support ownership and an exit decision.
Check the documents that define service scope, term, data handling, support and customer-specific commitments.
Find the current public policy, agreement explanation or controlled document without relying on an obsolete copy.
Use effective dates, review dates and change notices to determine which public policy applies.
Give actionable feedback that can be assessed for a customer-specific agreement or the shared product roadmap.
Know how confirmed service incidents are assessed, updated and closed without treating unverified reports as established events.
Understand the public approach to service resilience, communication, prioritisation and recovery governance.
Frame recovery objectives, customer responsibilities and evidence questions for the relevant contracted service.
Explain an accessibility barrier and preferred adjustment so the team can respond without requiring unnecessary health information.
Submit an identity-verifiable request for access, correction, restriction, portability or deletion of personal data.
Distinguish customer, user and Obedience responsibilities when personal and project information is processed.
Use the visible consent controls to make, change or withdraw optional analytics choices.
Understand how relevant service providers are disclosed and evaluated for the product you intend to use.
Identify which records are retained, why retention varies and how deletion or legal holds affect the lifecycle.
Know when AI assistance may be used, what human review remains mandatory and what information should not be submitted.
Understand the disclosed provider boundary, consent expectations and records used for AI-assisted features.
Assess the published layers for identity, transport, isolation, storage, monitoring and secure development.
Send a responsible, minimally invasive vulnerability report through the dedicated security route.
Know which accounts must enrol, how test identities differ and why administrators cannot bypass personal factor setup.
Follow invitation, activation, security, suspension, recovery and closure as distinct governed account states.
Separate Global corporate ownership, Cloud platform operations and Quantify workspace administration.
Use authoritative company identity and registered-office information during supplier setup and contracting.
Describe a relevant technical, commercial or professional partnership without sending a generic sales pitch.
Route factual questions, interview requests and publication deadlines to the appropriate company contact.
Use the appropriate route for employment, contractor or specialist-review opportunities.
Distinguish essential service mail from optional newsletters and promotional communications, then update preferences.
Know how weekly product news and occasional commercial offers should be consented, identified and measured.
Interpret what changed, when it applies, who is affected and whether customer action is required.
Navigate categories, search terms, versions, review dates, related guides, access labels and downloadable copies consistently.