> ## Documentation Index
> Fetch the complete documentation index at: https://docs.spirii.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Installers

> Bring installation partners into Connect to get your chargers live.

An installer needs enough access in Connect to bring a charge box live, and no more. The Installer role is scoped for exactly that.

## Overview

An installation is the point where an order becomes a working charger: hardware mounted, configured, registered in Connect, and confirmed to charge. That work usually falls to a third party who works across several operators' sites and does not need to see what you charge for energy.

Where the installation came from an onboarding flow, the whole sequence runs without anyone coordinating it by hand.

```mermaid theme={null}
flowchart LR
    O("Order completed") --> R("Installation request\nrouted by postcode")
    R --> I("Installer registers\nthe charge box")
    I --> A("Charge box comes online") --> E("Order fulfilled email\nto the customer")
```

See [Onboarding flows](/capabilities/automation/onboarding-flows) for the ordering half and the email templates behind it.

## The Installer role

You invite an installer through Team Access and give them the **Installer** role, which reaches what an installation needs:

* Look up locations
* View, add, and configure charge boxes and connectors
* Send remote commands to a charge box
* View sessions, so an installation can be verified on the spot

It does not reach tariffs or pricing.

Access is scoped when you invite them. An installer can either reach every customer and location under your account, or a single customer and that customer's locations. Choose the narrower option for a partner working on one client's estate, and the broader one for a partner covering your whole territory.

## Before an installer arrives

Three things need to be in place, and all three are yours to arrange.

**A validated charge box model.** Spirii validates whether a model can connect to the platform at all. Confirm the model is validated before the hardware ships, because an unvalidated box cannot be registered.

**The charger's OCPP configuration.** Whoever configures the charger sets these on the unit itself:

| Setting             | Value                                                                                                          |
| ------------------- | -------------------------------------------------------------------------------------------------------------- |
| OCPP version        | 1.6J                                                                                                           |
| OCPP endpoint       | `wss://ocpp.spirii.com`                                                                                        |
| Charge box identity | A unique ID following eMI3 syntax. See [Charge boxes](/components/charging/charge-boxes) for the form it takes |

**A token for testing.** An installer verifies the installation by running a real session, so issue them an RFID token to test with.

## What an installer does in Connect

<Steps>
  <Step title="Find the site">
    From **Locations**, search for the site by address. In Nordic markets an installer can also look a site up by its order ID.
  </Step>

  <Step title="Record the installation details">
    On the location's **Overview** tab, enter the **main fuse capacity** of the installation. Load balancing distributes power within that figure, so a site with more than one charger depends on it being right.
  </Step>

  <Step title="Register the charge box">
    On the **Charge boxes** tab, add a charge box: its type from the list, or **Other** where the model is not listed; the serial number printed on the unit; and the charge box identity.
  </Step>

  <Step title="Wait for it to connect">
    A correctly configured charger reaches the platform within five to ten minutes. Once it sends its first boot notification, Connect fills in the vendor, model, firmware, and connectors on its own. Some models need a reboot before they retry.
  </Step>

  <Step title="Test a session">
    Start a session with the token you issued, and confirm it appears in Connect. Authentication is enabled on every charge box by default, so a token that is bound correctly will start the session.
  </Step>
</Steps>

<Note>
  The charge box identity entered in Connect has to match the OCPP identity configured on the charger exactly. A mismatch is the most common reason a correctly installed charger never appears online.
</Note>

## Dependencies & limitations

* **Installers cannot see tariffs or pricing.** The role reaches locations, charge boxes, connectors, and sessions.
* **Access is scoped per installer.** Each one covers either every customer under your account or a single customer's locations.
* **Only validated models can be registered.** Spirii validates whether a charge box model can connect to the platform.
* **Moving or recreating a charge box is an operator action.** An installer cannot move a box between locations or recreate a deleted one.

## Related

Invite your installer through Team Access, then hand them the OCPP values above.

<CardGroup cols={2}>
  <Card title="Onboarding flows" icon="workflow" href="/capabilities/automation/onboarding-flows">
    The order that triggers an installation request, and the emails around it.
  </Card>

  <Card title="Team access" icon="lock" href="/capabilities/account/user-management">
    Inviting an installer and scoping what they reach.
  </Card>

  <Card title="Charge boxes" icon="plug" href="/components/charging/charge-boxes">
    What a charge box is, and how identity and connectors work.
  </Card>

  <Card title="Remote commands" icon="terminal" href="/capabilities/operation-monitoring/remote-commands">
    The commands an installer can send during commissioning.
  </Card>
</CardGroup>