Does Heimdall Governance Studio upload catalogue data?

No. Catalogue parsing, governance configuration and SQL generation happen locally in the browser.

Which catalogue file formats are supported?

The application supports XLSX, XLS, XLSB, CSV and normalized JSON column-level catalogues.

Does the application execute SQL in Snowflake?

No. It generates review-gated SQL files for authorized users to inspect and execute through their approved Snowflake workflow.

Can automation approve governance decisions?

No. Suggestions and optional CoCo recommendations remain preliminary. Live-schema review, masking review and final governance approval must be confirmed by a person.

Heimdall Governance Studio | Snowflake SQL Generator

Turn your catalogue into governance-ready SQL.

Import a column-level data catalogue, guide every masking, classification, quality and access decision through human review, then generate a complete eight-file Snowflake governance package.

No catalogue uploads

No SQL execution

Human approval gates

Bring your own catalogue.

XLS

snowflake_catalogue.xlsx258 tables · 5,689 columns

Ready

Tables258Imported

Review prompts47Human review

Output08SQL files

CUSTOMER_IDNUMBERIdentifier

EMAILTEXTPartial mask

CREATED_ATTIMESTAMPFreshness

Step 1

Select and verify the physical table

Import a column-level catalogue, choose a table, then compare it with Snowflake before approving any generated scripts.

Catalogue source

Import your data catalogue

Upload an XLSX, XLS, XLSB, CSV, or normalized JSON file. The file stays in this browser and drives every table, column, review, and generated governance script.

Spreadsheet headers: TABLE_NAME, COLUMN_NAME, DATA_TYPE, IS_NULLABLE, and ORDINAL_POSITION. Optional DATABASE_NAME and SCHEMA_NAME default to DEV and RAW.

Drop catalogue here or choose a file from this device No catalogue imported yet

Find an imported table

Selected table

Nothing selected

—columns

—review prompts

—overrides

Schema review

Catalogue columns and live overrides

#	Column	Type	Nullable	Source	Include

I compared this list with the current Snowflake INFORMATION_SCHEMA.COLUMNS result.

Step 2

Review classification and masking

Suggestions are deterministic review prompts. Nothing is selected automatically.

Column	Type	Review prompt	Semantic category	Privacy category	GDF_PII tier	Reason

I reviewed every column, including free text, identifiers, consent fields and unsupported Boolean/Variant fields.

Step 3

Assign governance tags

Choose critical data elements and derived identifiers, then confirm the object-level tags.

Object tags

Source system Layer Retention

Selection guide

CDE identifies columns with approved business-critical meaning.

PII_DERIVED marks identifiers derived from or resolvable to a person.

Column	Type	CDE	PII derived

Step 4

Define data-quality controls

Keys and thresholds require evidence. Leave a metric unselected when it has not been proven.

DMF schedule Freshness timestamp Approved baseline Expected DMF results

Column metrics

Duplicate key

Null-count columns

Step 5

Document the table

Comments become Snowflake metadata. Business terms remain review evidence for Collibra or the chosen catalogue.

Approved table description Business terms

Step 6

Access and de-identification decisions

Record explicit decisions even when no policy or transformation is applied.

Operational context Readers to notify

Execution roles

Governance Warehouse Owner Ingest Data engineer Data modeler

Row access Attach an approved existing row-access policy Decision and reason

De-identification / load-time treatment Approved decision

Acceptance checks

Step 7

Review and generate

The generator creates SQL files only. It never connects to Snowflake or executes statements.

Validation

I confirm these decisions have the required governance, privacy and data-owner approval.

Configuration summary

Turn your catalogue into governance-ready SQL.

Bring your own catalogue.

From spreadsheet to reviewable SQL, without the governance guesswork.

Import the catalogue

Review every control

Generate the package

One workspace for the governance decisions that usually live everywhere.

Your schema is the starting point.

Classification and masking stay connected.

Define the checks before the code.

Approval is a product feature.

Ordered SQL files

Your catalogue stays on your side of the browser.

Know the boundary before you begin.

Make the next governance review structured, repeatable and reviewable.

Choose a table