Docs / Pages

My applications (customer)

The customer's home page: every credit application the business has sent to suppliers, with status and approved credit.

/contractor/dashboard is where a customer lands after sign-in. /contractor/applications redirects here. (The path says "contractor" for historical reasons; it is the customer area.) In the left menu this page is the row Applications (the same word the supplier menu uses); the page title stays "My applications".

Who can use it#

Customer users whose role holds applications.view. A Buyer sees the applications they created; Owner, Administrator and Buyer Manager see the whole organization's. Suppliers and staff are sent to their own areas.

What it shows#

From top to bottom:

  • Gate notice: when applications.create is blocked (business details open, or required verification in review) a panel says why, whether anything is needed from you (verification in review needs nothing), what you can still do (browse Find vendors, save references, invite colleagues, each only if your role may) and one button to the step that unblocks you.
  • Needs you (n): work waiting on you, newest first, hidden when empty. Kinds: a supplier wrote the last message on an open application (Reply), a reference did not respond, link expired or declined (Resend, or Open for a role without references.remind), a draft untouched for 7 days (Continue). Each row names the application code and opens the right place on its detail page.
  • Accounts: approved accounts across all pages, the payment terms in days in use ("Net 30 x2, Net 60") and the sum of approved limits. Hidden until something is approved.
  • Status tabs (All, Draft, Submitted, In review, Approved, Declined) and the applications table: supplier, status, requested and approved limit, terms (days), references, date. On a phone each row is a two-line card. A row opens /contractor/applications/<id> (Application detail). Statuses use the shared vocabulary; "Declined" is the same word everywhere.
  • Finish setting up: a task list (every task with its status, any order) that leads the page for a first-time customer and sits under the table until finished.
  • Start application opens /apply and needs applications.create; without it the button is disabled with the role that holds it.

Test hooks: needs-you-item, accounts-line, app-row (with data-status), app-tab-<status>, gate-notice, setup-task-<step>.

Empty and error states#

A first-time customer sees "You have not applied to a supplier yet" instead of zeros. If the list cannot load the page shows a retry message.

Customer applying, Account settings for business verification.