Understand the Obedience ecosystem

Purpose and scope

See how the company site, QuantifyQS product and Cloud account service divide responsibilities while sharing one trusted identity.

Use this guide as orientation, then rely on the signed agreement, current policy or named support response where those sources set a more specific obligation.

Prepare the right information

• The outcome your organisation needs.
• Which product or public page you are using.
• Whether your question is commercial, product, account or support related.

Follow the controlled process

1. Frame the needState the desired outcome, affected product and accountable contact. For understand the obedience ecosystem, avoid assumptions that have not been confirmed in writing.
2. Review and decideUse the current governed source, record material questions and obtain approval from the person who owns the decision.
3. Retain evidenceKeep the final reference, date, decision and any follow-up action together so a later reviewer can reconstruct what happened.

Expected record

• The correct product route.
• A clear responsibility boundary.
• A named next action or contact path.

Security and disclosure boundary

• Never send passwords, authentication codes, private keys or recovery codes to Obedience staff.
• Share the minimum customer, project and commercial information needed for the stated purpose.
• Public documentation explains controls and responsibilities without publishing exploitable topology, credentials or confidential implementation detail.