Exception review
Turn warehouse-backed exception rows into a queue where operators correct values, add notes, and reviewers approve the outcome.
Features
Turn Snowflake tables into queues, forms, and approval paths
EntryLayer gives teams a controlled place to correct rows, review changes, collect related records, and keep the history that spreadsheets and side apps usually lose.
Workflow examples
Start with the work people are already doing outside Snowflake.
Find the spreadsheet, email chain, ticket queue, or side app that is carrying decisions about Snowflake data, then move that work into a controlled EntryLayer space.
Reference data corrections
Let authorized users request and review updates to values that downstream models, dashboards, and systems depend on.
Vendor or provider onboarding
Collect structured records, attach review status, and keep child checks or follow-up tasks connected to the parent record.
Forecast and planning adjustments
Replace ad hoc spreadsheet edits with a controlled process for proposed changes, approvals, and downstream extraction.
Master data stewardship
Give stewardship teams an interface for reviewing, correcting, and documenting changes to important operational records.
Operations intake
Capture work requests, clinical or finance intake, and operational follow-up without sending source context outside Snowflake.
Form generation
Point at a table, get a usable starting point
EntryLayer uses source metadata such as columns, keys, relationships, types, and comments to generate form sections, fields, dropdown structure, and layout. Builders refine the result instead of starting from a blank canvas.
Auto-detected field types
Column types, key metadata, and source comments shape the form fields, dropdown structure, and sections automatically.
Multiple source types
Start from a Snowflake table, import a CSV or Excel file, or create an empty form from scratch.
Generated form review
Form editor
Form editor
Design forms visually, then publish safely
Organize fields into sections and rows, set field types and dropdowns, and publish changes through a draft workflow. No code required.
- Drag sections and fields to reorder them
- Configure field types, labels, help text, and validation
- Save drafts and publish when ready, with full version history
- Add child projects to create parent-child form hierarchies
Review workflows
Submit, review, and approve instead of just collecting data
- Fill out and submit records through structured forms instead of spreadsheets.
- Route submissions through review, approval, and rejection steps.
- Track comments, field changes, access activity, and who did what as queryable data.
- Records become read-only during review so nothing changes mid-decision.
Approved submission
Virtual submissions from Snowflake
Virtual submissions
Browse Snowflake rows before they become local workflow records
When a project is connected to a Snowflake source, existing rows can appear as virtual submissions. Local workflow state is created when an allowed user starts work on a record.
- View source-backed work through the same grid and detail surfaces
- Open the drawer from the grid to inspect record details without losing the queue
- Materialize records only when workflow or editing requires it
- Filter between all source rows and records already in workflow
Validation and logic
Add rules that control what users see and can do
Use the visual rule builder or formula canvas to control field visibility, enabled state, and required validation based on other field values.
- Show or hide fields based on conditions (e.g., "hide Size when Part Type is Standard")
- Make fields read-only or required based on other values
- Use Logic Preview to see which rules are active on any submission
- Let Cortex suggest rules from field metadata and plain English builder instructions
Logic rule builder
Child records inside parent submission
Child projects
Connect related tables into parent-child workflows
Real operational work rarely fits a single flat row. EntryLayer lets builders link related projects so child records appear inside the parent context with join keys keeping the relationship legible.
- Auto-detect relationships from Snowflake table structure
- Link existing projects as children or create new ones
- View and edit child records inline within the parent form
- Support multi-level hierarchies (3+ levels deep)
SQL API and Cortex
Let admins and Cortex manage project configuration safely.
EntryLayer includes an admin-only SQL API for creating projects, editing drafts, configuring form design, managing access, and inspecting operational state from Snowsight or Cortex.
AI boundary
Cortex helps with structure, not source-row disclosure.
AI-assisted features are designed around metadata, field titles, field types, relationships, and the builder's own instructions. Source row values, submission values, secrets, and credentials should not be included in Cortex prompts.
What makes it different
Built for teams that need more than a generic form builder
Your Snowflake permissions apply
Queries run as the signed-in user. Masking policies, row-level access, and role hierarchy stay in effect.
Every change is tracked
Field-level change history, access logs, and workflow actions are recorded automatically and queryable.
Extract approved records with SQL
Use the installed app extract procedure and your own SQL to persist approved workflow data downstream.
AI helps, you decide
Cortex uses metadata and builder instructions to suggest forms and rules, while you keep full control over the final structure.
Alternatives
Use the right tool for the boundary you need to defend.
EntryLayer is intentionally narrower than a general internal-tool platform. That is the point: it focuses on Snowflake data entry, review, and operational history.
Spreadsheets and generic forms
Fast to start, fragile to govern
Useful for quick collection, but workflow state, row-level access, masking, audit history, and controlled extraction become separate cleanup projects.
Retool or Power Apps
Broad internal-tool builders
Great for many app patterns, but they sit outside the Snowflake Native App boundary and require a separate operational trust story.
Streamlit
Excellent for developer-built data apps
Streamlit is strongest when developers build Python apps. EntryLayer focuses on no-code forms, review workflows, and operator-facing records.
EntryLayer
Purpose-built for Snowflake data entry
EntryLayer keeps the interface close to Snowflake, generates the starting point, and records the history teams need to inspect later.
Next step
Ready to try it in your Snowflake account?
Open the live Snowflake Marketplace listing, set up your first admin seat, and create a form from your own tables in minutes.