> For the complete documentation index, see [llms.txt](https://docs.datapancake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datapancake.com/core-concepts/views.md).

# Views

System views for monitoring, querying, and integrating with DataPancake metadata and operations.

## Overview

System views expose metadata about data sources, attributes, scans, configurations, and operations. All views are in the `core` schema. Most views accessible via `app_public` role; some require `app_admin`.

## View Sections

* [**Schema Summary Views**](/core-concepts/views/schema-summary-views.md) - Data source overview, scan history, configurations, billing events, audit logs
* [**Schema Analysis Views**](/core-concepts/views/schema-analysis-views.md) - Attribute metadata, polymorphic version tracking, schema evolution
* [**Security & Governance Views**](/core-concepts/views/security-and-governance-views.md) - Security policies, data dictionary, transformations, Gen AI semantic models
* [**Integration & Code Generation Views**](/core-concepts/views/integration-and-code-generation-views.md) - Semantic layer, foreign keys, generated SQL code, Cortex Analyst integration
* [**Monitoring & Diagnostic Views**](/core-concepts/views/monitoring-and-diagnostic-views.md) - Integration process tracking, access control

**Note:** Primary attribute views (`vw_datasource_active_attributes`, `vw_datasource_all_attributes`, `vw_datasource_version_all_attributes`) are documented in [Attributes: Integration & API](/core-concepts/attribute-metadata/integration-and-api.md).

## Quick Reference

**Schema:** All views in `core` schema (e.g., `core.vw_datasources`)

**Schema Summary:** `vw_datasources`, `vw_datasource_scans`, `vw_datasource_scans_in_process`, `vw_datasource_scan_configurations`, `vw_datasource_scan_errors`, `vw_datasource_scan_procedure_calls`, `vw_datasource_billing_events`, `vw_datasource_product_tier_audit_log`

**Schema Analysis:** `vw_datasource_attributes`, `vw_datasource_polymorphic_attributes` (primary attribute views documented in [Attributes: Integration & API](/core-concepts/attribute-metadata/integration-and-api.md))

**Security & Governance:** `vw_datasource_attribute_security`, `vw_datasource_attribute_data_dictionary`, `vw_datasource_attribute_transformation`, `vw_datasource_attribute_genai`, `vw_datasource_schema_transformation`

**Integration & Code Generation:** `vw_datasource_active_attributes_semantic_layer`, `vw_datasource_active_attributes_gen_ai_semantic_model`, `vw_datasource_relationships_gen_ai_semantic_model`, `vw_datasource_queries_gen_ai_semantic_model`, `vw_datasource_foreign_keys`, `vw_datasource_relationships`, `vw_datasource_sql_code`, `vw_datasource_sql_code_summary`

**Monitoring & Diagnostic:** `vw_integration_process`, `vw_access_control_user_privileges` (app\_admin only)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.datapancake.com/core-concepts/views.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.