Customer portals

A portal is a page under your name where the people you send documents to can sign what is waiting for them and download what they have signed. They need no SignEnvoy account: they sign in with a link emailed to the address you already send to. Portals are a Pro feature, managed from the dashboard. They are not part of the API and there is no senv command for them.

Turning it on

Settings, then Portal. The page shows your portal address, copy-ready, in the form https://{slug}.portal.signenvoy.com (on staging, portal-staging.signenvoy.com). The slug is your workspace's and never changes, so the address is permanent: put it in your emails and on your website once. While the portal is off, the address shows nothing; emailed signing links keep working either way.

You can give the portal a name your customers see (by default, your company name), and "Preview as a customer" opens the sign-in page in a new tab the way a customer first sees it.

The page also states the visibility rule in full: "Anyone {you} has sent a document to can sign in with a link emailed to that address. They see only the documents addressed to them: ones waiting for their signature and ones they've signed."

Branding and the from-name

Your logo and accent color come from Settings, then Workspace, and apply to the portal, the signing page, and your emails. Logos are PNG or JPEG, re-encoded on upload (metadata stripped, at most 1024 pixels on the long side). The same page sets the name your email arrives from.

Every email SignEnvoy sends on your behalf comes from "{your name} via SignEnvoy", never from your bare name. The address is SignEnvoy's verified sending address. A message that claimed to be from you alone would be the shape of a phishing email, and your recipients are told on the signing page how to tell a real request from a fake one; the from-name rule is part of keeping that promise.

What customers see

The sign-in page carries your name and logo first and "Powered by SignEnvoy" second, small. Before asking for anything it says what the customer will find:

Enter the email address {you} sends your documents to. We'll email you a sign-in link. You'll see the documents addressed to that address: ones waiting for your signature, and ones you've already signed.

After they enter an address, the page says the same thing whether or not that address has documents from you: "If {you} has sent documents to that address, a sign-in link is on its way. It works for 15 minutes." No mail goes to an address you have never sent a document to, so the portal cannot be used to send email to strangers, and the page never reveals who your customers are.

The emailed link opens a page with one button, "Continue to your documents". The button signs them in; opening the link does not, so a mail client that prefetches links cannot use it up. The link works once and for 15 minutes; a used or expired link says so and offers a new one.

The document list has two parts:

• Waiting for you: documents addressed to this email that are not finished. "Sign now" appears only when it is this person's turn; otherwise the row reads "Waiting for an earlier signer". "Opening from here replaces the link in your email." is stated on the page: signing from the portal issues a fresh signing link, and the one in the earlier email stops working.
• Completed: finished documents with "Download signed copy" and "Download certificate". A document that has finished but is still being sealed says so and asks them to check back in a moment.

Voided, declined, and expired documents are not listed. Test documents and drafts never appear. A customer with nothing from you sees "No documents from {you} are addressed to this email yet."

Sessions

A portal sign-in is a session on that portal's address only. Your customer may also receive documents from another company using SignEnvoy; signing in to your portal does not sign them in to that company's, and nothing from one portal shows up on another. Sessions last 30 days and end with "Sign out".

Managing portal users

Settings, then Portal, lists everyone who has signed in, with their first sign-in and last access. "Revoke access" stops that person signing in to the portal and ends their current session; "Restore access" lets them sign in again. The page says what revoking does not do, and it is worth repeating here: "Revoking portal access does not affect their documents, signatures, or emailed signing links." A revoked customer can still sign from the link in their email, and anything they already signed stays signed.

Addresses that show nothing

An unknown slug, a workspace whose portal is off, a Personal workspace, and a deleted workspace all answer the same page: "This page isn't available." The page does not say which of those it is. Dashboard pages and the API are not reachable on a portal address, and portal pages are not reachable on the app's.

Not in the API

Portals have no /v1 routes and no CLI commands: the portal is something your customers use, not something your integration calls. Documents sent through the API appear in your portal like any other, addressed to their recipients' email addresses. Custom domains for portals (your own hostname in front of the portal address) are a later addition; the portal.signenvoy.com address stays valid permanently either way.