Request and manage your Conterminal email addresses

Requesting an address

1. Open the panel. Go to Settings → Email aliases. On a phone, the settings page shows one area at a time: choose Email aliases from the Settings area menu at the top, because the anchor link alone will not reveal a hidden panel.
2. Find the request form. It sits in the Requests block under the address table, beside the line Platform admins review and activate new aliases. If you do not see a form, you are not a tenant admin — see below.
3. Choose the Purpose. The menu offers Delivery-order documents and LFD conversations. This choice is permanent for the resulting address; a purpose cannot be switched later.
4. Enter the Alias local part. Type only the part before the @conterminal.com suffix shown next to the field. The placeholder is allied. Use lowercase letters, digits, and hyphens; start and end with a letter or digit; keep it at least two characters and at most 63. Do not paste a whole address: the field rejects the @ outright and the browser will refuse to submit the form without saying why.
5. Add a Reason. The field is optional and its placeholder is Why this address is needed, but the reviewer sees only this text. Name the mailbox, customer, or terminal program the address is for.
6. Select Request alias. A green Email aliases updated banner confirms with The alias request queue was updated, and the pending request appears in the list below the form.

Names Conterminal will not issue

These local parts are reserved for platform infrastructure and are rejected for every workspace: abuse, admin, bot, dmarc, hostmaster, mail, mailer-daemon, no-reply, noreply, postmaster, root, security, support, and webmaster. Addresses are also unique across the whole platform, so a plain name such as dispatch@conterminal.com may already belong to another company. Prefer something specific to your business.

What happens after you request

Requesting is not provisioning. Your submission creates a pending request that a Conterminal platform admin reviews; nothing is reserved, routed, or usable until they approve it. There is no self-serve activation and no published turnaround in the product.

1. The request sits in Requests showing the requested address, its purpose, and your reason (or No reason provided).
2. On approval, Conterminal creates the address and immediately tries to provision mail routing for it.
3. Successful routing lands in one of two states: covered by the domain catch-all, or an individually provisioned route. Either one is fully deliverable.
4. The address then appears in the table above with Status Active, and it becomes usable for its purpose at that moment.

For an LFD address there is a second step after activation. The LFD listener itself appears under Settings → LFD email scanning only after platform provisioning and a forwarding test, and until then that panel reads Request an LFD conversation alias above. The connection appears here after platform provisioning and a forwarding test. A tenant admin can change the digest recipient and set the listener to Active or Paused only once forwarding is verified.

Reading Status, Routing, and Last sync

The address table has five columns on a wide screen, and the same five labels stacked in a card on a phone.

Alias

The full address, including the @conterminal.com domain. This is the string to hand to a sender or paste into a forwarding rule.

Purpose

Delivery-order documents or LFD conversations. Fixed when the address is created.

Status

Active means the address is live. Disabled means it has been retired and no longer accepts mail.

Routing

How mail reaches Conterminal. Covered By Catchall and Provisioned both mean delivery works; Pending, Failed, and Disabled do not.

Last sync

When routing for that address was last written — on successful provisioning, on a provisioning failure, or when the address was disabled — shown in your local time zone. It is not a mail-activity timestamp and does not move when messages arrive, so an old value on a working address is normal. Not synced means no routing write has ever been recorded.

An address is usable only when Status is Active and Routing is Covered By Catchall or Provisioned. That pairing is enforced in the database, so in practice any row you see marked Active is deliverable. The Routing column is worth reading anyway, because it tells you which of the two mechanisms carries your mail: a catch-all covering the whole domain, or a route created specifically for that address.

What the table deliberately hides

Addresses that are still being created, still being provisioned, or that failed provisioning are filtered out of this table entirely. So is the underlying routing error text. If the table shows No active or disabled aliases are registered for this workspace while you are certain a request was approved, that is the shape of a provisioning failure, not a display bug — treat it as a support question rather than retrying the request.

Who can request and cancel

Tenant admin

Sees the request form and the Cancel button on pending requests. This is the workspace role mapped from an Admin membership in your company.

Everyone else in the workspace

Sees the address table and the list of pending requests, but no form and no Cancel button. Managers, members, and collaborators are all read-only here.

The whole Settings page requires a company workspace. If you are signed in to a portal or personal context, Conterminal redirects you to the Access Denied page instead. Conterminal platform staff viewing your workspace are treated as ordinary members on this page and do not see the request form either; they act from the platform admin tools instead.

Cancelling a request

Select Cancel beside a pending request to withdraw it. Cancellation applies only to requests that are still pending and only within your own workspace.

There is no tenant-side control for turning an existing address off. Retiring an address is a platform action, after which the row remains in the table with Status Disabled so you can still see what the address was.

Troubleshooting