Overview
Give your customers their own login. Your published Taskade Genesis app has its own users, separate from your workspace teammates. A solo realtor can run a marketing site plus a private inbound CRM where each lead signs in and sees only their own deal. The App Users screen is where you invite, list, tag, and revoke those people. Same place every time. Built into every app you publish.
TL;DR: App Users (beta) gives every published Taskade Genesis app a built-in admin surface for end users. Customers sign in with their email. You see who joined and when. Tag them as
client,beta-tester, or anything you invent. Revoke a seat in one click. Pair with GenesisAuth for sign-in and with Taskade Projects for per-user personalization. Free to try; paid-app access is gated on the new Stripe-backed App Kit.
Two layers, one workspace
Most builders trip on this once. Get it right early and the rest is easy.
| Workspace members | App Users | |
|---|---|---|
| Who | You + your team | The customers of your published app |
| What they touch | Projects, agents, automations, settings | Only the screens you published |
| Where they sign in | app.taskade.com |
Your app's URL (or custom domain) |
| Billing seat? | Yes, against your plan | No, separate count |
| Managed from | Workspace Settings | App Users dashboard in each app |
Think of it like a website. The workspace is your control panel where you build the app from your projects, agents, and automations. See Workspace DNA for how those three pieces fit together. The app is the public site itself. App Users are the people who visit and sign in.
What you can do with App Users
- Invite customers, clients, beta testers, or contractors by email.
- Tag them with roles you define (
client,vip,vendor, anything). - See every sign-in: provider, first seen, last active, status.
- Gate content in your app by tag, email domain, or signed-in identity.
- Revoke access on the next request without losing their history.
This is the answer to "how do strangers safely use my app." Workspace members run the workspace. App Users use the app.
Your first App Users in 90 seconds
- Open your published app and click Settings → App Users.
- Click Invite and paste one or more email addresses (one per line).
- Add a tag if you want to group them (for example,
clientfor portal access orbetafor early testers). - Click Send invites. Each invitee gets a sign-in link.
- Watch them appear in the Active list as they sign in.
That is the full loop. No deployment, no auth code, no third-party identity provider to configure.
The App Users table
The table shows every signed-in visitor:
Here is the App Users tab inside your published app's settings:
┌──────────────────────────────────────────────────────────┐
│ App Settings › App Users [BETA] │
│ Manage users who signed up through your Genesis app │
├──────────────────────────────────────────────────────────┤
│ Search by email ................. [ Search ] │
├──────────────────────────────────────────────────────────┤
│ EMAIL NAME CREATED STATUS │
│ ───────────────── ────────── ─────── ────────── │
│ [email protected] Maria Cole Apr 14 ● Active │
│ [email protected] J. Okafor Apr 18 ● Active │
│ [email protected] — Apr 22 ○ Disabled │
│ │
│ 128 users [ Load more ] │
└──────────────────────────────────────────────────────────┘
● Active · ○ Disabled — toggle any seat off in one click.
| Column | What it means |
|---|---|
| Verified email from the sign-in provider | |
| Name | Their display name (blank shows as —) |
| Created | When they first signed in |
| Status | Active or Disabled — toggle a seat off in one click |
| Actions | Disable or Enable a seat, or Delete it |
Search by email when the list grows, and load more as you scroll.
Gate content per user with Taskade EVE prompts
Once you have App Users, you describe access rules to Taskade EVE in plain English. Taskade EVE wires the checks into the app. No code to write.
Examples that work today:
- "Only show the Billing page to customers tagged
client." - "Hide the internal database unless the signed-in person's email ends in
@mycompany.com." - "Show every signed-in customer only their own row from the Customers project."
- "Let people tagged
vendorupload files but not see anyone else's uploads."
Say a mental-health clinic publishes a client portal. The clinic asks Taskade EVE to "show each signed-in client only their own appointments and notes." Every client lands on the same app, but each one sees only their own records. Taskade always knows who is signed in, so you can use that identity in your AI agent instructions and your automations too.
Common patterns
| Pattern | Tag scheme | What App Users unlocks |
|---|---|---|
| Client portal | client per customer name |
Personal dashboards, scoped data, branded sign-in |
| Internal tool | staff, admin |
Workspace-only access; gate destructive actions on admin |
| Beta program | beta, cohort-1, cohort-2 |
Roll features to one cohort at a time, revoke when GA |
| Paid app | paid, trial, expired |
Pair with the App Kit Stripe checkout for paid access |
| Education / cohort | student, instructor |
Different views and tools per role from one app |
Revoke a user
Click the row's overflow menu → Revoke. The next request from that user is denied. Their history (rows they created, tasks they completed, files they uploaded) stays intact in your Taskade Projects, so your records stay clean.
Re-invite the same email later if they should come back.
Tips that pay back
- Tag at invite time. Re-tagging 200 users in bulk takes longer than tagging the first 5.
- Set a per-app tag policy in your team docs so two admins do not invent two names for the same role.
- Pair
currentUser.emailchecks with a domain match for fast "team only" gates. - Combine App Users with App Analytics to see which roles actually use the app.
Frequently Asked Questions
What are App Users?
App Users are the real customers of your published Taskade Genesis app, kept separate from your workspace teammates. Each person gets their own login and sees only the screens you published, never your projects, agents, or settings. You manage them from the App Users dashboard built into every app, where you invite, tag, and revoke them.
Which plan do I need for client logins?
App Users for published apps are available on the Business plan and up. Free to try while you build, with paid-app access gated on the new Stripe-backed App Kit. See pricing for current details.
How do my customers sign in?
Customers sign in right on your app's URL with their email. You invite them by email and each invitee gets a sign-in link, so there is no code to write and no separate identity tool to set up. They appear in your Active list the moment they sign in.
Can each customer see only their own data?
Yes, that is the whole point. You describe access rules to Taskade EVE in plain English, like "show every signed-in user only their own row from the Projects database," and Taskade EVE wires the checks in. Each person then sees only what belongs to them.
How is this different from sharing a public link?
A public link is open to anyone who has it, so everyone sees the same screen with no sign-in. App Users gives each person a private account, so you can gate content by tag, email domain, or signed-in identity. That is what lets you run a real client portal where each customer has their own scoped view.
Can I manage or remove users?
Yes. The App Users dashboard lists every signed-in visitor with their email, name, sign-in date, and status. Toggle a seat to Disabled in one click, or open the row's overflow menu and choose Revoke to deny their next request. Their history stays intact in your Taskade Projects, and you can re-invite the same email later.
Related guides
- GenesisAuth. Email sign-in for the people who use your app.
- Publishing apps. How to ship the app your users will sign into.
- App Analytics. Track per-user activity over time.
- Collaboration. Workspace-side roles for your team.
- Custom Domains. Brand the sign-in URL your users see.