Professional review status
No professional domain review recorded
This bundle covers privacy, security, financial 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: A qualified Looker, analytics engineering, data governance, security, privacy, finance, or platform professional appropriate to the instance and data.
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
Looker source-backed Guide
Defines evidence-grounded planning, review, and controlled use for Looker.
Read the fileOverview
Looker overview
Scope, evidence, and authority boundaries for Looker.
Read the fileWorkflow
Looker source-backed workflow
Verify-first workflow for producing a reviewable Looker model and data-governance brief.
Read the fileTemplate
Looker model and data-governance brief
Review-ready template for Looker evidence, decisions, validation, and controlled next actions.
Read the fileIs this bundle right for your task?
Who it is for
- People who configure, operate, integrate, govern, or review work performed in Looker
- Teams working in Technology, Operations, Cross-industry
When to use it
- A proposed Looker 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
- Plan evidence-grounded Looker work.
- Review configuration, data, control, and operational constraints.
- Prepare controlled changes without inventing local state or outcomes.
What it helps produce
- Looker model and data-governance 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 Looker and produce Looker model and data-governance brief that maps configuration evidence, dependencies, permissions, tests, rollback, and actions that still require approval. Begin with docs.cloud.google.com — Docs / Intro, then confirm that the reference is current and applicable. Inspect Looker source-backed Guide before drafting.
Context path: bundles/tools/looker
What the bundle includes
Tools
- Looker
Frameworks
- evidence-grounded system change
Evaluations
- Looker 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 sources describe general occupational or product behavior; they do not establish local configuration, records, permissions, outcomes, compliance, or authority.
- Task-specific conclusions require current inspected evidence for product variant, instance, version, projects, Git state, connections, credentials, models, explores, dimensions, measures, access grants, roles, content, schedules, APIs, query evidence, tests, owners, and approvals.
- This bundle does not grant authority to change LookML or production projects, use credentials, query or expose sensitive data, alter access, schedule delivery, publish content, or deploy changes.
Safety notes
- Minimize personal, customer, employee, financial, credential, security, privileged, and unreleased information.
- Preserve prompt-supplied facts as Provided and mark missing facts Needs verification; do not invent owners, dates, versions, reviewers, or system state.
- Require explicit confirmation from an evidenced authorized reviewer before change LookML or production projects, use credentials, query or expose sensitive data, alter access, schedule delivery, publish content, or deploy changes.