Documentation

Install and Setup Quickstart

Install and set up Reseed in your Snowflake account. This guide is for the person performing the installation. Complete in about 10 minutes.

Prerequisites

Before you begin, ensure you have:

  • A non-trial Snowflake account on AWS or Microsoft Azure (commercial regions only)
  • The ACCOUNTADMIN role or privileges to install Marketplace apps. Reseed requires the CREATE DATABASE privilege, which is automatically granted with manifest version 2 during installation.
  • A spreadsheet file to upload (Excel .xlsx, Google Sheets export, or CSV)
Why Some Cloud Regions Are Not Supported

Reseed uses hybrid tables internally. If a cloud or region doesn't support hybrid tables, then it can't benefit from Reseed. Unfortunately, hybrid tables are not supported by Google Cloud, U.S. SnowGov Regions, or trial accounts. For details, see Snowflake's hybrid table limitations.

Step 1: Install Reseed from the Marketplace

  1. Go to the Reseed listing on the Snowflake Marketplace.

  2. Click Get to begin installation.

Understanding Snowflake's Overly Cautious Permission Screen

During installation, Snowflake may show a permissions screen listing all permissions that Native Apps could use. This screen reflects the maximum capabilities supported by the Snowflake Native App platform, not the privileges actually granted to Reseed.

Important: Reseed only creates and operates on objects explicitly defined in its setup scripts: a dedicated database (RESEED_DATA), schemas, tables, stages, and file formats. It does not create warehouses, compute pools, shares, listings, services, or external integrations.

Snowflake enforces all privilege checks at runtime and will block any operation not explicitly authorized by your account. You can safely click Agree and continue—Reseed will only use the CREATE DATABASE privilege to create the RESEED_DATA database.

You can see and double-check the actual privileges requested by Reseed on the Reseed Snowflake Marketplace page, which must align with the actual grants asked for and used by the app.

To learn more about Native App security, see the Snowflake Native App security overview.

Snowflake permissions required screen
  1. Choose the database name for the application (default: RESEED).

  2. Select the warehouse to use during installation.

  3. Approve the installation. Reseed requires only the CREATE DATABASE privilege, which is automatically granted with manifest version 2. You may need to acknowledge that some applications will be granted privileges automatically during install—these privileges are always explained on the app's marketplace page ahead of time.

  4. Click Get to complete the installation.

Installation typically takes 1-2 minutes. During installation, Reseed automatically:

  • Requests the CREATE DATABASE privilege (automatically granted with manifest version 2)
  • Creates a dedicated database (RESEED_DATA)
  • Creates schemas, views, optional materialized tables, and an internal stage
  • Sets up all core objects required for the app to function

Reseed creates a self-contained workspace in your account:

  • RESEED — The application database that exposes stored procedures
  • RESEED_DATA — A dedicated database containing:
    • RESEED_DATA.ACTIVE — Current views and optional materialized tables for query-ready data
    • RESEED_DATA.HIST — Historical views for all validated files, including outdated versions
    • RESEED_DATA.CORE — Internal stage and application tables

No manual SQL is required to install the app or begin using it as an administrator. Once complete, you'll see Reseed in your Apps section in Snowsight.

Step 2: Open Reseed

Click Open to launch the Reseed interface. The app is ready for the owner to use immediately; the application role setup for other users comes next.

Reseed Home dashboard showing navigation, events table, and stale users section
Page Navigation
Home Page: Events log
In-app Role selector
Filter Panel
Home Page: Admin Reports

The page navigation in the top left sidebar provides access to the app's pages:

  • Home — Your personal dashboard showing recent actions. If you're an app_admin, you can view and filter events for all users, and see lists of users and in-app roles with no recent activity.
  • Admin — (app_admin only). Here you can set up and manage in-app roles and user assignments.
  • Seeds — The primary workspace where you upload files, interact with existing files, and create or manage Seeds (the patterns and rules that govern file uploads). Available to both administrators and users. Sample seeds are included for learning: sample_budget_requests and sample_row_level_security_map.
Initial Access

Only the role that performed the installation (usually accountadmin) currently has access to Reseed. This role is considered the "app owner". By default, this role has access to all application roles used by the app. To allow other users to access Reseed, you'll need to grant them the appropriate application roles (Step 4 below).

App Owner Responsibilities

The installing role (often ACCOUNTADMIN) is the app owner. This role automatically inherits all application roles and can uninstall the app. Because Reseed creates the RESEED_DATA database, if you want to remove the app later, transfer ownership of the database and its objects to another role first. Do not run DROP APPLICATION RESEED CASCADE, which would drop application-owned objects and delete the data.

Step 3: Grant Application Roles

Reseed uses two application roles to control access to the app:

  • RESEED.APP_ADMIN — Manages Reseed's internal setup: in-app roles, user assignments, and system configuration
  • RESEED.APP_USER — Uses Reseed to upload files and (optionally) create and manage Seeds

You can grant these application roles to existing Snowflake roles, or create dedicated roles for Reseed. Below we show an example of creating dedicated roles, but you can also grant the application roles directly to any existing Snowflake roles.

USE SECURITYADMIN;

-- Create a role for Reseed administrators
CREATE ROLE IF NOT EXISTS RESEED_APP_ADMIN;
GRANT APPLICATION ROLE RESEED.APP_ADMIN TO ROLE RESEED_APP_ADMIN;
GRANT ROLE RESEED_APP_ADMIN TO ROLE SYSADMIN;

-- Create a role for Reseed users
CREATE ROLE IF NOT EXISTS RESEED_APP_USER;
GRANT APPLICATION ROLE RESEED.APP_USER TO ROLE RESEED_APP_USER;
GRANT ROLE RESEED_APP_USER TO ROLE SYSADMIN;
Role Hierarchy

Best Practice: If an administrator will also use Reseed as a normal user (uploading files, managing Seeds), consider granting them a separate Snowflake role with only reseed.app_user for day-to-day work. This follows the principle of least privilege—just as you wouldn't log into Snowflake always as ACCOUNTADMIN if you often perfrom ANALYST tasks.

💡 Warehouse Performance

Reseed runs well on an XSMALL warehouse. Individual actions in Reseed are simple and don't require large warehouses. If users experience lag, it's typically due to concurrency—multiple users competing for resources. In these cases, consider scaling out (enabling warehouse clustering) rather than scaling up to larger warehouse sizes. Clustering allows multiple compute clusters to work in parallel, which is often more cost-effective than a single larger warehouse.

🎉 Congratulations!

Reseed is now installed and set up in your Snowflake account. You've successfully completed the quickstart!

Suggested Next Steps

Now that Reseed is installed, here are the recommended next steps:

Try the Sample Seeds

Reseed includes sample seeds for learning: sample_budget_requests and sample_row_level_security_map. Open the Seeds page, enable Seed Admin Mode, and clone a sample seed to explore configuration options and validation behavior. You can safely upload invalid data to observe validation errors.

Need Help?

Questions, feedback, and feature requests are always welcome at support@reunionstudio.io.