Skip to app details
Back to app library
APPNEURAL APP FAMILYCustomers & Sales

Client Portal

One place where each client finds everything

Give each client one branded place to chat, share files, sign agreements, approve work and pay, with the whole history in one timeline.

01 / OVERVIEW

See where it fits in your day.

Each domain lists its clients (name, phase and status line, welcome note, account manager, booking link, GSTIN) and the contacts who may sign in. A client signs in at portal.<domain>/client with a 6-digit email code (10 minutes, 5 tries, rate-limited) and sees, in the domain's brand, the sections the business turns on: Overview, Projects with milestones and progress (live from Boards with an API key), Files that both sides upload (R2, 25 MB, served only after a session check) or Drive links, Decisions to approve or send back with the decider's name and time recorded, Quotes and invoices (live from Quotations), pay links from Payments, Requests, Messages and a booking link. The team's home shows what waits on the team and what waits on clients, with a page per client, an inbox and an activity log of what each client opened. Emails go both ways; a daily 10:00 IST cron sends decision reminders and one digest per team. Claude drafts a weekly client update from the last 7 days. GET/POST /api/v1/clients, GET /api/v1/requests and webhooks.

A LOOK INSIDEExample layout · sample content
Client portal
# Messages# Agreements# Activity
CONVERSATION PREVIEW
A
Kickoff call notes
N
NDA signed
T
Homepage design approved
02 / CAPABILITIES

Built around the work you do.

What Client Portal does for you.

01

Live chat

Messages with each client arrive within seconds, with attachments, read receipts and emails only for what stays unread.

02

Agreements

Send an NDA or agreement through Contracts; the client reviews and signs it from the portal.

03

One timeline

Messages, files, decisions, agreements, billing and requests on one timeline per client, with filters and CSV.

03 / GETTING STARTED

Start small. Build from there.

A suggested path for Client Portal. What you can do depends on your access in the app.

01

Add the client

Name the people who sign in with an email code and the sections they see.

02

Work together

Chat, share files, ask for decisions and send agreements and invoices.

03

Follow the timeline

See what waits on you and on the client, and everything that happened.

YOUR NEXT MOVE

Make Client Portal part of your workflow.

The app opens in a new tab, so your ecosystem stays close.

Open app
05 / CATALOG DETAILS

The registry record.

Live host, inventory, governance, health checks, verification, dependencies and history.

Catalog surfaceDEPLOYEDHEALTHY
InventoryACTIVE1 items
P2VERIFIEDPUBLISHED
Overview

Purpose and boundaries

Each domain lists its clients (name, phase and status line, welcome note, account manager, booking link, GSTIN) and the contacts who may sign in. A client signs in at portal.<domain>/client with a 6-digit email code (10 minutes, 5 tries, rate-limited) and sees, in the domain's brand, the sections the business turns on: Overview, Projects with milestones and progress (live from Boards with an API key), Files that both sides upload (R2, 25 MB, served only after a session check) or Drive links, Decisions to approve or send back with the decider's name and time recorded, Quotes and invoices (live from Quotations), pay links from Payments, Requests, Messages and a booking link. The team's home shows what waits on the team and what waits on clients, with a page per client, an inbox and an activity log of what each client opened. Emails go both ways; a daily 10:00 IST cron sends decision reminders and one digest per team. Claude drafts a weekly client update from the last 7 days. GET/POST /api/v1/clients, GET /api/v1/requests and webhooks.

One branded place per client of a connected domain, behind an email code: projects, shared files, decisions, quotes and invoices, pay links, requests and messages.

The records stay in their catalogs (Boards, Drive, Quotations, Payments); the portal shows and links them per client.

Priority
P2
Portfolio
Customers & Sales
Capability
Customers & Sales
Technical owner
Not configured
Runtime
Cloudflare Workers / OpenNext
Last verified
2026-11-18 14:03:12
Semantic inventory

Every number says what it counts

1Catalog itemstrackedEntityCount · catalog-api:live
Production-ready gate

Governance evidence required

5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.

MissingBusiness owner
MissingProduct owner
MissingTechnical owner
MissingMaintaining team
MissingGitHub repository
ConfiguredProduction URL
ConfiguredHealth endpoint
MissingDocumentation
MissingArchitecture document
MissingCurrent security review
ConfiguredData classification
MissingDependencies
MissingConsumers
MissingSLA / SLO
MissingOn-call
MissingLast release
ConfiguredLast verification
ConfiguredDeprecation status
Catalog details

portal schema v1

Catalog-specific metadata is not configured.
Live host

Where it runs

DNS & routing

Confirmed infrastructure only

Provider inspection appears after Cloudflare credentials are configured. Mutations require dry run, idempotency and explicit confirmation.
Repository & architecture

Technical context

APPNEURAL-Catalogs/portal-catalogLOCAL · NOT CONFIGURED

Documentation

Documentation and architecture evidence are not configured.
Dependencies

Registered relationships

No dependency edges are registered. Nothing has been inferred.
Operations

Checks and verification

No health checks have been recorded.
Security

Review posture

Security review not configured. This does not mean the catalog is secure or insecure.
Automatic reconciliation

GitHub · Cloudflare · DNS · catalog APIs

No synchronization run has completed yet. The scheduled Worker records missing credentials as Not configured, never as success.

Drift findings

No drift has been recorded.
Evidence & history

Trust record

Verification is verified. Run verification to store check-level evidence, confidence, expiry and remediation.

AI workspace

Human-reviewed drafts

AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.

App libraryOpen app