# Build a Customer Portal

> Build a branded customer portal in Taskade Genesis with sign-in, explicit identity-based filters, a Project database, and a custom domain.

- Source: https://www.taskade.com/learn/genesis/build-customer-portal
- Section: Taskade Genesis
- Updated: 2026-10-20
- Index of all pages: https://www.taskade.com/learn/llms.txt

## Overview

Build a customer portal where each client signs in and sees their own account. You add sign-in from **App settings → People & access → App users**, then ask Taskade EVE to match each signed-in email to a `customer_email` field. Sign-in works on every plan, including Free. Row filters are opt-in. A custom domain is Pro and above, and is a separate setting from sign-in.

A Project holds customer records and acts as the database. Taskade EVE drafts the sign-in copy, record filters, and dashboard layout. Automations can log activity and notify your team when a customer takes an action.

> **TL;DR:** Turn a prompt into a customer portal in Taskade Genesis. Add [Taskade Genesis Auth](https://www.taskade.com/learn/genesis/genesis-auth), share the sign-in URL, and match each signed-in email to the correct Project rows with explicit filters. Test two customer accounts plus an unmatched account before publishing private data. Custom domains start on Pro. [Build the portal](https://www.taskade.com/create).

![Build a customer portal with Taskade Genesis](https://www.taskade.com/static_images/blog/agent-automation-1.gif)

## Explore these live apps

Want to see a finished portal before you build your own? Open one of these live Taskade Genesis apps in your browser. If its creator shared it as a kit, a Clone action appears with a breakdown of everything Taskade copies.

| Live app | What it does | Preview |
| --- | --- | --- |
| Client Portal Dashboard | A branded home base where each client signs in and sees their account, documents, and status. The clinic and consultancy examples both start here. | [Open demo →](https://www.taskade.com/share/apps/7nj4gtlug6gjqtm6) |
| Event Management Portal | A portal for attendees and organizers. Guests see their schedule and tickets. Your team sees the full guest list and check-in status. | [Open demo →](https://www.taskade.com/app/event-management-portal-scv62ou1yocu3sno) |

When a Clone action is available, review the included Projects, agents, automations, and screens before you copy. Review the connections after cloning. Then follow the steps below to configure sign-in and identity filters.

## What You Will Build

1. A **Customers Project** in Table view holding accounts, contacts, and status.
2. A **Branded portal** with a public landing page and a private members area.
3. A **Sign-in flow** powered by Taskade Genesis Auth.
4. **Identity-filtered views** that match each customer to the correct rows.
5. An **Activity feed** that updates the moment a teammate or customer changes anything.

```mermaid
flowchart LR
    V[Visitor lands<br/>on portal]
    V --> S[Signs in via<br/>Taskade Genesis Auth]
    S --> R{Configured<br/>identity filter}
    R -->|Team route| T[Team dashboard<br/>full data]
    R -->|Email matches row| C[Client view<br/>matched records]
    C --> P[Customer Project<br/>as database]
    T --> P
    P --> A[Taskade EVE<br/>drafts replies]
    A --> N[Email and Slack<br/>notifications]
    style V fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8
    style S fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8
    style R fill:#1a140a,color:#ffb74d,stroke:#e65100
    style T fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8
    style C fill:#2a1225,color:#ff8fa3,stroke:#ff2d60
    style A fill:#2a1225,color:#ff8fa3,stroke:#ff2d60
    style P fill:#0d1a0e,color:#86efac,stroke:#22c55e
    style N fill:#1a140a,color:#ffb74d,stroke:#e65100
```

Read the diagram left to right. A visitor arrives and signs in. The portal applies the filter you configured, such as signed-in email equals `customer_email`. Your team reaches a separate full dashboard. Both can use the same Customer Project as the source of truth.

### Who is this for

| You run | Your customers get | They never see |
| --- | --- | --- |
| A mental-health clinic | Their own records, notes, and appointments | Any other client's data |
| A consultancy or agency | A branded login, deliverables, and invoices | Internal margins or other accounts |
| A SaaS or B2B team | Plan, onboarding checklist, support thread | The full customer list |
| An events business | Tickets, schedule, and updates | The master guest list |

## Do this in Taskade

### Step 1: Generate the portal

Open [Taskade Genesis](https://www.taskade.com/create) and paste this prompt.

```text
Build a branded customer portal.
Customer fields: name, email, account, plan, status, last_active.
Include a public landing page, a sign-in screen, a private dashboard,
a documents tab, a support ticket form, and an activity feed.
Let signed-in customers upload documents from their portal page.
Store a customer_email field on every customer row.
Filter the client dashboard so signed-in email must equal customer_email.
Show an empty state when no record matches.
Connect the customers Project as the live database.
```

*Why this works:* The `customer_email` line gives every row the field that the record filter needs in Step 4.

Taskade Genesis ships a Projects workspace, a published portal, three automations, and Taskade EVE ready to answer customer questions inside the portal.

### Step 2: Add sign-in

Add sign-in from the app settings. The workspace owner does these steps.

1. Open **App settings**.
2. Click **App users** under **People & access**.
3. If the app has no sign-in yet, click **Set up sign-in with Taskade EVE**.
4. Taskade EVE opens with a ready prompt that adds sign-in and keeps everything else the same. Send the prompt.
5. Publish the update.

The portal now has a sign-in screen where visitors create an account and log in. Sign-in confirms who the visitor is. It does not hide any rows on its own. Step 4 adds the record filters. Sign-in works on every plan, including Free. See [Taskade Genesis Auth](https://www.taskade.com/learn/genesis/genesis-auth) for the full sign-in setup.

### Step 3: Add your first App Users

Open the published portal's sign-in page. App Users appear after they create an app-specific account and sign in.

1. Share the portal's sign-in URL with a test customer.
2. Let the customer create an account and sign in.
3. Open **App settings → People & access → App users** and look for the email in the list.

To add a customer yourself, type their email in **Add person** on the same tab. Taskade emails them a link to set a password. To stop strangers from signing up, set **Who can sign up** to **Invite only**. See [App Users and Sign-In](https://www.taskade.com/learn/genesis/app-users) for every account control.

### Step 4: Configure and test record filters

Ask Taskade EVE to match the signed-in identity to your Project data.

1. Make sure that every customer row has a `customer_email` field.
2. Send Taskade EVE this prompt:

```text
Show each signed-in customer only the rows where customer_email equals their sign-in email. Show an empty state when no row matches. Do not change the sign-in screen or the dashboard layout.
```

3. Sign in with two customer accounts. Make sure that each one sees different rows.
4. Sign in with an account that matches no row. Make sure that it sees the empty state.

You are done when each test account sees only its own rows.

Taskade's workspace roles govern workspace members, not App Users. Do not use a Viewer role in place of customer-row filtering. App Users need an explicit identity-to-record rule in the generated app.

### Step 5: Connect the database

Taskade Genesis stores the portal records in a Project in the app's workspace. Open **Projects** in the app to see it. To use a different Project, ask Taskade EVE:

```text
Use my customers project as the data for the portal. Show status, plan, and notes on the dashboard. Do not change the sign-in or the record filters.
```

Every edit a customer makes in the portal writes back to the Project. Every edit your team makes in the Project shows up in the portal. One source of truth, no sync jobs.

## Common Portal Patterns

| Pattern | How Taskade Genesis handles it |
| --- | --- |
| Client onboarding | Add a checklist block on first sign-in. Status writes to the customer row. |
| Document delivery | Upload to the documents tab. Customer downloads from their portal page. |
| Document collection | Customer uploads a signed agreement or an intake form from their portal page. An automation reads the file and updates their row. |
| Support tickets | Form submission creates a new row in a `tickets` Project. Taskade EVE drafts the reply. |
| Billing summary | Pull invoice rows from a Project after matching the signed-in email. |
| Account managers | Tag a teammate as the owner of each row. Slack notification fires on status change. |
| Self-service updates | Customer edits their own row. Automation pings the account manager. |

## Use case: a 50-customer portal

A small SaaS team wires their portal in an afternoon. Each row in a `customers` Project is one account and carries the customer's email. The portal filters by the signed-in email after Taskade Genesis Auth identifies the user.

- **Day 1**: One Taskade Genesis prompt, the portal renders. Two team members fill in five rows by hand.
- **Day 2**: The team shares the sign-in URL. The first customers create accounts, and the team checks that each identity returns the expected row.
- **Day 7**: A weekly automation pulls each customer's status from the Project and posts a digest to a Slack channel. The account manager touches each customer once a week instead of chasing email.

This is the smallest version of a portal that earns its keep. Scale up from here.

## How the portal gets smarter

Your portal runs on Workspace DNA. Memory, Intelligence, and Execution feed each other in a loop, so every customer action makes the next one easier. After a quarter of this loop, a consultancy has a portal that knows each client's history. It drafts replies in the firm's voice and updates itself, with no spreadsheet work.

```mermaid
flowchart LR
    M[Memory<br/>Customer Project records]
    I[Intelligence<br/>Taskade EVE reads context]
    E[Execution<br/>Automations send and log]
    U[Client portal<br/>updates live]
    M --> I
    I --> E
    E --> U
    U --> M
    style M fill:#0d1a0e,color:#86efac,stroke:#22c55e
    style I fill:#2a1225,color:#ff8fa3,stroke:#ff2d60
    style E fill:#1a140a,color:#ffb74d,stroke:#e65100
    style U fill:#0d1b2a,color:#7dd3fc,stroke:#38bdf8
```

Memory is the Customer Project that holds every record. Intelligence is Taskade EVE reading that history to draft a reply or a digest. Execution is the automations that send the email and log the result. Each loop writes new records back into Memory, so the portal is never starting from scratch. See [Taskade as a CRM](https://www.taskade.com/learn/genesis/crm), our guide to customer relationship management, for the data side. See [App Analytics](https://www.taskade.com/learn/genesis/app-analytics) to watch the loop in action.

## What your client sees

A signed-in customer whose email matches a Project row lands on a clean page filtered to that record. Here is the rough layout.

```text
+--------------------------------------------------+
|  [Logo]            Welcome back, Acme            |
+--------------------------------------------------+
|  Status: Active        Plan: Standard            |
+--------------------------------------------------+
|  Your records          |  Documents              |
|  - Intake form  done   |  - Agreement.pdf        |
|  - Session notes       |  - Invoice-04.pdf       |
|  - Next appt: Jun 12   |  - Care plan.pdf        |
+------------------------+-------------------------+
|  Need help?  [ Open a support ticket ]           |
+--------------------------------------------------+
```

The same app can show your team a separate full-list route. Keep the team route behind its own workspace or domain checks.

## Publish on a Custom Domain

When the portal feels right, click **Publish**.

1. Pick a [custom domain](https://www.taskade.com/learn/genesis/custom-domains) like `portal.yourbrand.com`.
2. Add your logo and brand colors. Taskade EVE rewrites the theme on confirm.
3. Drop the link in your welcome emails or signature.

Every sign-in feeds the workspace. Customer activity, support tickets, and account history all live in one place. The portal gets smarter the more customers use it.

## Frequently asked questions

### Can customers use the portal without creating a Taskade account?

They create an app-specific sign-in on the portal URL. That sign-in works on every plan, including Free. It is not a Taskade workspace seat. Sign-in confirms who the visitor is. You still match records to that login and test with a second account.

### How do I run a customer portal on a Free plan?

Sign-in and the published portal work on Free. Isolation is opt-in: add a `customer_email` field and filter by signed-in email. A custom domain is Pro and above. Do not treat the domain as part of the sign-in setting. See [pricing](https://www.taskade.com/pricing).

**Can each customer see only their own records?**

Yes, after you configure and test a record filter. Match the signed-in email to a `customer_email` field, test multiple accounts, and return an empty state when no row matches. Taskade Genesis Auth identifies the user but does not automatically limit which Project rows they see. See [Configure and Test Record Filters](#step-4-configure-and-test-record-filters) above.

**Do I need to know how to code?**

No. You describe the portal in plain words and Taskade Genesis builds it. Taskade EVE writes the sign-in copy and dashboard layout for you. The fastest start is to clone the [Client Portal Dashboard](https://www.taskade.com/share/apps/7nj4gtlug6gjqtm6) above and rebrand it.

**Can I put the portal on my own web address?**

Yes, on the Pro plan and above. Publish to a [custom domain](https://www.taskade.com/learn/genesis/custom-domains) like `portal.yourbrand.com` so a consultancy's clients sign in on the firm's own branded address. Add your logo and colors and Taskade EVE rewrites the theme on confirm.

**Where is the customer data stored?**

In a Taskade Project that acts as the live database. Every edit a customer makes writes back to the Project, and every edit your team makes shows up in the portal. One source of truth, no separate sync jobs. See [Taskade as a CRM](https://www.taskade.com/learn/genesis/crm) for how to structure the data.

**How much does a customer portal cost to run?**

You can start free. Customer sign-in with Taskade Genesis Auth is part of every published app, on any plan. Custom domains unlock on the Pro plan and up. See [pricing](https://www.taskade.com/pricing) for current details. This replaces dedicated portal software that often runs $50 to $300 per month.

**Can the portal notify my team when a customer takes action?**

Yes. Automations watch the Customer Project and fire an email or Slack message the moment a customer updates their row, submits a ticket, or finishes onboarding. Taskade EVE can draft the first reply, so an account manager only reviews and sends.

### Related guides

- [Create Your First App](https://www.taskade.com/learn/genesis/first-app)
- [Taskade Genesis Auth](https://www.taskade.com/learn/genesis/genesis-auth)
- [App Users and Sign-In](https://www.taskade.com/learn/genesis/app-users)
- [Custom Domains](https://www.taskade.com/learn/genesis/custom-domains)
- [Taskade as a CRM](https://www.taskade.com/learn/genesis/crm)
- [App Analytics](https://www.taskade.com/learn/genesis/app-analytics)
- [Taskade EVE Memory](https://www.taskade.com/learn/genesis/eve-memory)
- [Build an Internal Tool](https://www.taskade.com/learn/genesis/build-internal-tool)
- [Build a Document Intake App](https://www.taskade.com/learn/genesis/document-intake)
- [Build a Client Portal Without Code](https://www.taskade.com/ai/portals)
