Getting started
Sign up, connect your first integration, import sites, invite your team — the smallest path to a live portfolio.
1. Create an account
Sign up at solarfleet.io. The first user becomes the organisation owner. Owners can invite anyone else and assign roles later from Settings.
During onboarding you'll be asked what kind of organisation you are — installer, operator, or both. This gates one optional feature: the Quote Mode tab is hidden for pure operators because it's an installer workflow. Everything else is the same.
2. Connect an integration
Settings → Integrations. Both integrations use API credentials, not your dashboard password. SolarFleet polls Solis Cloud every 5 minutes. SolarEdge is polled regularly through your own SolarEdge App API key, but every call counts against your SolarEdge API plan's per-minute and monthly limits, which are shared across every site on the key — so a small plan can't refresh a large fleet as often as a bigger one.
- SolarEdge. SolarFleet uses SolarEdge's monitoring API (V2) with an App API key your organisation creates at developer.solaredge.com: Create Application → Monitoring API → Fleet Access → My Fleet. Paste the key with the expiry date you chose (3, 6 or 12 months) and your SolarEdge API plan; we remind your owners by email 30, 14 and 3 days before the key expires. If some of your sites belong to another SolarEdge account, that account shares them with yours under Account Details → Associated Accounts in the SolarEdge portal. Keys from SolarEdge's old (V1) API stop working on 3 November 2026.
- Solis Cloud. Authenticate with the API ID + secret from your Solis console.
3. Import sites
Once an integration is connected, you'll see a list of every site the API exposes. Tick the ones you want SolarFleet to manage and hit Import. The first sync pulls equipment, recent telemetry (a couple of weeks by default), and any open alarms.
Sites for brands we don't yet have an integration for can be created manually. They won't auto-import telemetry, but everything else — cases, maintenance visits, BS EN 62446-1 reports, client PDFs — works the same.
4. Invite your team
Settings → Users. Invite by email and pick a role:
- Owner. Everything, including billing and deletion. Only owners can invite owners or admins.
- Admin. Sites, integrations and member invites. Billing, organisation-wide settings and role changes stay with owners.
- Member. Read/write on operational data (sites, cases, visits, reports). No settings changes.
There's no client role yet — a read-only client portal is on the roadmap. Don't invite end-customers as users (every role sees the whole portfolio); share data with them through reports.
5. Set up notifications
Settings → Notifications. Pick which events you want emails or push for: critical alerts, daily digests, visit assignments, case mentions. Each user controls their own preferences. The defaults are sensible — critical alerts on, info-level digest weekly.