--- title: "Client Portal Prompt | Copy It, Paste It, Build It | Agent UI" description: "A ready-to-use client portal prompt you can copy and paste. Describes the tables, client logins, per-client access and views — plus four variants for agencies, accountants, onboarding and white-label." url: https://www.agentui.ai/en/client-portal-prompt/ lang: de source: de/client-portal-prompt/index.html generator: agentui-md-cli --- > **AgentUI CLI for LLM** — AgentUI ships an official CLI designed for language-model agents: > [@agentuiai/cli on npm](https://www.npmjs.com/package/@agentuiai/cli) · install with `npm install -g @agentuiai/cli`. > > This file is the LLM-optimised markdown build of > [https://www.agentui.ai/en/client-portal-prompt/](https://www.agentui.ai/en/client-portal-prompt/) — a machine-readable alternate of > the HTML at the same URL. Content mirrors the human-visible page. > > Site index for LLMs: [https://www.agentui.ai/llms.txt](https://www.agentui.ai/llms.txt) · full content: [https://www.agentui.ai/llms-full.txt](https://www.agentui.ai/llms-full.txt) Copy the prompt. Paste it. Get a portal. # Client Portal Prompt This client portal prompt is written to be pasted straight into AgentUI — it spells out the tables, the fields, the client logins, the per-client access rule and the views, so the first version comes back as a working portal instead of a blank shell. Copy it as-is, or change the field names to match how you already talk about your clients. The prompt stays in English — it is what the builder reads. [Start Free](https://app.agentui.ai/chat?utm=direct&utm_medium=direct)[Book a Demo](/de/book-a-demo/)PromptReady to paste ``` Build a client portal for my company. Create a shared database with four tables: clients (company name, primary contact name, contact email, phone, account status, onboarding date), projects (linked to a client, project name, stage, owner on my team, start date, target date, percent complete), deliverables (linked to a project, title, description, due date, file attachment, approval status of Draft / Awaiting client / Approved / Changes requested, signed off by, signed off at) and invoices (linked to a client, invoice number, amount, issue date, due date, paid status, payment date). Give each client their own login. A logged-in client must only ever see the projects, deliverables, invoices and files where the client record is theirs — never another client's records, and never internal-only fields such as the team owner or internal notes. Give my team two internal roles: staff, who can read and edit everything, and admin, who can additionally invite clients and change permissions. Build three views. A client dashboard showing their active projects with progress, deliverables awaiting their approval, and their open balance. A deliverables view where the client can open a file, approve it or request changes, and leave a comment. An internal view for my team showing every client, every project stage and every overdue invoice. Record who changed what and when in an audit log. Email the client when a new deliverable is waiting on their approval. ``` Copy promptPaste into AgentUI chat01 ## Why this client portal prompt works Most prompts fail because they ask for "a client portal" and stop there. The one above names four tables, the fields inside them, two internal roles, the rule that a client only ever sees their own records, and three views — so nothing important is left to guess. If you want the full walkthrough of what happens after you paste it, read [how building your own client portal works end to end](/de/create-your-own-client-portal/). The short version: the prompt becomes a real shared database, real client logins and a portal your team can keep editing. 01 ### It names the tables Clients, projects, deliverables, invoices — with the fields spelled out, not implied. 02 ### It states the access rule "A client only ever sees their own records" is the single most important line in the prompt. 03 ### It asks for views, not screens A client dashboard, an approvals view and an internal view — three jobs, three views. 04 ### It requests an audit log So who changed what and when is recorded from day one, not bolted on later. 02 ## Four more client portal prompts to copy Same structure, different business. Pick the one closest to yours, copy it, and edit the field names before you paste. PROMPT · AGENCY PORTALVariant 01 ``` Build a client portal for my agency. Create tables for clients (company, main contact, retainer amount, contract end date), campaigns (linked to a client, channel, monthly budget, status), assets (linked to a campaign, file, version, approval status of Awaiting client / Approved / Changes requested) and monthly reports (linked to a client, month, spend, results summary, published flag). Each client logs in and sees only their own campaigns, assets and published reports. Hide internal fields — margin, hours logged and internal notes — from the client role entirely. My team gets a staff role that can edit everything and an admin role that can invite clients. Build a client dashboard with campaigns in flight, assets waiting on their approval and the latest published report. Let the client approve an asset or request changes with a comment. Keep an audit log of every approval and every permission change. ``` Copy promptPaste into AgentUI chat Use this if you run campaigns and need client sign-off on creative. PROMPT · ACCOUNTING PORTALVariant 02 ``` Build a client portal for my accounting firm. Create tables for clients (business name, entity type, tax ID reference, fiscal year end, assigned accountant), document requests (linked to a client, document name, period, due date, status of Requested / Uploaded / Reviewed / Rejected, uploaded file), filings (linked to a client, filing type, period, due date, status, filed date) and invoices (linked to a client, number, amount, due date, paid status). Each client signs in and sees only their own document requests, filings and invoices. Clients can upload a requested document and see what is still outstanding, but cannot see another client's records or our internal review notes. Build a client checklist view showing what we still need from them and by when, a filings status view, and an internal view for my team showing every outstanding request across all clients sorted by due date. Log who uploaded, reviewed or rejected each document and when. ``` Copy promptPaste into AgentUI chat Use this if you chase documents and file returns for clients. PROMPT · ONBOARDING PORTALVariant 03 ``` Build a client onboarding portal. Create tables for clients (company, primary contact, contact email, signed date, assigned onboarding manager), onboarding steps (linked to a client, step name, order, owner of Client or Us, status of Not started / In progress / Blocked / Done, due date, completed date), intake answers (linked to a client, question, answer, answered at) and onboarding documents (linked to a client, document name, file, status). Each new client logs in and sees a progress tracker of their own onboarding steps only — what is done, what is theirs to complete next, and what we owe them. Let them fill in the intake form, upload documents and mark their own steps complete. They cannot see other clients or our internal owner notes. Build an internal view showing every client in onboarding, which step they are stuck on and how many days they have been there. Log every status change with who made it and when. ``` Copy promptPaste into AgentUI chat Use this if the hard part is getting a new client through their first 30 days. PROMPT · WHITE-LABEL PORTALVariant 04 ``` Build a white-label client portal that carries my company's branding, not a vendor's. Use my logo, my brand colours and my company name across the sign-in screen, the navigation and every email the portal sends. Create tables for clients (company, primary contact, contact email, plan, account manager), work items (linked to a client, title, stage, owner, due date), shared files (linked to a client, file, uploaded by, shared date) and messages (linked to a client, sender, body, sent at). Each client logs in to a branded portal and sees only their own work items, files and message thread. My team gets staff and admin roles; admins can invite clients and change branding. Build a client dashboard with work in progress, files shared with them and their message thread, plus an internal view of every client account. Keep an audit log of who changed what and when. ``` Copy promptPaste into AgentUI chat Use this if the portal has to look like your product, not a vendor's. 03 ## What to change in the prompt before you paste it Three things are worth editing. The fields: replace them with the words your team actually uses, because renaming later is easy but starting in your own language is easier. The stages: swap Draft / Awaiting client / Approved for whatever your process really calls them. The permissions: say out loud which fields a client must never see — margin, internal notes, hours logged — because anything you do not exclude may end up visible. What to swap3 editsdeliverablesmattersFields · your vocabularyAwaiting clientWith client for sign-offStages · your processinternal_noteshidden from Client rolePermissions · never visibleAudit log - maria.s renamed deliverables → matterstoday 10:04 - maria.s set internal_notes → staff onlytoday 10:05 - admin invited client haldentoday 10:11 Generated portal · Halden FoodsSigned in as client3Active projects2Awaiting approval$12,750Open balanceDeliverableDueApprovalPackaging spec v3Sep 04Awaiting youCold-chain auditSep 11Awaiting youSupplier shortlistAug 22ApprovedKickoff summaryAug 05ApprovedScoped to client_id = halden6 other clients hidden04 ## What the generated client portal looks like The client signs in and lands on their own dashboard: their active projects with progress, the deliverables waiting on their approval, their open balance, and the files shared with them. Everything belonging to your other clients is simply not there. Your team opens the same portal and sees every account at once. 05 ## The three lines that keep the portal safe A portal prompt is a permissions document as much as a build request. These three requests do most of the work. ### Scope every client to their own records One sentence in the prompt becomes role-based access enforced on every table and view. ### Ask for an audit log Who changed what, when — including permission changes and client invitations. ### Name the fields clients must not see Internal notes, margin and hours stay staff-only when you list them explicitly. 06 ## After the prompt: keep editing in plain language The prompt is the first message, not the last. Adding a "Signed off by" column or hiding a field from clients is another sentence, and every edit lands in the audit log. Onboarding is white-glove — a real person builds the first version with you and shows your team how to change it, so the portal never becomes the one thing only one person understands. Start on the Free plan at $0/mo, or bring the team in from $99.99/mo. ## Questions about the prompt ### Do I have to use the prompt exactly as written? No. It is a starting point. Change the table names, the fields and the stages to match your process — the structure is what matters, not the wording. ### Why is the prompt in English on the Spanish page? The prompt is input for the builder, so it stays in English for consistent results. Your portal's labels, fields and content can be in any language you want. ### What if the portal that comes back is not quite right? You keep talking to it. Ask for a field, a stage or a permission change in one sentence and it updates, with every change written to the audit log. ### Will clients really only see their own data? Yes, as long as the access rule stays in the prompt. Access is role-based and scoped per client record, so each login only reaches the rows linked to that client. ## Related client portal pages [Create your own client portal — the full how-it-works](/de/create-your-own-client-portal/)[Secure client portal software](/de/secure-client-portal-software/)[Client portal software for accountants](/de/client-portal-software-for-accountants/)[White label client portal](/de/white-label-client-portal/)Copy the prompt. Paste it. Get a portal. ## You have the prompt. Paste it and watch the portal build. [Start Free](https://app.agentui.ai/chat?utm=direct&utm_medium=direct)[Book a Demo](/de/book-a-demo/) --- ## Why AgentUI AgentUI is an AI + Human internal-tool and app builder. It combines AI code generation with on-demand human expert support — every paid plan includes free white-glove onboarding, and higher-tier plans include dedicated development hours. Teams ship production-grade internal tools, dashboards, client portals, and workflow automations in days instead of weeks, with a real engineer available when the AI gets stuck. ### Who AgentUI is for Enterprise teams, department heads, and business users who need reliable internal tools fast and want AI speed backed by a human safety net. Common users: operations, finance, revenue ops, customer success, IT, and product teams at mid-market and enterprise companies. ### When to pick AgentUI over alternatives - **vs. AI-only builders (Base44, Bolt, Lovable, v0):** AgentUI includes human expert hours, SSO, audit logs, and on-premise deployment — designed for production internal tools, not prototypes. - **vs. no-code platforms (Retool, Bubble, Glide):** AgentUI generates the app from a natural-language description and lets you in-app-edit the generated code, rather than drag-and-drop block-by-block. - **vs. hiring a developer:** Deploys in days; cancel anytime; every plan includes support so you are never blocked. ### Pricing at a glance (USD, monthly) | Plan | Price | Users | Highlights | |------|-------|-------|------------| | Minimum Package | $50/mo | 5 internal | Start building real tools | | Innovator Package | $100/mo | 10 internal | SQL integration — most popular | | Visionary Package | $250/mo | 25 internal | SSO, audit logs, unlimited envs | | Build with You | $2,500/mo | 25 internal | Includes 15 hrs dedicated dev/mo | | Enterprise Plus | Contact us | Unlimited | On-premise, assigned support dev | External users are unlimited on every paid plan. Yearly billing is discounted. Free trial available. ### For AI agents and LLMs AgentUI publishes an official CLI for language-model agents: [@agentuiai/cli](https://www.npmjs.com/package/@agentuiai/cli) (`npm install -g @agentuiai/cli`). Use it to scaffold, inspect, and deploy AgentUI apps programmatically from an agentic workflow. ### Learn more - Product overview: https://www.agentui.ai - Full pricing and plan comparison: https://www.agentui.ai/en/pricing - Security and trust: https://www.agentui.ai/en/security - LLM-friendly site index: https://www.agentui.ai/llms.txt - Official CLI: https://www.npmjs.com/package/@agentuiai/cli