User
Billing
Screen overview
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
- Open /portal/billing on your site.
Steps
Review Billing
- Open /portal/billing on your application domain, using the workspace account for this task.
- Review the visible sections such as Billing, No plan assigned, No active subscription, Recent payments, Invoice, Plan. Empty-state headings appear only when the corresponding list has no data.
- Open an item only through its displayed row, card or record link. Check the selected account/workspace and any date or status filter before comparing results.
- If this screen has no editable form, it does not need a Save action. Follow the linked feature or action in the application when you need to create or change a record.
Fields and choices
Field descriptions appear beside each task above so that separate forms are not mixed together.
Check the result
- 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.
Common problems
| 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. |
Technical reference
Role-scoped source references
Pinned commit: 5af0236c6d99c50079f5ab8b8fb035506634bd8d
Source-only route information
| Method | Source-default route |
|---|---|
| GET | /portal/billing |
| POST | /portal/billing/subscriptions/{subscription}/cancel |
| GET | /portal/invoices |
| GET | /portal/invoices/{invoice}/download |