Set site-wide operations defaults

You load the tab that saves site-wide operations settings through the dashboard.

1. Sign in with settings access (Primary Owner or full-access Manager).
2. Open Settings → Operations.

Reports and timestamps follow the zone you store here.

1. Locate the timezone control (select or text field depending on build).
2. Choose the zone that matches how your business reads charts.
3. Save the Operations form.

Staff notifications inherit these values when a form leaves its own subject or signature blank.

1. Fill the default email subject line.
2. Fill the email signature block used on staff notifications where implemented.
3. Save, then send a test submission from a form that relies on defaults.

Intake rejects submissions that match configured substrings or addresses before insert when your rules say so.

1. Edit Blocked names using the delimiter rules shown beside the field.
2. Edit Blocked IP addresses in the same section.
3. Save, then submit from a known-good client to confirm normal traffic still passes.

You set how many submissions from one IP may occur inside the sliding window before further posts are blocked.

1. Find Max submissions before block and the related time window fields.
2. Use conservative numbers in production; loosen them on staging if testers share one IP.
3. Save the Operations form.

Inbox filters, performance widgets, and status updates all validate against this list.

1. Locate the lead status editor (labels and colours).
2. Align names with the vocabulary your team already uses.
3. Save, then open Inbox and confirm filters still make sense.

Operations stores up to ten HTTPS destinations with per-row toggles; payload shape is fixed in code.

1. Open the Outbound webhooks accordion.
2. Leave Enable outbound webhooks unchecked until each URL is ready.
3. Add or edit rows following the Webhooks setup checklist for field-by-field detail.
4. Check Enable outbound webhooks and save when every row is tested.

Multi-email forward (directory routing) is not configured on this tab. Enable it per template under Settings → Forms → Configure → Advanced settings → Use multi-email forward, then follow Notifications to generate signed recipient tokens in PHP. It is separate from department routing (visitor Department field Choices in the form builder).

When enabled, the form builder exposes a Payment field type that sends visitors through hosted checkout (Stripe). WCKD Forms never stores card numbers.

1. Open the Payment collection accordion.
2. Check Enable payments when your install should accept paid submissions.
3. Set test or live mode, default currency, and tax presets (or Stripe Tax) as shown in the UI.
4. Follow the Stripe setup steps in that section: paste API keys into the private config fields, register the read-only webhook URL in Stripe, and add a Payment field to a form template.
5. Save Operations, then review collected payments under the Payments nav item when it appears.

Lite sites can post into this dashboard only when the intake API accepts satellite submissions.

1. On Settings → Operations, open the WCKD Forms Lite integration accordion.
2. Check Allow WCKD Forms Lite (other sites) to POST to this install's intake API.
3. Save Operations after changing the checkbox.
4. Copy the routed public intake URL and ingest key shown in that section into the Lite installer on the other site.
5. Follow WCKD Forms Lite for the full Lite setup, rewrite, embed, and schema-copy flow.

You confirm the dashboard and disk config agree after a save.

1. Reload Settings → Operations and confirm the values you entered are still present.
2. Submit a test lead and confirm timestamps use the timezone you expect.
3. Optional: if you maintain the server, spot-check the generated app config read-only after saving.