Live chat
Messages with each client arrive within seconds, with attachments, read receipts and emails only for what stays unread.
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.
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.
What Client Portal does for you.
Messages with each client arrive within seconds, with attachments, read receipts and emails only for what stays unread.
Send an NDA or agreement through Contracts; the client reviews and signs it from the portal.
Messages, files, decisions, agreements, billing and requests on one timeline per client, with filters and CSV.
A suggested path for Client Portal. What you can do depends on your access in the app.
Name the people who sign in with an email code and the sections they see.
Chat, share files, ask for decisions and send agreements and invoices.
See what waits on you and on the client, and everything that happened.
Live host, inventory, governance, health checks, verification, dependencies and history.
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.
The records stay in their catalogs (Boards, Drive, Quotations, Payments); the portal shows and links them per client.
5 of 18 required controls are configured. Catalog deployment and inventory maturity remain independent until every required control is present.
portals.appneural.com
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
Configure or repair: Documentation exists.
Configure or repair: Architecture documentation exists.
Configure or repair: Security review is current.
No remediation required.
Configure or repair: Dependencies exist.
Configure or repair: Consumers exist.
No remediation required.
Configure or repair: SLA or SLO exists.
Configure or repair: On-call exists.
Configure or repair: Release exists.
No remediation required.
Configure or repair: Infrastructure drift is clear.
No remediation required.
No remediation required.
No remediation required.
No remediation required.
Configure or repair: Repository exists.
Configure or repair: Business owner exists.
Configure or repair: Product owner exists.
Configure or repair: Technical owner exists.
Configure or repair: Maintaining team exists.
AI outputs are saved as drafts with evidence references. They never replace verified catalog fields automatically.