Guides Overview
EntryLayer guides are organized around the jobs customers do after installation: finding projects, working records, building forms, configuring project behavior, administering Snowflake access, and using Cortex with the SQL API or the optional Snowflake-managed MCP server.
Start by role
Section titled “Start by role”| Role | Start with | Then use |
|---|---|---|
| End users | User Guide | Project Workspace, Submission Detail |
| Operators and reviewers | Workflow & Review | Submission Detail, Workflow States |
| Builders | Form Editor | Validation Rules, Project Settings |
| Relationship builders | Child Projects & Relationships | Form Editor, Data Lifecycle & Storage |
| Snowflake admins | Snowflake Integration | Admin Guide, Native App Security Model |
| Cortex users | Cortex SQL API Skill | Snowflake MCP Client Setup, SQL Procedures |
Common workflow paths
Section titled “Common workflow paths”| Job | Guide path |
|---|---|
| Learn the app after setup | User Guide -> Project Workspace -> Submission Detail |
| Build a project form | Form Editor -> Validation Rules -> Field Types |
| Run a review process | Workflow & Review -> Workflow States -> Submission Detail |
| Connect Snowflake source data | Snowflake Integration -> Source Objects & Semantic Views |
| Operate the installed app | Admin Guide -> Billing & Operations |
| Let Cortex administer projects | Cortex SQL API Skill -> Cortex & AI Boundary |
| Connect an MCP client | Snowflake MCP Client Setup -> Native App Security Model |
Before following a guide
Section titled “Before following a guide”EntryLayer access has several layers. A user can have an admin or build seat and still lack permission to read project data.
| Layer | What it controls |
|---|---|
| Snowflake app role | Whether the user’s Snowflake role can open or administer the installed app. |
| EntryLayer seat type | Whether the user can view, act, build, or administer product surfaces. |
| Project permission | Whether the user can read, edit, submit, delete, or manage project records. |
| Snowflake source grants | Whether Snowflake allows the user/app to see source metadata, rows, or values. |
See Seat Types & Licensing and Permission Model when an access result is surprising.
Marketplace-safe operating reminders
Section titled “Marketplace-safe operating reminders”- Source setup and SQL API source discovery are metadata-first.
- MCP is optional and uses a Snowflake-managed server over app-owned SQL API procedures.
- Do not put source row values, submission values, PII, secrets, or credentials into Cortex prompts.
ENTRYLAYER_ADMINis for controlled administration; it does not grant projectcan_read.- Replace
ENTRYLAYERin SQL examples with the installed app name if it differs.