NuAgent Docs

Work & Enterprise Accounts

Connecting a company email (Google Workspace or Microsoft 365) when your brokerage manages your account.

If your email is a company address — like your.email@brokerage.com — your brokerage's IT team controls which apps can connect to it. Connecting works the same way as a personal account, but your organization may need to approve NuAgent first. This page explains what to expect and exactly what to hand your IT team if you get stuck.

Personal Gmail / Outlook? You don't need this page.

A personal @gmail.com or @outlook.com account connects in one click — see Gmail & Outlook. This page is only for company-managed accounts.

First, just try connecting

Connect as usual

Go to Settings → Integrations and click Connect Gmail or Connect Outlook. Sign in with your work address.

If it works, you're done

Many organizations allow this directly. Your inbox starts syncing and there's nothing more to do.

If you see "approval required"

If you hit a screen like "Admin approval required," "This app is blocked," or "NuAgent hasn't been approved by your organization," your IT team needs to approve NuAgent once. Send them the section below.

What NuAgent accesses

So you (and your IT team) know exactly what's being granted:

PermissionWhat it's for
Read emailLink messages from your CRM contacts to their profiles
Send emailSend messages from NuAgent through your account
Calendar (Outlook)Sync events and showings

NuAgent only surfaces emails tied to contacts in your CRM — your personal correspondence stays private. NuAgent never reads other employees' mailboxes; each person connects their own account individually.


For your IT administrator

Hand this section to your IT / security team

An end user is asking to connect their mailbox to NuAgent, a real-estate CRM. NuAgent uses standard per-user OAuth — each user grants access only to their own mailbox; there is no domain-wide or service-account access to other employees' email. To allow it, do one of the following depending on your email platform.

Google Workspace

The user is requesting the Gmail scopes gmail.readonly and gmail.send. In the Google Admin console:

Open app access control

Go to Security → Access and data control → API controls → Manage Third-Party App Access.

Add NuAgent as a trusted app

Choose Add app → OAuth App Name or Client ID, search for NuAgent (or paste the OAuth client ID NuAgent support provides), and set it to Trusted.

Confirm scope

Trusting the app covers the Gmail read/send scopes above. Users can then connect without the block screen.

Microsoft 365 (Entra ID)

The user is requesting the delegated Microsoft Graph permissions Mail.Read, Mail.Send, Calendars.ReadWrite, and offline_access. If user consent is disabled in your tenant, an admin grants consent once:

Open the admin-consent URL NuAgent support provides (it points at login.microsoftonline.com/.../adminconsent), sign in as a Global Admin or Privileged Role Admin, and approve. This registers NuAgent under Entra ID → Enterprise applications.

Alternatively, under Enterprise applications → Consent and permissions, allow user consent for verified apps and these delegated scopes — then users can self-approve.

What NuAgent does *not* request

No application (app-only) permissions, no domain-wide delegation, no access to other users' mailboxes. Granting access is per-user and revocable at any time — Google: Admin console → API controls; Microsoft: Entra ID → Enterprise applications → NuAgent → remove.

Once approved

Return to Settings → Integrations, click Connect again, and your work inbox will sync. If you're still blocked after your admin approves NuAgent, contact support and we'll provide our exact OAuth client ID / admin-consent link for your IT team.

On this page