How clients reach it
Your Portal lives atyour-workspace.assembly.com by default. If you’ve connected a custom domain, it lives there too — portal.yourfirm.com is a common pattern.
Either URL works for clients. Both deliver the same Portal.
What clients see
Each client sees only their own data. If you’ve messaged John and Jane separately, John sees John’s messages and Jane sees Jane’s. There’s no admin view, no shared queue, no other clients in the sidebar. The Portal is sliced per-client. For companies, the slice is per-company. Multiple clients at the same company see the same data — the same invoices, the same shared apps. This is the difference between client-level and company-level scoping, which the app builder asks about when you build a client-facing app.How custom-built apps render in the Portal
When you build a client-facing app, Assembly Studio generates a third view alongside the team views — a client-facing surface that appears in the Portal sidebar. The Portal version is usually visually distinct from the Dashboard version. It’s simpler, more focused, designed for the specific things a client does. Assembly Studio handles this differentiation by default; you can shape it further when you iterate.Previewing it
You can’t truly preview the Portal from the Dashboard — it’s a separate signed-in surface for a separate user type. To see what your clients see, sign in as a client. See Try the client experience for the setup.Custom domains
Connecting your own domain is the single biggest change you can make to how clients perceive the Portal. Without it, your clients seeassembly.com in the URL bar. With it, they see your domain.
Custom domain setup
Step-by-step in the Assembly Studio guide