⚓ FormDockAll docs →

Dashboard guide

How FormDock is organized, your first five minutes, and the step-by-step for every main action. For wiring forms into your site's code, see the integration docs.

The mental model

Your account
Workspace — one per client
Form — one endpoint + its settings
Submissions — stored first, spam-scored, then delivered as email + webhook
Your account
One sign-in (magic link — no password), one plan, one invoice. Everything below belongs to it.
Workspace
A container for one client or one project. Each workspace has its own forms, submissions archive, and monthly usage meter. Freelancers often need just one; agencies create one per client so leads, quotas, and handoffs stay cleanly separated.
Form
One endpoint URL (formdock.app/f/…) plus its settings: who gets notified, spam protection, redirects, webhooks, autoresponder, retention. A workspace can hold unlimited forms — contact page, quote request, newsletter signup, each its own form.
Submission
One entry someone sent through a form. Stored first, always — then spam-scored, counted against your monthly quota, and (if clean and within quota) delivered by email and webhook. Lives in the archive until you delete it or retention purges it.
Notification
The email a submission triggers, sent to the form's recipient list. Reply-To is set to the submitter, so answering the email answers the lead.

Your first five minutes

  1. Create a workspace — name it after the client or project (you can rename it any time).
  2. Create a form inside it — e.g. “Contact page”. Your email is pre-filled as the notification recipient.
  3. Copy the endpoint — the form page shows its URL with a Copy button and a ready-made HTML snippet.
  4. Point your form at it — set your HTML form's action to the endpoint (framework recipes in the docs), keeping the hidden honeypot field from the snippet.
  5. Send a test submissionfrom your site — it appears in the form's Inbox within seconds, and the notification email lands in your inbox.
  6. Then shape it:add the client as a recipient, set a redirect to your own thanks page, and you're production-ready.

How do I…

Route a client's leads to their inbox (keep your archive)
  1. Open the form → Settings → Notification recipients.
  2. Add the client's email — one per line. Add your own too if you want copies.
  3. Save. From the next submission, the client gets the lead email; every submission stays searchable in your dashboard either way.

This is the core agency workflow: the client answers leads from their inbox, you keep the audit trail and the export.

Review spam & rescue a false positive
  1. Open the form and switch to the Spam tab — the count shows how many were caught.
  2. Each entry lists why it was flagged (honeypot, keywords, links).
  3. Legitimate message caught by mistake? Click “Not spam” — it moves to the Inbox. Spam never triggered an email, so nothing was sent on its behalf.

Spam is quarantined, never auto-deleted — a false positive is never a lost lead.

Search submissions & export a CSV
  1. Open the form — the search box matches across all field values.
  2. Click “Export CSV” (top right) for the full history; columns are built from your actual field names.
  3. Use the export for client handoffs, CRM imports, or your own backups.
Send visitors to your own thanks page
  1. Form → Settings → “Redirect URL after submit” → enter e.g. https://client-site.com/thanks.
  2. Save. Non-AJAX submissions now land there instead of FormDock's default thanks page.
  3. Need a different destination for one specific form instance? Add a hidden _redirect input — it must point to your own site's domain.
Push submissions to another system (webhooks)
  1. Form → Settings → Webhook URL — every clean submission POSTs JSON there.
  2. Set a Webhook secret; each request is signed (X-FormDock-Signature, HMAC-SHA256 of the body) so your receiver can verify it came from us.
  3. Failed deliveries retry five times automatically with increasing delays.
Auto-reply to people who write in
  1. Form → Settings → Autoresponder → enable it.
  2. Set the subject and body (e.g. “Thanks — we'll reply within one business day”).
  3. It's sent to the submitter's email field, only for clean submissions.
Set data retention (GDPR housekeeping)
  1. Form → Settings → “Auto-delete submissions after (days)”.
  2. Submissions older than the window are purged automatically — set it once, compliance runs itself.
  3. For individual requests: delete any single submission from its row in the Inbox, instantly.
Watch your usage & understand the cap
  1. Every workspace shows a usage meter: submissions this month against your plan's cap (green → amber → red).
  2. Going over the cap never loses a lead: submissions are still accepted and stored — only notification emails and webhooks pause.
  3. Notifications resume when you upgrade or the month rolls over; everything received meanwhile is waiting in the dashboard.
White-label notification emails (Agency plan)
  1. Workspace page → Workspace settings → “Notification from-name”.
  2. Enter your studio's name — notification emails to your client now carry it instead of FormDock's, with no “powered by” footer.
Delete a form or workspace
  1. Form → Settings → bottom: “Delete this form and all its submissions”.
  2. Workspace page → Workspace settings → “Delete workspace and all its forms”.
  3. Deletion cascades immediately and permanently — export a CSV first if you need the records.

Stuck?

Check the integration docs for anything code-side, status.formdock.app if something seems down, or just write to us — the contact form runs on FormDock itself, so we definitely get it.