Seed Types

Seeds in Reseed are identified by icons that indicate their type and access level. Understanding these types helps you choose the right structure for your data collection needs.

Overview

Every Seed in Reseed has a type that determines who can access it and how it can be modified. The icon displayed next to each Seed's name indicates its type:

• 🔒 (Lock) — System-locked Seeds
• 🌱 (Sprout) — Single-role Seeds
• 👥 (Two people) — Multi-user Seeds (guest view)
• 🔑 (Key) — Multi-user Seeds (owner view)

System-Locked Seeds (🔒)

Seeds with the lock icon are system-locked and cannot be edited or deleted (though they can be cloned). These Seeds exist to support Reseed's core functionality:

• in_app_roles — Used for bulk importing in-app roles via CSV upload
• in_app_assignments — Used for bulk importing user-to-role assignments via CSV upload

These Seeds allow app_admin users to quickly load and create many in-app roles and assignments by uploading CSV files instead of creating each one individually in the UI. The bulk import process is covered in a separate guide.

Single-Role Seeds (🌱)

Seeds with the sprout icon are single-role Seeds, meaning only the owner (the in-app role that owns the Seed) can access them. These are the most common type of Seed.

The sample Seeds that come with Reseed (sample_budget_requests and sample_row_level_security_map) are single-role Seeds. You're free to edit or delete them, but we highly recommend cloning them instead so you can reference the originals in the future.

Single-role Seeds are ideal when:

• Only one team or department needs to upload files
• You want to keep data isolated by role
• You're setting up a new data collection process and want to start simple

Multi-User Seeds (👥 / 🔑)

Multi-user Seeds allow multiple in-app roles to access the same Seed. The icon you see depends on your relationship to the Seed:

• 👥 (Two people) — Shown when you're a guest user with access to the Seed
• 🔑 (Key) — Shown when you're the owner of the multi-user Seed

Multi-user Seeds enable collaboration scenarios where multiple teams or departments need to upload files to the same data collection point while maintaining appropriate access controls.

Multi-user Seeds are ideal when:

• Multiple teams need to contribute to the same data collection
• You want centralized data while maintaining role-based access
• Different departments need to upload to a shared Seed but should only see their own files