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

# Roles and permissions

> What each role can see and do.

Every person has one role. The role decides what they see and what they can change.

## The roles

| Role | Best for |
| - | - |
| **Administrator** | Owners and managers who run the whole workspace |
| **Operations** | Office staff who run projects, installs and settings |
| **Sales manager** | Leads a sales team. Sees their own customers and their reps' customers |
| **Sales representative** | Sells. Sees their own customers and unassigned leads |
| **Finance** | Accounts. Can see everything but changes very little |
| **Technician** | Installers. Only sees their own jobs in the **Work** app |
| **External marketing** | Outside lead suppliers. Adds leads and sees their own results |

> [!NOTE]
>
> **Developer** is a role used only by ArcSolar staff. You can't invite or edit it.

## Who can do what

| Task | Admin | Ops | Sales mgr | Sales rep | Finance | Ext. marketing |
| - | :-: | :-: | :-: | :-: | :-: | :-: |
| Add customers and leads | ✓ | ✓ | ✓ | ✓ | – | ✓ |
| [Import leads](https://docs.arcsolar.com.au/customers/import-leads.md) and copy the [intake form](https://docs.arcsolar.com.au/customers/intake-form.md) | ✓ | ✓ | ✓ | ✓ | – | ✓ |
| Assign customers to reps | ✓ | ✓ | ✓ | – | ✓ | – |
| Create and send quotes | ✓ | ✓ | ✓ | ✓ | – | – |
| Change [pricing](https://docs.arcsolar.com.au/setup/pricing.md) | ✓ | ✓ | – | – | If allowed | – |
| Take and adjust payments | ✓ | ✓ | View only | – | ✓ | – |
| Run projects and installs | ✓ | ✓ | – | – | View only | – |
| See reports | ✓ | ✓ | Their team | Their own | ✓ | Their leads |
| Invite people and change roles | ✓ | – | – | – | – | – |
| Suspend and reactivate people | ✓ | ✓ | – | – | – | – |
| Remove people (offboard) | ✓ | – | – | – | – | – |
| Open **Team & Access** | ✓ | ✓ | – | – | View only | – |

Sales reps can only import leads for themselves. External marketing sees either only the leads they added or all records. You choose this when you invite them.

## Agent follows the same rules

[Agent](https://docs.arcsolar.com.au/agent.md) can only do what your role allows. A sales rep can't use Agent to change pricing, for example.

## Change someone's role

Only **Administrators** can change roles. See [Team and access](https://docs.arcsolar.com.au/setup/team.md#change-a-role).

[Continue with**Invite your team**](https://docs.arcsolar.com.au/setup/team.md)


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