Overview
Your published Taskade Genesis app has its own users, separate from your workspace teammates. The App Users surface is the admin dashboard where you invite, list, tag, and revoke them. 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 email, Google, Microsoft, or single sign-on. You see who joined, when, and from which provider. 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 admin panel — where you wire up the site. 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:
| Column | What it means |
|---|---|
| Verified email from the sign-in provider | |
| Provider | Google, Microsoft, single sign-on (SSO), or email magic link |
| First seen | When they first signed in |
| Last active | Most recent sign-in |
| Tags | Labels you attached during invite, or added later |
| Status | Active, invited, or revoked |
Filter the table by tag, status, or provider when the list grows. Export a CSV for record-keeping.
Gate content per user with Taskade EVE prompts
Once you have App Users, you describe access rules to Taskade EVE in plain English. EVE wires the checks into the app. No conditional-logic code to write.
Examples that work today:
- "Only show the Billing page to users tagged
client." - "Hide the admin database unless
currentUser.emailends in@mycompany.com." - "Show every signed-in user only their own row from the Projects database."
- "Let users tagged
vendorupload to the Files page but not see anyone else's uploads."
The currentUser context is available to every layer of your app. Use it in agent prompts, automation filters, and project queries.
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.
Related guides
- GenesisAuth. Sign-in providers, magic links, SSO.
- 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.