Getting the right people into the portal, on the right screens, takes a paste of email addresses and a tag. You are not configuring an identity provider or writing a permissions matrix. You invite, you tag, and the app decides what each group sees.
Client Portal Nexus is a live Taskade Genesis app embedded on this page and a practical place to start. Open it, look at how a signed-in surface is structured, then choose "Use this app" to clone it into your workspace and start inviting your own list.
The build gives you a working access layer. App Users is the screen inside your published app where you invite people by email, one per line, and assign a tag such as client, vendor, vip, or beta. Everyone who signs in appears in the table with their email, name, when they first signed in, and whether the seat is active. Tags are yours to invent, and they are what your gating rules read: people tagged client open the billing and documents tabs, people tagged vendor open work orders only. App Users are counted separately from your workspace members, so inviting two hundred clients does not touch your team seat count. App Users is in beta.
Tag design is worth ten minutes of thought because everything downstream reads it. The pattern that holds up is one tag for what someone is, such as client or vendor, and one for what they are entitled to, such as a tier or a module. Two dimensions cover almost every rule you will want, and they stay readable when the roster reaches two hundred people. What does not hold up is a tag per client, which turns your access rules into a list you have to maintain by hand every time you sign someone new.
Workspace DNA holds the structure. Memory keeps the roster and the tags. Intelligence, powered by frontier models from top AI labs, turns your plain-English access rule into the check the app runs. Execution sends the invites, records each sign-in, and applies the revocation on the next request.
The roster renders in every layout you need:
- Table view for the full user list with tag, status, and last active
- Board view for grouping people by tag or account tier
- List view for a simple per-account membership summary
- Org Chart view for mapping who belongs to which client organization
- Plus Calendar, Mind Map, and Gantt across the multiple project views
Automations handle the joining and leaving. Connect Taskade automations so a signed contract invites the client contact automatically, a new tag opens the right screens, and an account marked closed disables the seat. With 100+ bidirectional integrations, your CRM and billing tools pull membership signals in, while Gmail and Slack push invites and confirmations out.
Invite in waves rather than all at once. A first group of ten tells you whether the sign-in copy works, whether the scoped view is right, and whether anything in the invite email is confusing. Fixing that before you send four hundred invites is the difference between a smooth launch and four hundred confused replies.
The AI agents in the app carry built-in tools including persistent memory. An agent can audit the roster on request and tell you which invited people never signed in, which accounts have no contact at all, and which seats have gone quiet for ninety days.
Clone the app, invite your team, and the roster is yours. Client sign-in works on every plan, and custom domains are available on Pro plans and up, $10/mo billed annually.
Read App Users for the full walkthrough, Taskade Genesis Auth for how sign-in works, or App permissions for the project side. Start at Taskade Genesis. Pair this with Show Each Client Only Their Own Records and Revoke and Offboard Portal Access Cleanly.
Frequently Asked Questions
Do app users take up my workspace seats?
No. App Users are the end users of your published app and are counted separately from workspace members. Your teammates are workspace seats. Your clients are app users.
Can I invite people in bulk?
Yes. Paste a list of email addresses, one per line, add a tag for the group, and send. Each person gets a sign-in link and appears in the table as they join.
What tags should I use?
Whatever matches how you actually think about your customers. Common sets are client, vendor, vip, and beta, or a tier such as standard and enterprise. Tags are labels you invent, and your gating rules read them.
Can I see who has actually signed in?
Yes. The table shows first seen and status per person, so invited-but-never-signed-in is visible at a glance. That is usually the list you want to follow up on.
How fast does revoking access take effect?
Access ends on the person's next request. Their history stays in the app, so your records and reporting are unaffected by removing a seat.
Can a client invite their own colleagues?
You can allow it. Give an account owner a form that submits a colleague's email for approval, then have an automation issue the invite once you approve. That keeps growth self-service without losing control.
Which plan do I need?
Client sign-in is included on every plan, and custom domains are on Pro plans and up, $10/mo billed annually. You can build and preview the app on any plan, including Free, which includes 3 Taskade Genesis apps and starts with no AI credits (earn free AI credits as you go).
How many tags should I create?
Fewer than you think. One tag for the type of person and one for their tier covers most portals. If you find yourself creating a tag per client, the rule you actually want is probably a field on the account record instead.