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

# Use ArcSolar in AI apps

> Work with ArcSolar from Claude, ChatGPT, Cursor and other AI apps, with exactly your own permissions.

Connect ArcSolar to an AI app such as Claude or ChatGPT. Then ask about your customers, quotes and jobs, or ask the app to do a task, without opening ArcSolar.

ArcSolar uses the **Model Context Protocol (MCP)**, the standard way AI apps connect to other software. Any app that supports remote MCP servers can connect.

> [!NOTE]
>
> AI apps are available to every role in every ArcSolar workspace. There's nothing for an administrator to turn on. To connect, see [Connect an AI app](https://docs.arcsolar.com.au/ai-apps/connect.md).

## It acts as you

* The app can only do what **your role** allows. If you can't see a customer in ArcSolar, the app can't either. See [Roles and permissions](https://docs.arcsolar.com.au/setup/roles.md).
* You sign in **in ArcSolar**, never in the AI app. The app never sees your password.
* It works in **one organisation at a time**.
* Every action is recorded against your name. You can see the last 30 in **Settings → AI apps → Recent AI activity**.

## You confirm anything that matters

Looking things up happens straight away. For anything that contacts a customer or a team member, or can't easily be undone, the app first shows you a preview. It only goes ahead after you say yes.

* Previews expire after 10 minutes. Ask again if one expires.
* Bulk price changes run as a dry run first, so you see every change before it's saved.
* A **Read only** connection can look things up but can't change anything.

## What you can ask

| Area | Examples |
| - | - |
| Customers and leads | "Find Jane Citizen", "Add a solar and battery lead for Sam in Geelong", "Import the leads in this spreadsheet and assign them to me" |
| Quotes | "Where is the deal for Jane Citizen at?", "Did she open the quote?", "Why didn't the quote send?" |
| Payments | "Has the deposit been paid?" (read only) |
| Projects and jobs | "Is this job ready to install?", "Book the install for Friday", "Upload these site photos to the job" |
| Tasks and calendar | "What's on my calendar tomorrow?", "Create a follow-up task for Monday" |
| Products and pricing | "Export my price list", "Update prices from this supplier price list" |
| Reports | "Give me my weekly sales summary", "Show team activity this week" |
| Amy | "Why hasn't Amy called this lead?", "Show Amy's calls from yesterday" |
| Team (Administrators) | "Invite a new sales rep", "Resend Sam's invitation" |
| Help | "How do I import leads?" (answered from these docs), "Report this problem to ArcSolar support" |

## What AI apps can never do

* Change your plan, billing or subscription
* Collect, refund or void a payment
* Change anyone's role, or invite another Administrator
* Buy or release phone numbers
* Change Amy's settings
* Show passwords, tokens or keys
* Send free-form texts or emails to customers
* Permanently delete records
* Anything in ArcLeads

Do these in ArcSolar itself.

## What each role can reach

| Role | What AI apps can do |
| - | - |
| Administrator, Operations | Work across your organisation, within your role's permissions |
| Finance | Look across your organisation, including financials. No creating or sending quotes |
| Sales manager | Your own records and your approved team's. No company financials |
| Sales representative | Your own and unassigned customers, your quotes, tasks, calendar and messages, and your own reports. No company financials |
| Installer | Your assigned jobs and uploading site photos. No customers, quotes, messages or financials |
| External marketing | Shared lead outcomes only |

If the app says it can't find a record, it may exist but be outside what your role can see. ArcSolar never confirms records you can't reach.

## Your data

* What the app reads from ArcSolar is sent to the AI app's provider (for example Anthropic or OpenAI) under your agreement with them. Check your company's policy before you connect.
* ArcSolar records which action ran, when and whether it worked. It doesn't store your chat.
* Each connection lasts 30 days. Disconnect it at any time in **Settings → AI apps**.

> [!NOTE]
>
> Agent, the chat built into ArcSolar, works the same way inside the app. See [Agent](https://docs.arcsolar.com.au/agent.md).

[Continue with**Connect an AI app**](https://docs.arcsolar.com.au/ai-apps/connect.md)

**Facts for assistants.** Server URL: `https://app.arcsolar.com.au/mcp` (Streamable HTTP, OAuth 2.1 with PKCE, or a personal access token as a Bearer header). Settings: Profile settings → AI apps, `https://app.arcsolar.com.au/dashboard/profile-settings?tab=ai-apps`. Available to every role; not plan-gated; not available on the demo site. OAuth connections last 30 days; personal tokens 7, 30 or 90 days. Writes that contact people or can't be undone need a preview and confirmation token (10 minutes). On a connection granted several organisations, every change must name its `organisation`; reads default to the default organisation.


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