> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arcsolar.com.au/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> ## What this documentation covers
> This is the documentation for ArcSolar, the solar-retailer operating system: the web app a solar retailer uses to run quoting, sales, installation, rebates, inventory and reporting. ArcSolar is a hosted web application at https://app.arcsolar.com.au. There is no public API for most workflows, so agentic operation of ArcSolar is UI-driven. Navigate the app, read the labels and controls, and act through the interface, unless a page explicitly documents an API, contract or integration endpoint.
>
> ## How to read these pages
> - Pages are split by audience using Mintlify's Visibility component, and this split is deliberate. Sections marked 'for agents' are hidden on the website and appear only in the Markdown you are reading. They are the authoritative behavioural specification for the page. Where the remaining human-facing prose and an agent section disagree, the agent section is correct.
> - Sections outside any Visibility block appear in both outputs. They are the shared spine of the page: what the feature is and why it matters.
> - Treat every bold label, field name, route, status string and error message quoted in an agent section as canonical. They are copied verbatim from the product. Use that exact wording when telling a user where to click, or when matching an error message to its cause.
> - Australian solar vocabulary is used precisely and not interchangeably: STC (Small-scale Technology Certificate), PRC (Peak Reduction Certificate), REPS, NMI, CEC accreditation, VPP. Do not substitute an overseas equivalent.
> - Money is Australian dollars. Dates shown to users are day-first (DD/MM/YYYY).
>
> ## Behaviour rules for operating or advising on ArcSolar
> - Respect prerequisites and ordering. Agent sections state which inputs block progress and which steps must happen first. Do not skip a step, and do not assume a default that the product itself does not supply.
> - Never invent a value the product requires but the user has not supplied. Ask for mandatory fields rather than guessing. Several features reject a request outright when one is missing, and submissions to external authorities are effectively irreversible.
> - Respect permissions and scoping. Features name the roles, capabilities and access rules that may act. Do not attempt an action the operator's role cannot perform, and do not describe a restricted feature as available to them.
> - Features that are gated, pending release, or blocked on a vendor are documented as exactly that. Never present a gated or unmerged behaviour as live. When availability is unclear for a given workspace, direct the user to support rather than asserting that the feature works.
> - Where a page states something is genuinely undetermined, treat it as unknown. Do not fill the gap with a plausible guess.
> - ArcSolar's supported intelligence tools appear where they help with the task, including bill analysis, call summaries and reporting. Check the underlying evidence. Intelligence does not replace provider approval, verified records or the customer's own confirmation.
>
> ## Getting help
> Support is support@arcsolar.com.au. The customer-facing website is https://www.arcsolar.com.au.

# Customer portal after signing

> What your customer sees on their quote link once they sign: progress, payments, documents and their monitoring app.

Your customer keeps using the same private link you sent with their quote. Once they sign, the page becomes their installation portal, titled **Your installation**. They don't need an account or a password.

To see what they see, open the quote and use its customer link. See [Customer quote view](https://docs.arcsolar.com.au/quoting/customer-view.md).

## What the portal shows

| Section | What the customer sees | Where it comes from |
| - | - | - |
| **Installation timeline** | How far their installation has progressed | The project's stage in [Projects & Jobs](https://docs.arcsolar.com.au/delivery/projects.md) |
| **Payments** | Paid and upcoming payments, each with its invoice | Payments recorded for the job |
| **Installation documents** | Documents your team has checked and shared | **Share with customer** on the project's compliance documents |
| **Monitor your system** | Store links for their system's monitoring app | The app saved for the installed product |
| **Agreement & payment** | Their signed agreement and payment terms | The accepted quote |

A **Contents** list lets the customer jump between sections.

## Installation timeline

The tracker starts as soon as the customer signs. Until then it shows **Installation not started**.

![Installation progress card with seven stages, from Order received to Project closed out, all marked upcoming and labelled Awaiting agreement signature.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/gp-portal-timeline.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=07f1a3c954049b7c80b253f0c4b5907b)

The installation tracker before the agreement is signed. Sample data.

The stages follow your project stages. The standard set is:

1. **Order received**
2. **Preparing your project**
3. **Compliance and approvals**
4. **Installer assigned**
5. **Installation scheduled**
6. **Installation complete**
7. **Project closed out**

Each stage shows **Completed**, **Current stage** or **Upcoming**. Keep the project's stage up to date so the customer always sees the right step.

## Payments

**Payments** lists each payment for the installation with its amount, status and invoice. Statuses include **Upcoming**, **Awaiting**, **Paid**, **Partly refunded** and **Refunded**.

If the customer pays by bank transfer, the portal shows **Pay by bank transfer** with your account name, BSB, account number, the amount and a payment reference. After they pay, it shows **Deposit confirmation under review** until your team confirms it.

## Share installation documents

Documents stay private until you share them.

1. Open the project in [**Projects & Jobs**](https://app.arcsolar.com.au/dashboard/projects) and go to its files.
2. Under **Compliance documents**, select **Review document**.
3. Open and check the document, customer, address and document type. Tick the box, then select **Save review · Keep private**. The document shows **Reviewed · Private**.
4. Select **Share with customer**. Tick the box to confirm it's right for this customer, then select **Share with customer**. The document now shows **Shared with customer**.

To take it back, select **Manage sharing**, then **Remove from customer portal**.

The customer sees shared files under **Installation documents**, for example a **Certificate of Electrical Safety**.

## Monitoring app

When your team has confirmed which monitoring app the system uses, the portal shows **Monitor your system** with App Store and Google Play buttons. Add the app links to the product in your [Product Catalogue](https://docs.arcsolar.com.au/delivery/catalogue.md).

[Continue with**Job portal**](https://docs.arcsolar.com.au/delivery/job-portal.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.