Getting started

Welcome to Expeed Relay. This is the help track — everything here is aimed at admins and managers configuring the dashboard, not developers integrating forms. If you’re wiring up a form on a website, you want the Developer track instead.

Log in

Go to relay.expeed.com, select Sign in, and enter your work email in the box that opens. Expeed Relay finds the organisation the address belongs to and takes you to its sign-in page, at your own address — something like yourcompany.relay.expeed.com. Sign in there with whatever method your organisation uses.

Once you know that address you can go straight to it next time; the email step exists only to find it for you.

If the same email address is used at more than one organisation, Expeed Relay cannot tell which one you mean and will say so. Go straight to your organisation’s address in that case — your administrator can tell you what it is.

Expeed staff sign in with their Microsoft account, from the link at the bottom of that same box.

First-time users. You must be added to Expeed Relay by an admin before you can sign in. If your credentials are accepted but Expeed Relay still rejects you with “User not found or inactive”, ask an Expeed Relay admin to add you — the steps are in Users & roles, which also explains what the admin, manager, and viewer roles can each do. If you were added but never received the email inviting you to set a password, use Forgot your password? on your organisation’s sign-in page to request it again.

After sign-in, you land on the dashboard.

Screenshot to come

The Expeed Relay dashboard immediately after sign-in, showing recent submission and job activity with the sidebar on the left.

What you’ll see

The left sidebar is grouped:

Dashboard — at-a-glance stats across everything below.

Configure

1. Sites — every website that submits to Expeed Relay gets one site. Holds its allowed origins, CAPTCHA settings, and provider credentials.
2. Forms — each form on a website has one entry here, with its recipients (who gets notified) and templates (what they receive).

Monitor 3. Submissions — every submission Expeed Relay has received, filterable by site and form. Exports to CSV. 4. Jobs — every notification Expeed Relay has attempted to send. Failures and their reasons live here, and you can retry by hand.

Access 5. Users — manage who can access Expeed Relay and at what role. Admins only. 6. API Keys — for server-to-server integrations. Issued per site and hashed at rest. Admins and managers. 7. Account Activity — a record of every occasion Expeed support entered your organisation, with the reason given and who did it. Admins only.

Three of those are role-gated: Users and Account Activity are visible to admins only, and API Keys to admins and managers. If you don’t see them, that’s your role, not a bug.

Everything you see is your organisation’s, and only yours. Sites, forms, submissions, jobs and users all belong to the organisation whose address you signed in at. There is no view that crosses from one organisation to another, and a session issued for one is refused at another’s address.

Expeed support can enter your organisation to help you, and cannot do so invisibly: every occasion is recorded on Account Activity, with the reason, the person, and the time. That page is yours to read, not a support-side log.

What to configure next

For a brand-new website integration, work through these in order. Steps 1, 2 and 4 require the admin role — a manager can do the rest within their assigned sites, but cannot create a site, configure a provider, or change the CAPTCHA settings.

1. Register the site — set its name, site key, and allowed origins.
2. Configure a provider — an email provider is the minimum; WhatsApp is optional.
3. Create a form and add recipients — attach the people who should be notified and the template they receive.
4. Enable CAPTCHA — do this if the form is public and could attract bots.
5. Give the developer the site key, form key, and (if you enabled it) the CAPTCHA site key.
6. Watch delivery as the developer tests — submissions and jobs appear within seconds.

Don’t skip the provider step. A form with no configured provider accepts submissions and then fails every delivery. If jobs are piling up as failed, check the provider first.

Once the basics work, you can forward submissions to another system with webhooks, or let a backend service post submissions directly using an API key.

Related

• Creating a site
• Configuring providers
• Users & roles