Projects, Collections, and Saved Schemas

Everything you save in ERD Factory sits under this hierarchy: your account has one or more Projects, each project can have Collections (optional folders), and each collection (or the project directly) holds Saved Schemas — each of which can accumulate its own version history.

Projects

The Dashboard is where projects live. First-time users get a one-field prompt to name their first project. From there, projects can be created, renamed inline, and deleted at any time. Opening a project takes you to its Project Home; deleting one always opens a confirmation dialog first (with item counts for a non-empty project) before cascading the delete through every collection, saved schema, and version inside it.

Saving a schema

The top-bar Save button persists the current DDL, schema name, dialect, and any per-table notes to your project. New saves start out uncategorized. If you’re saving over a schema that’s already been saved and the DDL has changed, Save opens a diff confirmation so you can choose between Update Existing (which appends a new version) or Save as New — it never silently overwrites.

Collections

Collections are optional folders for organizing saved schemas within a project, opened from the sidebar’s Saved (N) row. From there you can create a collection, rename it inline, delete it (schemas inside move to “Uncategorized” rather than being deleted with it), and move a saved schema between collections. Deleting a collection or a saved schema goes through the same request/confirm/cancel flow as project deletion, rather than deleting instantly on click.