Search documentation

Search docs pages by title or description

Join the waitlist
Browse documentation

Templates & the sandbox

A template is a complete Emberblocks app: its own database with sample rows, a dashboard, boards, calendars or maps, roles, and a couple of workflows. Browse them at emberblocks.com/templates.

Three ways in

  1. 1

    Use this template (signed in)

    From the Apps page choose New app → Start from a template, or click Use this template on a template page. Emberblocks provisions a fresh Ember database for it, generates the app and loads the sample data — a few seconds. The copy is yours: rename it, delete the sample rows, change anything.
  2. 2

    Open in the editor (no account)

    Open in the editor starts a sandbox: a private workspace with the template already inside. Everything works — editing, preview, publishing, workflows — with small limits (no AI drafting, no external data connections, no invites). Sandboxes are deleted 24 hours after they start.
  3. 3

    Preview the live app

    Each template page links to a read-only public copy of the app's dashboard — a public link — so you can see the finished thing before touching anything.

Keeping a sandbox app

Built something in the sandbox you want to keep? Click Keep this app in the banner and enter your email. You receive a transfer link; open it, sign up (or sign in), pick a workspace and accept. The app moves with its database, versions and users — the same app transfer teams use between workspaces. A sandbox with a pending transfer stays alive until you accept.

Sample data and emails

Sample rows are ordinary rows — delete them or import your own CSV. The templates' workflows send email to addresses in the sample data (all @example domains); they only run in a published app, so nothing goes out until you publish with real data.

What every template includes

  • A Dashboard view with stat tiles, charts and one working surface (board, calendar or map).
  • One view per table, a record page with actions, and an add/edit form.
  • The starter roles — Admin, Editor, Viewer — plus a portal role where it makes sense.
  • Conditional formatting (style rules) and select-option colours.
  • One or two workflows: status-change emails, a daily digest, or an overdue flag.