Overview
Give your customers their own login. Your published Taskade Genesis app has its own users, separate from your workspace teammates. The App Users screen lists people after they sign in, and lets you search, disable, re-enable, or remove their access. Use the signed-in identity when you build filters for a portal or member area.
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, then appear in the app's user list. Search the list, disable or re-enable access, or remove an account. Pair with GenesisAuth and test explicit identity-based filters before publishing private customer data.
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 | www.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
- See people who signed in to the published app.
- Search the list by email.
- Disable or re-enable an account.
- Delete an App User when you no longer need the account.
- Build identity-aware screens by explicitly matching the signed-in user to the correct Project records.
This is the answer to "how do strangers safely use my app." Workspace members run the workspace. App Users use the app.
Add your first App Users
- Add GenesisAuth to the published app.
- Share the app's sign-in URL with the customer or member.
- Let the person create an app-specific account and sign in.
- Open App Settings → People & Access → App Users.
- Search for the email. The account must show an active status.
App Users does not currently send invitation or password-reset emails from this table. People create their app account from the published sign-in screen.
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 › People & Access › App Users [BETA] │
│ Manage the users of your Taskade 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 names show as a dash |
| 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
Once you have App Users, ask Taskade EVE to build explicit checks that match the signed-in identity to fields in your Project data. Sign-in confirms who the visitor is. It does not automatically hide unrelated Project rows.
Examples that work today:
- "Match the signed-in email to the customer_email field before reading a row."
- "Hide the internal database unless the signed-in person's email ends in
@mycompany.com." - "Return only Customers rows whose customer_email equals the signed-in email."
- "Test an unmatched account and show an empty state instead of the full Project."
Uploads from signed-in app users become part of the app's files, so an automation can read them and write the result back to that person's row. See Files from Your App's Users.
Say a clinic publishes a client portal. The clinic stores each customer's email on the relevant appointment rows and asks Taskade EVE to filter by the signed-in email. Before publishing, the builder tests two customer accounts plus an unmatched account. That configured match is what scopes the records; App Users alone is not a row-level permission system.
Common patterns
| Pattern | Identity rule | What App Users unlocks |
|---|---|---|
| Client portal | Signed-in email equals customer_email |
Personal dashboards after you configure and test the filter |
| Internal tool | Email domain allowlist | Company-only access to selected screens |
| Beta program | Email allowlist stored in a Project | Limit a feature to approved testers |
| Paid app | Customer email matches a paid order record | Gate premium screens after your Stripe automation updates the record |
| Education / cohort | Email matches an enrollment row | Different course content from one app |
Disable or remove a user
Use the row action to Disable an App User. To return access later, re-enable the account. To remove the App User record, choose Delete.
Disabling an App User does not delete separate Project rows, automation history, or uploaded files. Manage that data in its owning surface.
Tips that pay back
- Store the user email on every Project row that needs per-user filtering.
- Test two real identities and one unmatched identity before publishing private data.
- Pair signed-in email checks with a domain allowlist for company-only screens.
- 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 end users of your published Taskade Genesis app, kept separate from workspace teammates. Each person gets an app-specific login and appears in the App Users dashboard, where you can search, disable, re-enable, or delete the account.
Which plan do I need for client logins?
You do not need a specific plan. App Users and client sign-in work on every published Taskade Genesis app, on every plan including Free. What does need Business or above is putting that app on your own custom domain. See pricing for current details.
How do my customers sign in?
Customers create an account or sign in on your app's URL with their email. Share that URL directly. After a person signs in, the account appears in the App Users list.
Can each customer see only their own data?
Yes, after you configure and test an explicit identity-to-record filter. Ask Taskade EVE to match the signed-in email to a field such as customer_email, then test multiple accounts. Sign-in by itself does not scope Project rows.
How is this different from sharing a public link?
A public link can show the same screen to every visitor. App Users gives each person an identity that your app can use in explicit email, domain, or record-matching checks. Configure those checks before treating a screen as a private client portal.
Can I manage or remove users?
Yes. The App Users dashboard lists signed-in visitors and lets you search by email, disable or re-enable an account, or delete the App User record.
Related guides
- GenesisAuth. Email sign-in for the people who use your app.
- Files from Your App's Users. What happens to a file after someone uploads it.
- 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.