Your portal lives at your own web address, with your logo, your colors, and no share-link look about it. Clients who sign in at a page that carries your brand treat it as part of your business, because it is.
Client Portal Nexus is a live Taskade Genesis app embedded on this page, and it is exactly the kind of portal you would point a domain at. Work through it, then choose "Use this app" to clone it in about ten seconds and run the go-live steps below against your own copy.
The build gives you the sequence that takes a working app to a branded, public front door. You pick the address, point the record at the app, publish, and confirm the sign-in screen renders on the new domain. Around that sit the launch tasks people forget: applying the brand styles, writing the landing page copy, checking the portal on a phone, setting the sign-in redirect, testing with a real invited address, and preparing the announcement to your client list. Custom domains are available on Business plans and up, $25/mo billed annually, and you can buy a domain directly if you do not already own one.
The address itself does quiet work. A client who signs in at portal.yourfirm.com behaves differently from one clicking a share link, because the first reads as part of a business and the second reads as a document someone sent. That perception carries into how seriously they treat the content, whether they bookmark it, and whether they forward it internally to a colleague. Pair the domain with your logo on the sign-in screen and the portal stops being a tool you use and starts being part of what clients buy.
Workspace DNA runs the launch. Memory keeps the checklist and who owns each step. Intelligence, powered by 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers, drafts the landing page copy and the announcement email in your voice. Execution sends the announcement and the invite wave once you flip the switch.
The launch plan renders in every layout you need:
- Board view for moving launch tasks through ready, doing, and done
- List view for the sequential go-live checklist
- Calendar view for the launch date and the invite waves
- Table view for the register of domains, apps, and their status
- Plus Mind Map, Gantt, and Org Chart across the 7 project views
Automations carry the go-live. Connect Taskade automations so the launch date sends the announcement, the invite wave goes out in batches rather than all at once, and any client who has not signed in after a week gets a friendly nudge. With 100+ bidirectional integrations, your CRM pulls the client list in, while Gmail and Slack push announcements and internal status out.
Test the whole path on a phone before you announce anything. Open the address, sign in as a real invited user, and walk through the two screens clients will use most. A good share of first sign-ins happen on a phone between meetings, and a sign-in screen that works only on a desk is a launch problem you want to find yourself.
The AI agents in the app carry 34 built-in tools including web search and persistent memory. An agent reviews your landing page copy against your brand voice, checks that every link resolves, and drafts the frequently asked questions clients will send in week one.
Clone the app, invite the team, and the launch plan is yours. Sign-in and custom domains are on Business plans and up, and App Users is in beta.
Read Custom domains for the setup, Buy a domain if you need one, and Publishing for how apps go live. Start at Taskade Genesis. Pair this with Build a Branded Client Portal With Sign-In and Write the Portal Welcome and Sign-In Copy.
Frequently Asked Questions
Do I need to own a domain already?
No. Use one you own, or buy one during setup. See Buy a domain for the flow.
Can I use a subdomain of my main site?
Yes, and many teams prefer it. Something like portal.yourfirm.com keeps the portal visibly connected to your existing website while staying separate from it.
What plan is required?
Custom domains and client sign-in are available on Business plans and up, $25/mo billed annually. You can build and test the portal on a share link before you commit to the domain.
Will the sign-in screen show my branding?
Yes. Apply your logo, palette, and typography, and the sign-in screen renders as part of your site rather than a generic login page. See App styles.
Can I move the portal to a different address later?
Yes. Point the new address at the same app. Your data, users, and automations are unaffected by the change.
How should I roll out to existing clients?
In waves. Invite a small group first, confirm the sign-in and scoped views behave, then send the rest. The automation can batch the invites for you.
Does the portal work on a phone?
Yes, and it is worth checking before launch, because a good share of client sign-ins arrive from a phone rather than a desk.
What should I check the day after launch?
Who signed in, who did not, and whether anyone hit an access error. The first day tells you whether the invite copy worked and whether your scoping rules match reality, and both are cheap to fix in week one.
