If you are accessing Nectar through Microsoft Teams or an embedded iFrame on your company intranet (such as SharePoint), you will need to complete a quick, one-time authentication process.
đĄ Tip: You will only need to complete this verification process once, unless your browser cookies or cache are cleared.
How do I authenticate my Nectar account in Microsoft Teams?
If you are using Microsoft Teams, follow these steps to open Nectar and begin the sign-in process:
Open the Nectar app: Click the Nectar tab on the left sidebar of your Teams window.
Note: If you donât see it, click the ellipsis (...), search for "Nectar", and select the app. You can right-click the app icon to pin it to your sidebar.
Enter your email: Type your company email address into the field and click Continue.
How do I generate and paste my SSO login code?
Once you click continue, Nectar will use Secure Single Sign-On (SSO) to verify your identity through a separate window.
Log into your identity provider: A new browser tab will automatically open. Sign into your company's SSO provider (such as Google Workspace or Microsoft).
Copy your unique login code: After a successful login, an authentication screen will appear. Click the Copy Login Code & Continue button. This action automatically copies the code to your clipboard and closes the tab.
Paste the code to log in: Return to your Teams window or company intranet iFrame. Paste the copied code into the designated login box and click Login.
You are now successfully signed into Nectar!
Common Login Issues and Causes
Microsoft Teams Cache Needs to Be Cleared (macOS): If the SSO sign-in window is looping, not loading correctly, or repeatedly prompting you to log in, Teams may be using outdated cached credentials. Quit Microsoft Teams completely, clear the Teams cache on your Mac, then reopen Teams and try signing in again. Follow Microsoftâs official steps here: https://learn.microsoft.com/en-us/troubleshoot/microsoftteams/teams-administration/clear-teams-cache#clear-the-cache-in-teams-for-macos
Browser Session or Cookies Are Interfering with SSO: Because Nectar opens SSO verification in a separate browser tab, an existing (or conflicting) login session in your browser can block authentication. Try signing out of other accounts in the browser, using an Incognito/Private window, or switching to a different browser, then restart the login flow from Teams.
SSO Profile Mapping Mismatch: When you sign in using SSO, Nectar matches your login to a Nectar user account using details provided by your companyâs identity provider (most commonly your email address). If the email/username coming from SSO doesnât exactly match the email on your Nectar account (for example: alias vs. primary email, a recent email change, or a different Microsoft/Google account already signed into the browser), authentication may fail. Confirm youâre signing into the correct work account and ask your IT team or Nectar admin to verify the SSO email/identifier matches the email on your Nectar profile.




