Recommended approach: Add Nectar as a Guest User
NJNG grants third-party access by adding a Guest User to your account. You’ll generate a dedicated Nectar email address in the connection wizard, then enter that email — along with Nectar’s name on NJNG’s portal.Step 1: Generate your Nectar forwarding email
In the connection wizard, select Option 1: Managed MFA forwarding. You’ll be asked to enter your own email address — this is where Nectar will forward any MFA codes or notifications it receives, so you stay in the loop.1
Start the NJNG connection or reconnect
From Data Input > Connections, click New connection and select NJNG, or click Reconnect on an existing connection showing MFA Token Expired. When the wizard reaches the MFA step, choose Option 1: Managed MFA forwarding.
2
Enter your own email as the forwarding destination
Enter the email address where you’d like a copy of any forwarded messages to go. This is your address, not Nectar’s.
3
Copy the generated Nectar email
On the next screen, the wizard displays:
- A generated Nectar email address (unique to this connection — e.g., nectar-forward-to-your-company@nectarclimate.com)
Step 2: Add Nectar as a Guest User in NJNG
1
Log in to your NJNG account
Go to njng.com and sign in with your credentials.
2
Navigate to account access settings
Go to Account > Guest User > Invite User.
3
Add Nectar as a Guest User
Click Invite User and enter the values:
- Select Service Account Number
- Name: Nectar Climate
- Select Full access vs view only
- Email: (the generated Nectar email from Step 1 — e.g., nectar-forward-to-your-company@nectarclimate.com)
4
Confirm the invitation
NJNG sends an invitation to the generated Nectar email. Nectar accepts it automatically and begins pulling billing and usage data. The connection status updates to Connected, and any future notifications NJNG sends are forwarded to the email you entered in Step 1.
If you have multiple NJNG accounts
Each NJNG account (login) needs Nectar added as a Guest User separately. If you manage many NJNG accounts across your portfolio, contact support@nectarclimate.com — we can help coordinate bulk onboarding.Alternative: Email MFA forwarding
If you can’t add Nectar as a Guest User (for example, if you don’t control the account settings), forward NJNG’s verification code emails to a Nectar-provided address so we can complete login on your behalf:1
Start a new connection or reconnect
From Data Input > Connections, click New connection and select NJNG, or click Reconnect on an existing connection showing MFA Token Expired.
2
Enter your NJNG credentials
In the wizard, enter the username and password Nectar should use to log in to NJNG.
3
Get your Nectar forwarding address
The wizard provides a unique forwarding address for your organization (for example,
nectar-forward-to-your-company@nectarclimate.com). Copy it.4
Choose MFA forwarding type
The wizard presents two options:
- Managed forwarding: Nectar provides a unique email address (for example,
nectar-forward-to-your-company@nectarclimate.com). Update your NJNG account’s email address to this Nectar-provided address so codes are sent directly to us. - Customer-inbox forwarding (recommended): Keep your current email on NJNG, and set up an auto-forwarding rule in your email client to forward NJNG verification emails to the Nectar-provided address (for example,
nectar-forward-to-your-company@nectarclimate.com).
5
Set up email forwarding in your inbox
In the mailbox that receives NJNG verification codes, create a forwarding rule that sends messages from NJNG to the Nectar address from Step 3.
- Sender / from: the NJNG sender addresses your account uses
- Forward to: the Nectar address from Step 3
- Keep a copy in the original inbox if you still want to see the codes
6
Confirm the forwarding address (if required)
Most email providers send a confirmation code to the forwarding address before enabling the rule. Nectar receives and confirms this automatically, usually within a few minutes.
7
Confirm the setup
Nectar triggers a test login. When the verification code is forwarded successfully, the connection moves to Connected.