Overview
GenesisAuth gives clients and members an app-specific login, separate from Taskade workspace membership. Ask Taskade EVE to add it to a page and publish. Visitors sign in with their email, and the app can use that identity in filters and access checks you configure.
TL;DR: GenesisAuth adds secure email sign-in to a Taskade Genesis app. Visitors sign in on the app's URL without joining your Taskade workspace, then appear as App Users. Sign-in identifies the visitor. Configure and test explicit filters before you use that identity to scope private Project records. GenesisAuth is in beta and works on every plan.
When to use GenesisAuth
- Client portals that show a customer their own records
- Member-only dashboards, course hubs, or community pages
- Internal tools where access is gated to your team
- Any Taskade Genesis app that needs to know who is visiting
How people sign in
GenesisAuth gives every published Taskade Genesis app its own secure email sign-in. Visitors sign up or sign in with their email address, with no Taskade account required.
| What you get | What it means for you |
|---|---|
| Email sign-in and sign-up | Visitors sign in on your app's own URL, no Taskade account needed |
| Managed sessions | Short, secure sessions you can revoke any time |
| No backend to run | Taskade handles accounts, sessions, and signing keys for you |
| App Users built in | Every sign-in becomes an account you can search, disable, re-enable, or remove |
Looking for company single sign-on for your own team members inside Taskade? That is workspace SSO, included from the Business plan up, and separate from GenesisAuth.
Add GenesisAuth to a page
- Open your app in Taskade Genesis and ask Taskade EVE: "Add GenesisAuth to the homepage."
- Set up the sign-in in the right-hand panel. You can adjust it later.
- Publish the app. New visitors see the sign-in screen, returning visitors skip straight through.
What a new visitor sees on a gated page (returning visitors skip straight through). You manage sign-in from the panel Taskade EVE sets up when you ask it to add GenesisAuth:
┌────────────────────────────────────────────────────────┐
│ yourapp.com › Sign in │
├────────────────────────────────────────────────────────┤
│ [ Acme Client Portal ] │
│ Sign in to continue │
│ │
│ Email │
│ ┌──────────────────────────────────────────┐ │
│ │ [email protected] │ │
│ └──────────────────────────────────────────┘ │
│ Password │
│ ┌──────────────────────────────────────────┐ │
│ │ •••••••••••• │ │
│ └──────────────────────────────────────────┘ │
│ [ Sign in / Sign up ] │
│ │
│ Short, secure session · Taskade manages sign-in │
└────────────────────────────────────────────────────────┘
New visitors sign up with their email. Returning visitors sign straight in.
App Users
Every person who signs in becomes an App User (beta). Manage them from App Settings → People & Access → App Users: search the list, disable or re-enable an account, or remove it. The table does not currently send invitations or password-reset emails. See App Users for the full walkthrough.
Personalize by signed-in user
Ask Taskade EVE to match the signed-in email to a dedicated field in your Project records. Then test at least two user accounts plus an unmatched account before publishing private data. GenesisAuth identifies the person, but it does not automatically add row-level permissions to a Project.
From sign-in to a personalized view. GenesisAuth confirms who the person is, keeps them signed in for a short, secure session, and turns them into an App User. Your configured current-user filter then selects the matching records:
Security
- Every sign-in uses short-lived sessions, so stolen links stop working fast
- Taskade rotates signing keys on a fixed schedule, no action required on your end
- You never store or see raw passwords
- Disabling an App User blocks that account from signing in
Frequently asked questions
How do the people who use my app sign in?
The people who use your published Taskade Genesis app sign in with their email address on your app's own URL. They create an account or sign in, and you never run an auth server or manage passwords. Each person who signs in becomes an App User your app can personalize for. GenesisAuth is in beta and needs no upgrade: it works on any published app, on every plan. Publishing that app to your own domain is the part that needs Business or above. Company single sign-on for your own Taskade team members is a separate feature, workspace SSO, included from the Business plan up.
Do my app's users need a Taskade account to sign in?
No. App Users are separate from Taskade workspace members. They use the account created on the published app; Taskade workspace credentials do not open that app account, and no workspace seat is required. They become an App User, and your app can use their identity in filters and access checks that you configure and test.