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

# Google Sheets

> Copy each lead intake form submission into a shared Google Sheet.

When someone submits your public [lead intake form](https://docs.arcsolar.com.au/customers/intake-form.md), ArcSolar adds them to Customers. With Google Sheets connected, it also adds a row to one Google Sheet. This helps if your team already works from a spreadsheet.

Only an Administrator can connect or disconnect Google Sheets.

## What syncs

* Only new lead intake form submissions. Existing customers are not copied.
* Rows go to a tab called **ArcSolar Leads**, which ArcSolar creates if it is missing.
* Columns: Submission ID, Submitted at (UTC), Customer name, Email, Phone, Lead source, Sales agent, Address, Ideal meeting (UTC), Preferred days, Preferred times, Document, ArcSolar customer reference.
* Sync goes one way, from ArcSolar to the Sheet. Edit customers in ArcSolar, not in the Sheet.

## Connect a Sheet

**1. Create a dedicated Sheet**

Make a new Google Sheet just for leads. It will hold customer contact details. Keep **General access** set to **Restricted**.

**2. Open the connection form**

Open [**Retailer Settings → Integrations → Google Sheets**](https://app.arcsolar.com.au/dashboard/quoting-settings?tab=integrations) and select **Sync to Google Sheets**.

**3. Paste the Sheet link**

Paste the Sheet's address into **Google Sheet URL**.

**4. Share the Sheet with ArcSolar**

Select **Copy ArcSolar email**, then **Open Sheet to share**. In Google Sheets, select **Share**, add the copied address as an **Editor**, and send. Share the file only, not its folder.

**5. Connect**

Back in ArcSolar, select **Connect sheet**. The status changes to **Connected**.

![Google Sheets connection settings with the Google Sheet URL field, Connect sheet and Cancel buttons.](https://mintcdn.com/arc-solar/ERA6sYSpHiPDrpGK/images/v2/ri-google-sheets-connect.png?fit=max\&auto=format\&n=ERA6sYSpHiPDrpGK\&q=85\&s=f079d2cbd76d19e04700cd27d132eb81)

The Connect a spreadsheet form. In the sample workspace the sharing address is not shown.

## Change or disconnect

* **Change Google Sheet** connects a different Sheet. Remove ArcSolar from the old Sheet's sharing to revoke its access.
* **Open connected Sheet** opens the current Sheet.
* **Disconnect** stops sync. New leads still go into Customers. Rows already in the Sheet stay there. Remove ArcSolar's email from the Sheet's sharing to fully revoke access.

## If something goes wrong

Leads always go into Customers, even when the Sheet can't be updated. If the card shows a delivery problem, ArcSolar retries. If it says a delivery could not be verified, an Administrator needs to check the Sheet before those rows are sent again. **Last synced** shows the last successful update.


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