Definition: Password protection lets you share a Taskade Genesis app, a project, an agent, or any public link with exactly the people you choose. You set a password, hand it out with the link, and only people who know it get in. Everyone else hits a locked door. It is the fastest way to keep client work, internal tools, and premium content out of public search while still sharing one simple URL.
You are already doing a version of this. A spreadsheet you only email to two people. A doc set to "anyone with the link." A folder you never quite trust to stay private. Password protection turns that instinct into one clear control.
TL;DR: Password protection gates any shared Taskade surface behind a password you set, so only people with the code can open it. For Taskade Genesis apps you also get built-in email logins via Taskade Genesis Auth and custom domains on Business and above. Pick public, password, or logins, then share securely →.
How Do You Password Protect an App or Project?
You password protect an app or project in three steps: open the share panel, turn on the password toggle, and set the code. Then you share the link plus the password with your audience. They enter the password once and the content opens. No account required, no public listing, and you can change the password anytime in the same panel.
What Can You Password Protect?
You can add a password to almost anything you share from Taskade: AI agents, intake forms, automations, project bundles, and Taskade Genesis apps. Any surface that produces a public link can be gated, so the same control covers a client dashboard, a sensitive workflow, and a premium agent you only want paying members to reach.
| What you share | Why password it | Where it lives |
|---|---|---|
| Taskade Genesis app | Client portals, dashboards, and tools you don't want indexed | App publishing |
| AI agent | Custom agents for clients or paying members only | AI Agents |
| Project or bundle | Templates and project sets with restricted access | Projects |
| Form or automation | Intake forms and internal workflows with sensitive data | Automation |
| Any public link | A quick lock on anything you're already sharing | Security & sharing |
Three Ways to Control Access
Taskade gives you three access models for shared work, and they layer cleanly. A public link is open to anyone who has it. Password protection gates that link behind one shared code. Built-in logins (Taskade Genesis Auth) give each person their own email sign-in, so you know exactly who opened the app. Pick the lightest control that fits the audience.
| Access model | Who gets in | Best for | Plan |
|---|---|---|---|
| Public link | Anyone with the URL | Marketing pages, free resources, community apps | Free+ |
| Password | Anyone with the shared code | Client work, premium content, beta groups | Free+ |
| Built-in logins (Taskade Genesis Auth) | Named users, each with email sign-in | Member portals, per-user access, gated apps | Free+ |
| Custom domain | Your own branded URL | White-label client and member portals | Business+ |
Taskade Genesis Auth uses email sign-in, so members get their own access without you provisioning accounts by hand. Custom domains with automatic SSL are available on Business and above, which is what turns a Taskade Genesis app into a branded portal at your own address.
SHARE PANEL
┌─────────────────────────────────────────────┐
│ Access │
│ │
│ ( ) Public link anyone with the URL │
│ (•) Require password ███████████ [ set ] │
│ ( ) Built-in logins email sign-in │
│ │
│ Link: taskade.com/share/apps/your-portal │
│ Code: ••••••••• [ copy both ] │
└─────────────────────────────────────────────┘
When Should You Use Each One?
Use a password when one shared code is enough: a client presentation, a beta test, a premium agent, a confidential project. Use built-in logins when you need to know who each person is, revoke one person without changing everyone's access, or run a true member portal. Use a plain public link only for content meant for everyone.
Reach for a password when:
- You're sharing client work or a presentation that shouldn't show up in search
- An internal tool or automation holds sensitive company data
- You sell premium content and want one code for paying customers
- You're beta testing with a small, trusted group for a fixed window
Reach for built-in logins when:
- Each person should have their own access you can grant or revoke
- You're running a client or member portal that people return to
- You want a per-user record of who opened the app, via App Users
A plain public link is the right call for general resources, open documentation, and apps you publish to the Community Gallery. For those, the goal is reach, not a gate.
Keeping Protected Content Secure
Password protection is one layer of Taskade's security model. The strongest setups combine it with the right access model and good habits. Use a unique, hard-to-guess code, share it only with people who need it, and rotate it for anything sensitive. For apps that connect to outside services, keep API keys in app secrets so they never appear in your shared link or front-end code.
- Strong, unique code. Mix letters, numbers, and symbols. Avoid anything guessable.
- Limited sharing. Hand the code only to people who actually need access.
- Rotate regularly. Change the password for sensitive content on a schedule, then tell your audience.
- Layer it. Combine password protection with role-based access (7 permission levels, Owner through Viewer) for fine-grained control on the project itself.
- Protect your keys. Saved API keys live in secure app secrets, never exposed in the shared app. Taskade runs a pre-publish secret check so nothing sensitive ships by accident.
Common Questions
Can I change the password after I share it?
Yes. Update it anytime in the share settings. The old code stops working immediately, so tell your audience the new one. Rotating the password is the cleanest way to cut off access for anyone who shouldn't have it anymore.
What happens if someone forgets the password?
They ask you for it again. You control access, so you resend the code. For per-user access where people sign in with their own email instead of a shared code, use Taskade Genesis Auth built-in logins.
Is there a limit on how many people can use one password?
No. The same code works for as many people as you give it to. If you need per-person access you can grant or revoke individually, switch to built-in logins via App Users.
Can I see who opened my protected content?
A shared password is anonymous by design, so it shows that someone with the code got in, not who. For named, per-user visibility, use built-in logins and track access through App Users and app analytics.
Do I need a paid plan to password protect content?
No. Password protection and built-in email logins are available across plans, starting Free. Custom domains for branded client and member portals are on Business ($25/mo) and above.
How is this different from making a project private?
A private project is invite-only inside your workspace. Password protection gates a public share link with one code, so people outside your workspace can open it without an account. See Security & sharing for how the two fit together.
What You'd Build in Taskade
Picture a Client/Member Portal. You describe it to Taskade Genesis in plain English, and it builds a live app where each client logs in to see their own project status, files, invoices, and next steps. You publish it behind built-in email logins, point it at your own custom domain on Business and above, and use a password gate for the early-access group while you test. Clients see a clean branded portal, sign in with their email, and find exactly their own information. Reminders and status updates run on their own through reliable automation workflows. You manage one app, everyone gets a private door, and nothing leaks to the open web. Build your portal with Taskade Genesis →