Serve Your Portal on Your Own Domain
Put your portal on a domain you own, like portal.acme.com, with one DNS record and an automatic TLS certificate. Included on every paid plan.
A client clicking through to a portal on someone else's domain notices. It reads as a tool you bought rather than a service you run, and it is the one part of the experience your logo cannot fix.
A custom domain fixes it. The portal answers on portal.acme.com, or whatever you own, and nothing in the URL bar mentions us.
What it does
Each portal can have one custom domain. You add it in the portal's Domain tab, create a single DNS record at your registrar, and the portal starts answering there. It is available during the trial too, so you can see the finished thing before you pay.
- One DNS record: a CNAME for a subdomain, or an ALIAS or ANAME for a root domain
- TLS certificate provisioned and renewed automatically, so HTTPS just works
- The original collabportals.com URL keeps working alongside it
- Included on every paid plan and during the free trial, not a premium add-on
Why it matters
Two reasons, and the second one is the one people underestimate.
The obvious one is trust. External users are being asked to log in and, often, to submit information about themselves. A domain they recognize removes the moment of hesitation before they do.
The less obvious one is control. Because your collabportals.com URL keeps working, moving to a custom domain is not a cutover. You point the DNS record, test it, and start sending the new link. Links you already sent do not break.
How it works
Add the domain in the Domain tab, and CollabPortals shows the exact DNS record to create. Add that record at your DNS provider, and the domain is verified once it propagates, usually in minutes.
The certificate is issued and renewed for you. There is nothing to install, and nothing that expires in eighteen months when whoever set it up has left.
A root domain like acme.com needs a DNS provider that supports ALIAS or ANAME records. A subdomain like portal.acme.com works on any provider with a plain CNAME, which is why most people use one.
Full instructions, including the per-provider notes, are in the custom domains guide.
Who it is for
Anyone whose portal is client-facing rather than internal. Agencies and consultancies serving client portals, real estate teams sharing listings, and anyone whose portal sits behind a link in a contract or an onboarding email.
Try it on your own base
Connect Airtable, build a portal, and share it. Seven days free, no card needed.
Related guides and examples
Your Logo, Your Colors, Your Favicon
Brand the portal so end users see your company, not ours: a logo in the header, primary and background colors, and a custom favicon on the browser tab.
Use caseClients
Give your clients secure, branded access to their project data in Airtable. No extra seats, no code, no complex setup, just share a link.
ComparisonCollabPortals vs Softr: Lightweight Portal or Full App Builder?
Compare CollabPortals and Softr for Airtable portals. See how a $10/month focused portal tool stacks up against a full no-code app builder starting at $49/month.
GuideCustom Domains: Put Your Airtable Portal on Your Own Domain
Serve your CollabPortals Airtable portal on your own domain like portal.acme.com, with an automatic HTTPS certificate. Available on any paid plan. Here is how to set it up.