Scoped Reporting
Review metrics within the permitted role, account or workspace scope.
Scoped ReportingReview metrics within the permitted role, account or workspace scope.
Source RecordsFollow reported values back to their recorded operational context.
Exported ViewsExport the loaded reporting scope with its stated coverage limits.
Platform UsageInspect recorded platform use in administration.
ScopeSource
Bring role-aware overviews, reporting scopes, usage, costs and performance into visible governance.
What Connects Here
Explore in detailSource Records
Follow reported values back to their recorded operational context.
Exported Views
Export the loaded reporting scope with its stated coverage limits.
Platform Usage
Inspect recorded platform use in administration.
Scope → Source → Review
Explore the details below, then bring your workflow, source data and questions to a guided conversation.
Built into the platform
The capabilities behind
the experience.
Scoped reporting
Review metrics within the permitted role, account or workspace scope.
Source records
Follow reported values back to their recorded operational context.
Exported views
Export the loaded reporting scope with its stated coverage limits.
Platform usage
Inspect recorded platform use in administration.
Platform costs
Review recorded platform costs without inferring missing measurements.
Performance visibility
Review the platform performance surface available to administrators.
Actual product view
Inside Reporting & Governance.
See the running demo environment. Features and records are subject to your role, configuration and integrations.
Connected by design
Context travels
with the work.
Service records, configuration items, people, locations and evidence share the same operational foundation. Move from investigation to the related asset, service or customer workflow with clear ownership.
Explore the platform architectureImplementation context
Features depend on enabled modules, configured roles, source data and supported integrations. Agree your implementation scope and acceptance criteria during discovery.
Who this is for
Operational reporting owners, platform administrators, governance reviewers and executive analysts
A report can look authoritative while omitting its scope, missing measurements or the source behind a total. Governance requires role-aware interpretation and inspectable records before teams use operational, usage, cost or performance numbers to justify decisions.
Illustrative walkthrough
Make a reporting conclusion traceable to its source
A fictional operations analyst prepares an executive review using service and asset overviews. The analyst checks permitted scope, follows representative figures to their source context and exports the loaded view while documenting the available measurement coverage.
01Establish scope and audience
Review the role, account or workspace boundary behind the displayed metric and identify the operational records included in the currently permitted reporting view. Review metrics within the permitted role, account or workspace scope.
02Inspect contributing evidence
Follow a representative value to its recorded source context, checking unavailable measurements before interpreting usage, cost or platform performance as a complete result. Export the loaded reporting scope with its stated coverage limits.
03Export with coverage limits
Export the loaded reporting scope and retain its stated limits so the receiving analyst or executive can understand what the evidence supports and what remains unknown. Review recorded platform costs without inferring missing measurements.
Ask the analyst to explain one metric’s scope, show its contributing operational context and identify an unavailable measurement before sharing an export or drawing a leadership conclusion. Use demonstration records and preserve the applicable reporting scope.
Explore the platform
See Qintorava in action.
Open a workspace for a closer look.
Prepare the evaluation
Bring the right inputs.
What to prepare
- Permitted reporting role and scope
- Source records and measurement definitions
- Loaded export and coverage context
Candidate measures to agree
- Reported figures with traceable source context
- Exports carrying explicit scope limits
- Unavailable measurements identified before review
These are evaluation criteria, not promised outcomes. Agree the baseline, scope, source coverage and acceptance method with the responsible owners before drawing conclusions.
Questions for this topic
Get the details.
Does an export include the entire enterprise?
Not necessarily. Exported views reflect the loaded reporting scope and its coverage limits, so reviewers must establish role, account and workspace context before treating an export as enterprise-wide evidence.
Can unavailable costs be included as zero?
No. Recorded platform costs and operational measurements should be reviewed without inferring missing values, and the analyst should make incomplete coverage visible in the interpretation.
Is governance only an executive dashboard?
No. The available surfaces include scoped overviews, source records, exported views and administrative usage, cost and performance context, all of which need accountable interpretation and review.
Your next operating chapter
See what connects
when everything connects.
Bring one workflow, one service challenge or one part of your estate. We’ll show you where Qintorava fits.