User

Client Reports

Screen guide

Before you start

Use the account and workspace that own the relevant records. The feature also needs to be enabled for this installation and plan.

Open this feature

Choose a task

Open /portal/reports/client on your application domain, using the workspace account for this task.
Find the form containing Title, Status, Organization. Complete the relevant fields using the table below. Fields can appear or change after you select an option.
Select Create report. Check the current record, recipients, amount or destination before confirming when those values apply.
If the application identifies a missing or invalid field, correct that field and submit again. If an external request or payment has an uncertain outcome, check its history before repeating it.

Field	What to enter or choose
Title	Required. Enter the title for this task, using the help or example shown by the form. The form’s example is NovaPeak Studio Progress Update. Replace it with your own value. Maximum 255 characters.
Status	Required. Choose Shared - visible to client, Ready - internal review done, Draft - not ready.
Organization	Optional unless the current form requests it. Choose No organization.
Project	Optional unless the current form requests it. Choose No project.
Report type	Required. Choose Project progress, Performance summary, Recommendations, Approval summary.
From	Optional unless the current form requests it. Enter the from for this task, using the help or example shown by the form.
To	Optional unless the current form requests it. Enter the to for this task, using the help or example shown by the form.
Short summary	Optional unless the current form requests it. Enter the short summary for this task, using the help or example shown by the form. Maximum 1000 characters.
Client-facing content	Required. Enter the client-facing content for this task, using the help or example shown by the form. Use clear sections: summary, completed work, next steps, risks, and requested decisions. Maximum 20000 characters.

Field descriptions appear beside each task above so that separate forms are not mixed together.

Stay in the same account/workspace and reopen the intended record or result screen.
For saved settings, compare the displayed values with the choices you made. For filters and previews, check the current result scope.
For queued or external work, inspect its status/history and provider result where applicable. A successful save does not by itself prove message delivery, publication, payment completion or provider approval.

Problem	What to check
The screen or action is missing	Check the correct workspace account, role, enabled app and plan. A hidden action is not fixed by typing an internal endpoint.
A field is rejected	Read its validation message, choose from the offered options and check the relevant format or limit. Do not substitute a database ID for a displayed choice.
A list is empty	Check the selected workspace, search text, date range and status filters. Clear one filter at a time before concluding that records are missing.
A request is still pending	Check its status/history before repeating it. For messages, publishing, imports and payments, a submitted request can finish later or fail separately.

Role-scoped source references

Pinned commit: 40d27448e4517301d3d8f5a27ca0c7531c51f136

Source-only route information

Method	Source-default route
GET	/portal/reports/client

Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source key	Handler
reportDateFrom	modules/AppClientReports/Livewire/ClientReportIndex.php
reportDateTo	modules/AppClientReports/Livewire/ClientReportIndex.php