> ## 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.

# Installers

> Keep your installer directory current and assign the right installer to each job.

[**Installers**](https://app.arcsolar.com.au/dashboard/installers) is your directory of installation companies and crews. A project can only be assigned to an installer listed here.

![The Installers table listing five installer companies with their capabilities, service regions, availability, active jobs and status.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/dl-installers.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=711de92155a33445dcfefa84883877a8)

The installer directory shows capabilities, regions, availability and active jobs. Sample data.

## Add an installer

1. Choose **Add installer**.
2. On **Details**, enter the **Business name**, **Legal name**, **ABN**, **Business email** and **Business phone**.
3. Set the **Directory status**. Only **Active** installers can be assigned to jobs.
4. Turn on **Preferred installer** to show this partner first when you assign work.
5. Add the primary contact and business address.
6. On **Coverage**, choose the **Capabilities** (such as **Solar**, **Battery** or **Solar + Battery**) and **Service regions**.
7. On **Capacity**, add when they are available and how much work they can take. You can skip this and add it later.
8. Choose **Add installer**.

## Review an installer

Choose **View** on a row to open the record.

![An installer record showing status badges, primary contact, availability and the Capacity, Business details, Coverage, Compliance and Technician access sections.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/dl-installer-detail.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=2a0fe2bc498bdce16876eab1453fc151)

An installer record. Expand each section for the detail. Sample data.

| Section | What to check |
| - | - |
| **Capacity** | Units of work available and the next available date |
| **Business details** | Legal entity, ABN, address and contact details |
| **Coverage** | Capabilities and service regions |
| **Compliance** | Electrical licence, accreditations, public liability, workers compensation and safe work method, each with its status and expiry |
| **Technician access** | The team member who signs in to the Work app for this installer |

Choose **Edit installer** to change any of it. Keep compliance documents current. An expired item can stop the installer being offered for new jobs.

## Give the installer a sign-in

An installer record is not a login. To let a technician see their jobs in the [Work app](https://docs.arcsolar.com.au/delivery/job-portal.md):

1. In [**Team & Access**](https://app.arcsolar.com.au/dashboard/team-access), invite the person with the **Technician** role. See [Team](https://docs.arcsolar.com.au/setup/team.md).
2. Ask them to accept the invitation.
3. Open the installer, expand **Technician access** and choose them under **Technician user**.
4. Choose **Save technician user**.

A pending invitation does not give access yet.

## Assign an installer to a project

1. Open the project in [**Projects & Jobs**](https://app.arcsolar.com.au/dashboard/projects).
2. On **Overview**, expand **Associate an installer** in the **Delivery checklist**.
3. Pick the installer from **Associate to installer**.

![The Delivery checklist with Associate an installer expanded, showing the Associate to installer menu.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/dl-assign-installer.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=45aa2d62f4b4d0b4fa566dbaec0b8fb3)

Only installers who cover the site's state and the job type are listed. Sample data.

The list only shows active installers who service the site's state and can do this type of job. If it shows **No eligible installers service this state and job type.**, check the installer's **Coverage** and **Directory status**.

Then choose **Add installation date** under **Review installation schedule**. See [Projects and jobs](https://docs.arcsolar.com.au/delivery/projects.md#schedule-the-installation).

## Remove an installer

1. Choose **Select**, then tick the installers to remove.
2. Choose **Delete**.
3. Choose **Confirm delete**.

They are removed from the directory and from assignment options. Past projects and jobs keep their records. You can't remove an installer who has active work.

[Continue with**Field operations**](https://docs.arcsolar.com.au/delivery/field-operations.md)


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