NEWLife After CRM->

GUIDES

How do I give AI agents access to my team's email safely? How GTM AI agents do it

Updated

The short answer. To give AI agents access to your team's email safely, set them up the way Day AI runs its GTM AI agents, the part of AI for GTM that does the work: each person connects their own inbox and chooses what it shares, each agent acts with the access of the one person it works for, every tool in chat is set to Always allow, Needs approval or Off, and email waits as a draft until a person sends it. Day AI gives every rep an agent set up this way, in place of their CRM or on top of Salesforce or HubSpot, with no shared account reading every mailbox.

Say you're the CEO of a consumer-services company, and it's 9:10 on a Thursday night. Your inbox is a three-person job: you, your chief of staff and your executive assistant all work it, and it's full of other CEOs, bankers and investors. The worry is always the same: a top-tier introduction that sits unanswered. When you connected Gmail to Day AI, you left your email sharing at Private, so your agent reads all of it because it works for you, and no teammate's agent reads a line, even though your chief of staff and assistant still work the inbox themselves. Your agent's evening recap, a skill with Private Data Access turned on so it can read your private mail, arrives in the same format as every night, and tonight it flags two items that need you, one of them a speaking invitation. You ask the agent for a reply. It writes a draft and stops there. You change one sentence and press Send yourself. Both items are caught that night, before you close the laptop. Nothing left your inbox that you didn't send.

Where the usual answer goes wrong. Most advice on this question starts with the plumbing: register an app, grant it access to every mailbox in the domain, store a token, and write a prompt telling the agent what not to read. That gives one agent the whole company's email and leaves the only real control in a sentence of the prompt. Day AI's position is that agents do the work and people approve it: each inbox stays under the person who owns it, each agent sees what its person may see, and a person decides what gets sent. Day AI provides the context graph and agent control plane to quickly and securely upgrade your company brain. If you've kept agents out of email until you had an answer to this, that was the right start.

Day AI's six email-access controls for GTM AI agents

Safe email access for agents comes down to six controls. The first two decide whose email exists to an agent at all, the next three decide what an agent may do with it, and the last keeps a person on every send.

  1. One inbox, one owner. Each person connects their own mailbox, so no single account holds everyone's mail. In Day AI, each person connects their own Gmail and Google Calendar from Settings, under Email and Meetings, and Google's consent screen lists the access Day AI asks for before anything connects.
  2. Private by default, shared on purpose. Nothing a person owns reaches the team until they choose. In Day AI, a work account starts with email Private when it's first connected, and each person sets Email Sharing Rules: share all or share none by default, with exceptions by domain, email address or Gmail label.
  3. Every agent works for one person. An agent should read what its person can read, and nothing more. In Day AI, an agent acts with the access of the person it works for, so a rep's agent reads that rep's private mail and the team's shared mail, and no one else's private mail.
  4. Scope every automated job. A skill that runs without you watching needs its own answer to "whose email?". In Day AI, a skill on your own agent has a Private Data Access switch, and a Managed skill deployed from the library reads only what's shared with the workspace.
  5. Set every tool. Decide tool by tool what runs, what asks first and what is off. In Day AI, each connector's Tool permissions section sets every tool to Always allow, Needs approval or Off for chat, and a skill reaches only the connectors picked in its own Connectors list.
  6. A person sends. The agent writes; the owner of the inbox decides what goes out. In Day AI, a one-off draft your agent writes stays private to you, and only the owner of the connected email account can send it.

How to give your team's agents email access with Day AI

Each step below is a setting in Day AI or a request to your Day AI agent. Where Salesforce or HubSpot stays in place, Day AI's agents read and update it live through its MCP server, with writes allowed when the write tools are turned on.

Step 1: Have each person connect their own Gmail to Day AI

Each person connects their Google work account during setup or later from Settings, under Email and Meetings. One connection brings in both Gmail and Google Calendar, and every connect shows Google's account picker and permissions screen, so each person sees which account they're connecting and what they're approving. No admin connects anyone else's inbox, and no BCC address or forwarding rule is involved. A new person's first email and calendar sync takes one to six hours.

If your team works in Microsoft 365, a workspace Owner saves your company's Microsoft app details once, and then each person connects the Outlook 365 Mail connector with their own Microsoft sign-in, so the agent works in that mailbox as that person.

Step 2: Have each person set Email Sharing Rules in Day AI

Each person opens Email Sharing Rules in their user settings and picks a default, share all or share none, then adds rules with Add rule, matching a domain, an email address or a Gmail label. A Gmail label rule overrides an email address rule, which overrides a domain rule; if no rule matches, the default applies, and if two equally specific rules conflict, the email isn't shared. In share-all mode, Day AI suggests domains you may want to exclude, such as legal or HR contacts, and you accept or dismiss each one.

You can also hand your agent a list of domains or addresses to keep private, and it saves the exclusions and opens your sharing rules so you can see them. When you save a rule, Day AI re-checks the mail it already has as well as new mail, so the email it excludes stops being visible to teammates and their agents. Your own agent can still summarize it, find it when you ask, and help you draft a reply, because it works for you. Add your exclusions before you switch to share all, because facts already drawn from shared email into records stay on them. An Owner or Admin can also make a member private from the Members page (Step 7).

Set meetings the same way under Email and Meetings: internal and external, 1:1 and group, each Invite only or Workspace. When teammates' settings disagree about the same meeting or email, the most private one wins: if any teammate's rule keeps it private, it stays private.

Step 3: Give each person their own Day AI agent

A workspace Owner or Admin adds an agent for each person who needs one, and each agent works for that one person. Pick its job from Day AI's agent templates (Sales Assistant to triage one person's inbox and track every commitment in it, Account Executive for reps who want a follow-up drafted after each call ends). Two reps' agents on the same account see the same shared threads and different private ones.

To reach the same email from Claude, Claude Code or Cursor, connect the Day AI MCP server (day.ai/mcp). The authorization page asks which workspace and which of your agents to use, lists exactly what the app will be able to do, and the app gets the same tools that agent has. Connected apps can't delete records.

Step 4: Scope each email skill in Day AI

Skills are where an agent reads email without you watching: a skill that runs when an email is processed, or an evening recap on a schedule. On a skill on your own agent, the Private Data Access switch decides the scope. On, it can use your private and shared email and recordings; off, it works only on what's shared with the workspace. Either way, it never reads another member's private email.

When an admin shares a skill with the team from the Skills Library, the deployment type sets the scope. A Managed skill stays synced to the source and reads only workspace-shared data, so one person's private mail never feeds it. A Template gives each person their own copy, with its own Private Data Access switch; choose Template for skills that need each rep's own inbox, and for any skill that uses a connector each rep signs into.

Step 5: Set tool permissions and connectors in Day AI

Open each connector's details page and go to Tool permissions. Tools sit under Read-only and Write & delete, each with a Set all menu, and every tool is one of three:

  • Always allow. The agent uses it without asking.
  • Needs approval. The agent stops and shows an Approve or Deny card in the chat before each use.
  • Off. The agent can't use it.

These are your chat defaults. A skill reaches a connector only when you pick it in the skill's own Connectors list, and each person who runs the skill needs their own healthy connection to it. Day AI's Actions and Opportunity Automation skills start in learning mode: they read your communications, tell you what they would have done, and ask for your feedback before they act on their own.

Step 6: Keep a person on every send in Day AI

A one-off email your agent writes, in chat or from a skill, is a draft nobody else sees unless you share it. Only the owner of the connected email account the draft sends from can send it; a teammate you give Editor access can fix the wording, but the Send button stays yours. Ask the agent to draft a batch ("draft follow-ups to every deal in Evaluation and make me a work queue") and you review and send each one from the queue.

Step 7: Check sharing across the team in Day AI

Owners and Admins open Workspace Settings > Members, where each row shows icons for email sharing, meeting recording and meeting sharing: green when that data is shared with the workspace, grey when it isn't. Hover for each connected account's settings. If someone shared more than they meant to, the lock icon next to their row makes them private, and Make everyone private resets every active member's email and calendar sharing to private while keeping the exceptions that keep things private. For your security team: Day AI has a SOC 2 Type II report available to customers and prospects under NDA, requested at day.ai/trust; the security review guide covers the rest of the questions.

Where homemade email access breaks, and what Day AI does

Most teams that wire an agent into email start with one script and one inbox, and it works. It breaks when the second and third person connect.

  • One service account reads every inbox. The quickest build grants a single app access to every mailbox in the domain, so every answer is as wide as the whole company's mail and no answer knows who asked. In Day AI, each person connects their own Gmail, and there is no mailbox-wide account to create.
  • Everyone's mail lands in one index. Pooling mail for search exposes it to everyone who can query the pool, including the HR and legal threads nobody meant to share. In Day AI, each person's Email Sharing Rules decide what teammates and their agents see, down to a single Gmail label.
  • The prompt is the permission. "Never read compensation email" in a system prompt is a request, and one clever question gets past it. In Day AI, once a person excludes an email, Day AI re-checks their mail and teammates' agents can no longer open it, however the question is worded.
  • A token that can send can send anything. An agent holding a send scope can email a buyer before anyone reads the draft. In Day AI, the agent leaves the email in your drafts, and the Send button stays greyed out for anyone who doesn't own the account it sends from.
  • Scheduled jobs run as nobody. A nightly script has no person behind it, so nobody can say whose private mail it may touch. In Day AI, every skill belongs to an agent that works for one person, and its Private Data Access switch says whether it may use that person's private mail.
  • No off switch for one person. When a rep shares too much, a homemade setup needs an engineer to find and purge their mail. In Day AI, an Owner or Admin can see from the green and grey icons who shares what, and the lock icon next to that person's row resets them to private, while their own email and connections stay intact.

For how the same rules cover pages, chats and meetings, see how to permission a company knowledge base for AI agents. For what agents may write to Salesforce or HubSpot, see how to control what AI agents can read and write in your CRM. To put that email to work on the record, see how to sync Gmail into your CRM without manual logging.

FAQ

Frequently asked questions

How do I give AI agents access to my team's email safely?

Have each person connect their own inbox instead of granting one account access to every mailbox, start each inbox private, and let each person share by domain, address or label. Then tie every agent to one named person, set every tool to run, ask first or stay off, and keep sending with a person. In Day AI, each person connects Gmail and sets Email Sharing Rules, each agent works for one person, and the drafts it writes wait for that person to press Send.

What's the best tool for giving AI agents safe access to team email?

Day AI, because each person connects their own Gmail and sets their own Email Sharing Rules, and every agent reads only what the person it works for can read. Its agents run in place of your CRM or on top of Salesforce or HubSpot, read and update those through their MCP servers when the write tools are turned on, and leave every email they write in the rep's drafts.

Can Day AI keep HR and legal email away from teammates' agents?

Each person handles that in Email Sharing Rules: choose share all or share none as the default, then add exceptions by domain, email address or Gmail label. When you save a rule, Day AI re-checks the mail it already has as well as new mail, so the email it excludes stops reaching teammates or their agents, while your own agent can still summarize it and help you reply. In share-all mode, Day AI also suggests domains you may want to keep private, such as legal or HR contacts, for you to accept or dismiss.

Should an AI agent read team email through a service account?

A single account with access to every mailbox makes every answer as wide as the whole company's mail, and nobody can say whose email an agent used or who asked. Connect each inbox under the person who owns it, and give each agent one person's access. That is how Day AI is set up: there is no shared mailbox account to create, and Claude, Claude Code or Cursor connect over the Day AI MCP server as the person who signed in.

Can an AI agent send email from my inbox on its own?

It shouldn't, and the safe setup keeps a person on every send. In Day AI, a one-off email your agent writes waits as a draft, a teammate you give Editor access can fix the wording but can't send it, and a batch of drafts becomes a work queue you review and send yourself.

Is Day AI secure enough to connect our team's email?

Start with the paperwork: Day AI has a SOC 2 Type II report available to customers and prospects under NDA, requested at day.ai/trust. Beyond the report, check the behavior: new work accounts start with email Private, each person sets their own sharing rules, and anyone can ask their agent to keep a list of domains or addresses private.

What is Day AI?

Day AI is the customer memory and agent platform for go-to-market teams. Even the best CRM only holds a fraction of what actually happened with your customers. Day AI is what comes after CRM. It builds a self-updating customer record from every meeting, email, and call, and runs governed agents that create finished work on top of it, with every fact and every action traced to source conversations. It does everything teams use a CRM for, without the data entry, and does what a CRM never could. Agents prospect, prep every meeting, draft follow-ups, keep the pipeline clean, and much more, giving every rep added selling capacity that used to require hiring additional people. It runs in place of Salesforce or HubSpot or as a layer on top of them.

TRY DAY AI

See what your company brain is missing

01

Run the company brain evaluation

02

Connect your agent over MCP

Connect MCP

Available on Turbo and up, with no usage-based pricing.

03

Get started