> ## Documentation Index
> Fetch the complete documentation index at: https://docs.mythex.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Build a client portal with Mythex

> A place for clients to see status, files, or requests — database-backed, with BYO login when you need it.

# Build a client portal with Mythex

A client portal is a **logged-in (or shared-link) home** for people outside your team: project status, files, invoices, or support requests.

## When this is a good fit

* Clients keep emailing “what’s the status?”
* You want one URL per client (or one app with a client list) instead of a messy shared folder
* v1 can be a simple status + documents list before you add real auth

A shared Notion page is enough if there is one client and nothing sensitive.

## What you’ll have

* A client-facing home (status, next steps, files)
* An internal list of clients/requests in the same project (or a simple admin view)
* Optional [file uploads](/features/storage) and a [database](/features/database)

## Starter prompt

```text theme={null}
Build a client portal for [AGENCY / PRODUCT].
Client home: project status, upcoming milestones, and a files list.
Simple request form (title, details) saved with /database.
Include a plain admin view of all requests. Placeholder login — we'll add real auth later.
```

## Build it

1. Describe **what the client needs to see in 10 seconds** (status beats a 12-page wiki).
2. Enable `/database` for requests and `/storage` if they upload files.
3. Keep the **admin view** off the public nav or behind a placeholder gate until [BYO auth](/recipes/add-authentication).
4. Preview as if you were the client on a phone.
5. `/test` submit a request → it appears on the admin list.
6. [Publish](/publish/how-to-publish) when you are ready to share a URL.

## Honest limits

* App login is [bring-your-own](/recipes/add-authentication) — Mythex accounts are for builders
* No built-in e-signature, invoicing, or Magic Link product
* Don’t put secrets in the public portal; use [project secrets](/features/env-and-secrets) for APIs

## Related

* [Use cases](/use-cases/overview)
* [Build an internal tool](/use-cases/build-an-internal-tool)
* [File storage](/features/storage)
* [Add login (BYO)](/recipes/add-authentication)
