Creating a site

A site is how Expeed Relay represents one website. Every form that submits to Expeed Relay belongs to a site, and the site is where you configure the things that apply to the whole website: which browser origins may submit, which delivery providers to use, and whether CAPTCHA is required.

Create one site per website. If you run example.com and careers.example.com as separate properties with separate contact forms, they are two sites — that keeps their credentials, origins, and access lists independent.

Register a new site

1. Open Sites in the left sidebar and click New site.
2. Enter a Name. This is the human label you will see everywhere in the dashboard — use the website’s real name, like “Expeed Marketing Site”.
3. Enter a Site key. This is the identifier the developer puts in their integration code. Use lowercase and hyphens, like expeed-marketing.
4. Add your Allowed origins — one entry per browser origin that will submit forms. Leaving this empty disables origin checking altogether, so only do that if submissions come exclusively from a server.
5. Click Create site.

Those three are all the dialog asks for. Everything else about a site — Requestor name and Requestor email, the CAPTCHA settings, the Active toggle, and its providers and forms — lives on the site’s own page, which you reach by clicking the new row. Nothing there is required to start receiving submissions, and a new site is active by default.

Screenshot to come

The New site dialog with Name, Site key, and Allowed origins filled in

Origins must be exact. An allowed origin is a scheme plus a host plus an optional port — https://example.com, not example.com and not https://example.com/contact. A path or a trailing slash will not match and the browser’s submission will be rejected. If the site is served on both the apex and www, add both.

What to configure next

A site with no providers cannot deliver anything, so the order matters:

1. Add at least one delivery provider — see Configuring providers.
2. Create a form and attach recipients — see Forms & recipients.
3. If the form is public, turn on CAPTCHA — see CAPTCHA setup.
4. Give the developer the Site key and the form’s key so they can wire up the integration.

Editing an existing site

Open Sites and click any row to reach the site detail page. The General tab holds everything about the site, not only what the creation dialog asked for — Name, Site key, Allowed origins, Requestor name and Requestor email, the CAPTCHA fields, and the Active toggle. Change what you need and click Save changes. The Providers and Forms tabs beside it are covered in Configuring providers and Forms & recipients.

Two things behave differently after creation:

• Site Key cannot be changed. It is baked into the developer’s integration code, so changing it would silently break every live form. If you truly need a different key, create a new site and migrate the forms.
• Deactivating a site (turning Active off) stops it accepting new submissions immediately. Existing submissions and their delivery history stay visible. This is the safe way to pause a website without deleting anything.

Only admins can create, edit, or delete sites. Managers and viewers see the site detail page in read-only form. See Users & roles for what each role can do.

Deleting a site

Deleting happens in two quite different forms, and the difference matters more than the interface suggests.

The delete button deactivates — it does not destroy

The trash icon on the Sites list performs a soft delete. The site is marked inactive and nothing else happens: every submission, delivery job, form, recipient, template, webhook, API key, and provider configuration is retained exactly as it was. The site stops accepting submissions, and it disappears for managers and viewers.

Deactivating also stops deliveries that were already queued. Anything still waiting to be sent for that site is abandoned rather than delivered, and retrying such a job by hand will refuse too. So switching a site off genuinely stops the sending, not just the receiving.

Setting Active back on from the site’s General tab reverses it completely.

The site comes back on refresh — that is the soft delete working, not a failed delete. The row vanishes from your list the moment you confirm, but reload the page and it returns, because admins see inactive sites as well as active ones. Check the Active column: it will read Inactive. Managers and viewers stop seeing it entirely.

Permanent deletion

Erasing a site for real is a separate, deliberate operation that is not exposed in the dashboard. There is no button for it. If you genuinely need a site and its history erased — a decommissioned property, a data-retention request — ask your Expeed Relay administrator to run it against the API for you.

Permanent deletion destroys the record of what your website received, not just the site’s settings. It erases, with no archive and no undo: every submission the site ever captured, every delivery job recording what was sent and to whom, all forms with their recipients, templates and webhooks, all API keys, all provider configurations, and every user’s assignment to the site. If anyone might later need to know who contacted you through that website, export the submissions to CSV first — see Submissions & jobs. Once this runs there is nothing left to export.

In almost every case the soft delete is what you actually want. Deactivate, leave it a while, and only erase once you are certain nobody needs the history.

Troubleshooting

• The developer says submissions return “not found”. This single message covers several distinct causes, deliberately — Expeed Relay does not reveal which one, because a detailed error would let a stranger probe for valid site keys. It means one of: the site key is wrong, the form key is wrong, the site or form is deactivated, or the browser’s origin is not in Allowed origins. Work through them in that order.

An origin that is not allowlisted produces no clue that origins are the problem. The developer will see the same generic “not found” as they would for a misspelt site key, so they can easily spend an afternoon checking keys that were correct all along. If the keys are definitely right and the site is active, suspect the origin next — and compare it character by character against Allowed origins, including the scheme and any port.

• Submissions worked yesterday and stopped today. Check the Active toggle on both the site and the form before anything else. A deactivated site returns the same “not found” message as a wrong key.
• The site is missing from a colleague’s list. They are a manager or viewer and the site is not in their Site assignment, or the site is inactive — non-admins do not see inactive sites at all. See Users & roles.

Related

• Configuring providers — the next step for any new site
• Forms & recipients — create the form that actually collects submissions
• Users & roles — grant colleagues access to the site you just created
• Getting started — the dashboard tour, if you need to get your bearings