For the complete documentation index, see llms.txt. This page is also available as Markdown.

Add Login & Roles

Add secure sign-in and access control to your Taskade Genesis app so the right people see the right things — no code, no third-party auth provider.

Taskade Genesis apps can ship with real user accounts and secure sign-in built in, powered by GenesisAuth. To add login, you don't configure anything — you describe the need when you build the app (for example, "users can sign in to see their own dashboard"), and Taskade Genesis wires up the sign-in component, session handling, and per-user data access automatically.


When to use what

GenesisAuth is part of a broader access-control story. Pick the control that matches who needs to get in and how locked-down it has to be. Every option below is no-code.

Control
What it does
When to use

GenesisAuth (App Users)

Account-based sign-in for your app's end users

Any multi-user app — external clients, members, or customers

Workspace SSO

Lets your Taskade workspace members sign in with their existing identity

Internal tools for your own team

Password-protected public links

A single shared password on a link

A quick gated preview

Private / Unlisted visibility

Controls whether the app can be discovered

Non-indexed, share-by-link only

Public agent tool opt-out

Keeps sensitive tools workspace-only

Apps that publish an AI agent

For external customers and members, reach for App Users. For your own staff, Workspace SSO means no second account to manage. For a fast, low-stakes gate, a password-protected link is enough.

The App Users tab is currently in Beta and rolling out across paid plans.


How to turn it on

You won't find a switch to flip — you ask for it in plain language.

  1. In Taskade Genesis, describe an app that needs accounts. Include phrases like "a client portal where each client has their own dashboard" or "a members-only knowledge base."

  2. Taskade Genesis generates the app with the sign-in component already in place.

  3. Open your app's settings and go to the App Users tab to invite people, suspend access, or remove accounts.

If your first prompt didn't add login, you can ask Taskade Genesis to "add sign-in for users" later while editing the app.

For the full walkthrough — the App Users tab, Workspace SSO, custom-domain sign-in, and the security model — see the source page:

GenesisAuth

Give each user only their own rows

For a client portal or member app, signed-in users usually shouldn't see each other's records. Turn on Private per-user data (row scoping) when you publish:

  1. Open your app's publish menu and enable Private per-user data. (The option appears for apps built on the current app template with sign-in enabled; turning it on rebuilds and republishes the app.)

  2. Pick — or add — a dedicated field on your project that stores each row's owner. Rows created through the app are tagged to the signed-in user automatically.

  3. Publish. Each signed-in user now sees only their own rows. Rows with no value in the owner field are hidden from app users entirely — the safe default.

Before you launch, sign in as a test user and confirm they see only their own records — this pairs with the go-live checklist item on per-user data isolation. Data you add inside Taskade (rather than through the app) won't have an owner tag, so it stays hidden from app users until you assign one.


Pair it with a custom domain

GenesisAuth works on apps hosted at your own web address with no extra setup. Combining sign-in with a custom domain gives end users a fully branded, production-ready product.


Next steps

Last updated

Was this helpful?