Skip to main content

Customer Portal

The customer portal is the page your own customers sign in to. It carries your name, logo, and colours — not SaaSy's — and shows each customer only their own records, plus a flow for signing documents you send them. This page explains what they see and where you configure it.

What's included​

Your portal is assembled from capabilities enabled for your workspace. Each appears as a section on the customer's dashboard: Invoices, Appointments, Quotes, Documents, and Messages. A capability that is turned off does not render. If nothing is enabled, the customer sees a short note that there is nothing to show yet.

Where your customers reach it​

By default the portal is served on the shared host at portal.hellosaasy.ai/{your-slug}. You can put it on your own domain instead:

  1. Go to Settings → Branding and find the Customer portal domain card.
  2. Verify a domain first in the domain verification section above the card if you have not already — the picker only offers verified domains.
  3. Under Portal domain, choose your domain, or leave it on Use the shared host.
  4. Add the CNAME record shown — Type, Name, and Value are displayed for copying. Apex domains that cannot CNAME should use their provider's ALIAS or flattening record. TLS is provisioned once the record resolves.

If a designated domain stops being verified, the portal falls back to the shared host and the card tells you so. An address that does not match any tenant renders a neutral Portal not found page rather than revealing anything about your workspace.

Branding what they see​

Portal branding comes from Settings → Branding in your workspace.

  1. Set the Logo URL to a public image URL. If one is present, the portal header shows the image; if not, it shows your company name in your primary colour.
  2. Set the Primary color and Secondary color. These are injected into the portal as brand variables, so buttons and focus rings pick them up automatically.
  3. Add your Terms of Service URL and Privacy Policy URL.
  4. Select Save.

The browser tab of a customer's portal reads "Your company — Customer Portal", and portal pages are marked not to be indexed by search engines.

How a customer signs in​

Sign-in is passwordless. There is no password to issue or reset.

  1. The customer opens your portal address and lands on the Sign in page.
  2. They enter their email address and submit. The page always confirms that a link has been sent — it never reveals whether an address matches one of your contacts.
  3. They open the emailed link, which signs them in and drops them on their dashboard.
  4. Sign out is in the top-right of the dashboard.

An expired or already-used link shows "This sign-in link is invalid or has expired. Please request a new one." The customer can just request another.

What they can do in a session​

  • Invoices — select Pay on an invoice to be handed off to hosted Stripe checkout.
  • Quotes — a quote that is still open shows Approve and Decline. Quotes already accepted, rejected, or expired are visible but have no actions, and drafts never appear.
  • Messages — read the thread and send a reply from the message box.
  • Documents — view and open the files you have shared. Documents are read-only here.
  • Appointments — see upcoming and past jobs with their scheduled times and service address.

The signing flow​

Documents you send for signature can be signed two ways. A customer who is signed in sees an Awaiting your signature section in Documents with a Sign action. Someone who has no portal account signs from a link you email them, which opens a standalone page with no sign-in and no portal branding — the single-use token in the link is the only credential.

Both routes run the same ceremony:

  1. The document is shown inline. Where you have placed signature fields, the actual pages render with read-only markers at each field position; otherwise there is a plain preview and a View document link.
  2. The signer ticks a consent checkbox agreeing to sign electronically. Nothing can be submitted until they do.
  3. They adopt a signature — Type their full name in a signature font, or Draw one on the canvas, with Clear to start over. The adopted signature previews in the markers where it will land.
  4. They select Sign document, and see Signature complete once it is recorded and the signed document has been finalised.

Decline is available throughout, and recorded as such. A link that has expired, or a request already completed or declined, shows the appropriate state instead of the form. Consent, the adopted signature, and the outcome are all recorded against the request; see E-Signature for what the module keeps.

Availability​

The portal reflects what your workspace already has: capabilities appear as the underlying features are enabled for you, and the portal itself needs no separate purchase. E-signature is its own module — see Modules, packs, and plans if a section you expected is missing.

SaaSy is not a legal advisor. Confirm signature requirements for your jurisdiction and use case with a qualified professional.