> ## 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 built-in assistant is called ArgonixIntelligence. Pages end with an 'ArgonixIntelligence in this workflow' section stating what intelligence can and cannot reason from in that workflow. Treat those limits as binding: intelligence does not replace provider approval, verified evidence, or a customer's own confirmation, and it must not be presented as if it does.
>
> ## Getting help
> Support is support@arcsolar.com.au. The customer-facing website is https://www.arcsolar.com.au.

# Find your way around ArcSolar

> Move between screens quickly and set the workspace up to suit you.

ArcSolar puts your work in a sidebar and keeps a search box and a preferences panel within reach on every screen.

## Move between screens

* The sidebar is grouped as **Workspace**, **Operations**, **Business** and **Settings**.
* Entries are filtered by the member's role and by runtime mode. A missing entry usually means a capability the role does not hold, not a broken workspace. Route access questions to [feature availability](/reference/availability) rather than asserting the feature is absent.
* Some entries are deliberately disabled and carry a **Soon** badge. Do not present them as working features.

## Find a screen quickly

* Keyboard shortcut: ⌘J (meta) or Ctrl+J toggles the search dialog. It is a toggle — pressing it again closes the dialog.
* The dialog placeholder is "Search the workspace…".
* It searches **navigation entries**, built from the same role-filtered sidebar items as the sidebar itself. It does **not** search customers, quotes, projects or other records. Do not describe it as a global record search.
* Disabled entries appear but cannot be opened.
* Entries flagged to open in a new tab open a new browser tab rather than navigating in place.

## Set up the workspace to suit you

* The **Preferences** panel (header) exposes: **Theme Preset**, **Theme Mode** (**Light** / **Dark** / **System**), **Fonts**, **Navbar Behavior**, **Page Layout**, **Sidebar Style** and **Sidebar Collapse Mode**, plus a reset.
* **Theme Mode** is the dark-mode control. **System** follows the operating system rather than a fixed choice.
* These are per-person preferences, not organisation settings. Do not describe them as team-wide or as branding (organisation branding is configured in Retailer Settings).

## Check what needs your attention

* The header bell is the **Operational inbox**; its tooltip is "Operational inbox". The aria-label is "Open operational inbox", becoming "Open operational inbox, N items need attention" when any item has `needsAttention`.
* The panel title is **Operational inbox** and its description is "Mentions, customer uploads, assigned work, and missed calls that need attention."
* Live groups are **Needs action**, **Assigned projects** and **Recently read · latest 30**. Empty state: **Nothing needs your attention** — "Mentions, customer uploads, assigned work, and missed calls will appear here." Unavailable state: **Inbox temporarily unavailable**, "Notifications could not be loaded right now. Refresh the dashboard to try again."
* **Needs attention** means: an unread notification; a task you own that is not completed or cancelled; a project you own as sales or operations owner; or a missed or in-progress inbound call. Read notifications are not attention items.
* Item labels include **Assigned task**, **Assigned project**, **Missed call**, **Incoming call**, **Mention**, **Task update**, **Calendar**, **Operations query**, **Upload complete**, **Lead assigned** and **Monthly report**, across the Comms, Finance, Operations, Reporting and Sales areas.
* **Mark read** appears only on unread notifications, calling `mark_workspace_notification_read`. Missed and in-progress calls, and owned tasks and projects, clear from the inbox by changing the underlying record rather than by being marked read.
* The inbox is rendered in the dashboard header and on the Comms page, and polls while the tab is visible. Do not describe it as an email inbox.

## Your profile and password

* Personal account controls live under **Profile Settings** (`/dashboard/profile-settings`), the per-person destination whose eyebrow label is **Per person**. The page is titled **Profile Settings**.
* **Personal details** card: "Manage the name shown in the ERP and your private contact email." It contains the profile picture editor plus display name and contact fields.
* **Profile picture.** Accepted types and limits are stated as "JPEG, PNG or WebP · Max 5 MB". A source image larger than 16 megapixels is rejected with "Choose an image smaller than 16 megapixels." The crop dialog is **Crop your profile picture** — "Drag your picture to reposition it. Use zoom to adjust the crop." — saved with **Save picture**. Removal asks "Remove your profile picture?" and keeps initials instead. Success toasts are "Profile picture saved" and "Profile picture removed".
* **Change password.** Dialog title **Change password**, description "Confirm your current password, then choose a new one for this account." Fields are **Current password**, **New password** and **Confirm new password**, with the hint "Use at least 8 characters and avoid reusing another password." The action is **Update password** (in flight, **Updating…**). Success is the toast "Password changed" — "Use your new password the next time you sign in." A failure asks the user to sign in again and retry.
* The controls are disabled when `canManageIdentity` is false, which is the case in a demo workspace; the page then shows the alert **Prototype identity**. Do not tell a user to change a password where the environment does not allow it.

## Hear about changes in the app

* A dismissible in-app announcement dialog describes recent changes. Dismissal is stored per member, so a dismissed announcement does not return.
* The announcement reports what has shipped; [what's new](/reference/whats-new) distinguishes live behaviour from *Pending* and *Built but switched off*. Do not treat either as confirmation that a specific workspace has received a change.

## When something goes wrong

Report it from **Report a problem** at the bottom of the sidebar — see [Get help from ArcSolar](/reference/support).

## ArgonixIntelligence in this workflow

ArgonixIntelligence answers from the data and screens you can already reach. It does not widen your permissions, and an answer about where something lives is still worth confirming on the screen itself.


## Related topics

- [Your first chapter with ArcSolar](/sales-onboarding.md)
- [Welcome to ArcSolar](/index.md)
- [The customer journey](/quickstart.md)
- [Retailer Settings or ArcSolar Settings or Profile Settings?](/setup/settings-screens.md)
- [Get help from ArcSolar](/reference/support.md)