Connection guide

Connecting a workspace to Solar Engine

Solar Engine is a platform UK solar installers use to produce quotes, proposals and grid paperwork. A company on Solar Engine connects its own Google Workspace or Microsoft 365 business mailbox (info@ or enquiries@ — never a personal account) so the team can send and receive email and manage bookings from one place. If you were sent here, the company needs this connection made, and it takes admin access you hold.

What connecting actually does

It is a standard OAuth grant — the same mechanism any Google or Microsoft marketplace app uses. Solar Engine never sees or stores the account password.
The grant is scoped to one mailbox — the business mailbox that signs in — not the whole domain and not other users.
You can revoke it at any time (see undoing it), and it stops working immediately.

Google Workspace — the steps

Decide which mailbox is the company's sending identity — usually info@ or enquiries@. If it only exists as an alias, that works too: connect the account that carries the alias.
Open the connection step in the company's Solar Engine workspace and press Connect Google Workspace, signing in as that mailbox — or grant the person doing the setup access to the mailbox.
If your Workspace restricts third-party apps, approve the consent when Google asks — or pre-approve the app under Admin console → Security → API controls → App access control. Google's own doc: Control which third-party apps access Google Workspace data.

Exactly what Google will show on the consent screen

gmail.send	Send email as the connected mailbox.
gmail.modify	Read and label the mailbox's messages — how replies reach the CRM and get marked handled — and list the addresses the mailbox may already send as, so a job can be given one of them.
calendar.events.owned	Create and update the bookings Solar Engine itself makes.
calendar.freebusy	Read busy/free times so bookings avoid clashes.
admin.directory.user.alias	Add an alias such as enquiries@ to the connected mailbox. Asked for only when you press Create alias, and only works for a Workspace admin.

Microsoft 365 — the steps

Decide which mailbox is the company's sending identity — usually info@ or enquiries@.
Open the connection step in the company's Solar Engine workspace and press Connect Microsoft 365, signing in as that mailbox — or grant the person doing the setup access to it.
If your tenant requires admin consent for new applications, approve it when Microsoft asks — or grant it under Entra ID → Enterprise apps → All applications → select the app named on the consent screen → Security → Permissions → Grant admin consent. Microsoft's own doc: Grant tenant-wide admin consent to an application.

Exactly what Microsoft will show on the consent screen

Mail.Send	Send email as the connected mailbox.
Mail.ReadWrite	Read the mailbox's messages and mark them handled — how replies reach the CRM.
User.Read	Read the mailbox's own profile and its send-as addresses.
Calendars.ReadWrite	Create and update bookings on the mailbox's calendar.
User.ReadBasic.All	List the company's mailboxes, so a job can be given one. Asked for only when you press Pull the company's mailboxes.
Mail.ReadWrite.Shared	Read a shared mailbox you assign, so its replies reach the CRM. The connected account needs Full Access on it.
Mail.Send.Shared	Send as a shared mailbox you assign. The connected account needs Send As on it.

Undoing it

Google: Admin console → Security → API controls → Manage third-party app access (Google's doc), or from the mailbox itself at myaccount.google.com → Security → Third-party access (Google's doc).
Microsoft: Entra ID → Enterprise apps → All applications → the app named on the consent screen → Properties → Delete (Microsoft's doc; deactivating instead of deleting also stops sign-ins), or from the mailbox at myaccount.microsoft.com → App permissions.

When you're done

Reply to the email that brought you here — it goes straight to the person who asked, not to a ticket queue. Nothing at the company is blocked while this waits: their workspace keeps working, and mail simply starts flowing once the connection lands.

More guides: solarengine.co.uk/guides. Questions about this page — reply to the email that linked you here.