Definition: App Users (beta) is the settings surface inside every published Taskade Genesis app that lets you manage the app's end users independently from your Taskade workspace members. Where workspace members are the people who collaborate on building apps with you, app users are the people who use a specific published app โ a client portal's clients, a SaaS app's customers, an internal tool's team members. App Users ships as part of Taskade v6.151.
App Users closes the loop on the Genesis Auth story. Genesis Auth gives you sign-in; App Users gives you a directory of who can sign in, when they did, and how to remove them.
Why This Is a Big Deal
Pre-App-Users, a published Genesis app either had no auth (anyone with the link could use it) or used Genesis Auth but with no clean place to manage the user list. You could see signed-in sessions in logs but you could not invite, organize, or revoke at the app level.
App Users fixes this. Each published app now has its own user directory, managed from the app's settings page. The app has a lifecycle of its own users, separate from your Taskade workspace โ the way a real SaaS product does.
Two Distinct User Populations
Workspace members collaborate on building. App users use what you built. The two populations almost never overlap โ your client never needs to see your Taskade workspace, and your workspace teammates do not need to be listed as users of a client-facing app.
What App Users Shows
For each published app, the App Users panel displays:
| Column | Meaning |
|---|---|
| The user's sign-in identity | |
| Name | Display name (optional, collected at sign-in or provided on invite) |
| Last sign-in | When they last opened the app |
| Status | Active, invited (pending first sign-in), or revoked |
| Role | Per-app role if your app has role-based access |
The list is scoped to one app. Switching between apps in your Taskade workspace shows a different user directory each time.
Operations You Can Perform
- Invite โ Add a user by email. They receive a sign-in invitation.
- Bulk invite โ Upload a list, invite many at once.
- Revoke โ Remove a user. Their session dies immediately; they cannot sign in again unless re-invited.
- Re-invite โ Resend the sign-in link if they lost the original.
- Role assignment โ If your app defines roles, assign the user a role.
- Export โ Download the user list (JSON/CSV) for compliance or migration.
- Audit view โ See which users have actually used the app versus who was invited but never signed in.
Where This Plugs into Your App
On the server side, your Genesis app reads the authenticated user from the Genesis Auth session. On the client side, your app uses standard hooks to render the current user. App Users is the control plane that decides who is allowed to be one of those authenticated users.
App data is automatically scoped. If your app stores data per user (tasks, saved views, preferences), each user sees their own data. No leakage between accounts, no manual access control to write.
Use Cases
Client portals. One app per client engagement. Each client's users listed and managed separately.
Paid customer apps. Combine App Users with Stripe checkout automations. When a customer pays, invite them. When they cancel, revoke.
Employee tools. Invite the whole team. Revoke access on offboarding.
Community apps. Open sign-ups for a public community, moderate with revocation when needed.
Beta programs. Invite a cohort, track who actually uses the app, graduate active users to paid tiers.
App Users vs Taskade Workspace Members
| Workspace Members | App Users | |
|---|---|---|
| Scope | Your Taskade workspace | One published Genesis app |
| Who they are | Builders and collaborators | End users of the app |
| Role system | 7-tier RBAC (Owner โ Viewer) | Per-app roles you define |
| Billing | Count toward plan seat limits | Free, unless you monetize |
| Invitation | From workspace settings | From app's App Users panel |
| Overlap | Usually none | Usually none |
The key mental model: your workspace is where you build. Your app users are who uses what you build. Keep them separate in your head and the settings UI makes immediate sense.
How Cloners Handle Users
When your app gets cloned from the Community Gallery, the clone gets its own empty App Users list. The cloner is now in charge of their own app's users; your users stay yours. This is the correct isolation boundary: same code, different users.
Related Concepts
- Genesis Auth โ The auth layer App Users manages
- Genesis Apps โ What App Users governs access to
- App Publishing โ Where a private app becomes accessible to users
- Custom Domains โ Where your app lives
- Community Apps โ Cloning behavior
Frequently Asked Questions About App Users
What is App Users in Taskade Genesis?
App Users is the settings surface inside every published Taskade Genesis app that lets you manage the app's end users โ separate from your Taskade workspace members. Invite, revoke, and monitor who uses each published app.
How is this different from Taskade workspace members?
Workspace members are the people who build and collaborate on apps with you. App Users are the end users of a specific published app. The two populations are usually separate โ your clients are app users, your teammates are workspace members.
Do App Users count toward my Taskade seat limit?
No. App Users do not consume Taskade workspace seats. They are end users of your published app, not members of your Taskade workspace.
Can I bulk-invite App Users?
Yes. Bulk invite accepts email lists. Each invited user receives a sign-in link via Genesis Auth.
What happens when I revoke an App User?
Their current session terminates immediately and they cannot sign back in until re-invited. Any data they stored in the app remains unless your app explicitly deletes it.