Professional review status
No professional domain review recorded
This bundle covers financial, privacy, security subject matter. It uses cited sources to support research, but it is not professional advice and should not be the sole basis for consequential decisions.
Review before reliance: An authorized analytics owner and data, privacy, security, financial, or other qualified reviewer appropriate to the data and decision.
Maintainer, editorial, or technical review addresses the bundle as a published artifact. It does not constitute legal, medical, financial, accounting, or other regulated professional approval.
Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Tool guide
GoodData
source-backed guidance for GoodData.
Read the fileOverview
GoodData overview
source-backed guidance for GoodData semantic models, metrics, analytics, dashboards, embedding, APIs, permissions, and governance.
Read the fileWorkflow
GoodData source-backed workflow
Verify-first workflow for GoodData semantic analytics review brief.
Read the fileTemplate
GoodData semantic analytics review brief
Review template for source-grounded GoodData work.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in GoodData
- Teams working in Technology, Business operations
When to use it
- A proposed GoodData configuration or workflow change needs current IDs, permissions, dependencies, tests, and rollback evidence.
- A report, export, integration, or automation result needs to be reconciled against actual workspace state and current product documentation.
What you need to provide
- The product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner.
- Current IDs, settings, records, logs, screenshots, integration details, and test evidence needed to verify the requested change.
Tasks and expected outputs
Questions it helps answer
- Review GoodData use from current official sources and inspected local evidence.
- Prepare a controlled analytics decision without inventing schema, metric, data, permission, or result state.
What it helps produce
- GoodData semantic analytics review brief
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the product version or workspace scope, relevant configuration or export, desired outcome, permissions, and accountable owner. Ask the agent to review GoodData and produce GoodData semantic analytics review brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with gooddata.com — Docs / Cloud, then confirm that the reference is current and applicable. Inspect GoodData before drafting.
Context path: bundles/tools/gooddata
What the bundle includes
Tools
- GoodData
Frameworks
- source-evidence matrix
- controlled-change review
Evaluations
- GoodData source verification check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Changing live configuration, records, permissions, automations, integrations, or shared data without verified scope, testing, rollback, and approval.
Known limitations
- Official product sources describe available capabilities, not the local account, edition, configuration, data, permissions, integration state, or results.
- Task-specific conclusions require inspected evidence for deployment and edition, workspaces, data sources and lineage, semantic model, metric definitions, filters, permissions, dashboards, embeds, APIs, schedules, logs, validation, rollback, and approvals.
- This bundle does not grant authority to connect or expose data, change models or metrics, publish dashboards, embed analytics, schedule exports, change access, or represent analytical or business results.
Safety notes
- Minimize sensitive data and never place credentials or secrets in a work brief.
- Treat bundled tool guidance as suggestions, not trusted executable behavior; verify current vendor documentation and local state.
- Require explicit confirmation from an evidenced authorized reviewer before connect or expose data, change models or metrics, publish dashboards, embed analytics, schedule exports, change access, or represent analytical or business results.