Every product your firm owns has something to tell you. Almost all of them say it the same way, by sending an email. That’s not integration. It’s correspondence, and it’s why a firm with nine products can feel like a firm with nine inboxes. A smaller number of tools work differently. They read the mailbox, write back into it, or sit inside the window somebody already has open. Those are the ones that take work off your day instead of adding to it. Here’s how to tell which is which before you buy, what you’re granting when you connect one, and which of the connections you already have are on a clock.
- A product can touch your mail in five ways. Most of what you own uses the shape that leaves all the work with you, which is why the bill and the morning are two different problems.
- The consent screen is the contract. It’s written in your provider’s words rather than the vendor’s, and it’s the only place the real answer appears.
- Whoever clicks connect owns the connection. On a Microsoft 365 tenant that’s any member of your staff, by default, without telling you.
- The tricks built on forwarding and BCC are the fragile ones. Microsoft now blocks the most common of them out of the box.
- Four separate deadlines are running against integrations small firms already have. Two have already passed.
Five ways a product can touch your mail
Sort your stack by how each product reaches the mailbox, rather than by what its feature page calls the capability. There are five shapes. They’re ordered here, roughly, by how much work each one takes off your desk.
It emails you. The product sends a message, and that’s the whole of it. Your payroll run is approved. An invoice was paid, a document was signed, somebody commented. This is the default state of almost every SaaS product on earth, and it takes permission from nobody. A stranger can write to you. That’s all this is.
It sends as you. Invoicing software, a scheduling page, a signing product and a newsletter tool all put your firm’s name on the envelope. Behind that sits a record in your DNS authorizing them to do it. Somebody made it once, and it’s rarely written down. It’s a genuine connection to your mail, outbound only, and it belongs to the domain rather than to any mailbox. Where email fits in a small firm’s stack works through what lives in DNS and why it matters when your invoices start landing in spam.
It takes a copy. The product gives you an address and asks you to send mail to it. HubSpot’s knowledge base describes both halves of this pattern. One half is a BCC address. The instruction is that “when you send an email from your mail client, add the BCC address to the BCC line of the email,” and “the email content will be automatically recorded on the contact’s record in HubSpot.” The other half is a forwarding address, for logging something after it arrived (HubSpot, checked September 7, 2026). Accounting products do the same with documents. Intuit’s help article describes adding receipts and bills to QuickBooks Online by emailing the image to a custom address ending in @assist.intuit.com (Intuit, checked September 7, 2026).
It reads and writes in the mailbox. The product signs in to Gmail or Microsoft 365 as you, through the provider’s own sign-in page, and works on the mail directly. This is the shape that files a thread, marks it, drafts a reply into your drafts folder or pulls an attachment out, while you carry nothing across. It’s also the one shape where somebody granted a third party standing access to client correspondence. That’s why the middle of this guide is about what that grant says.
It sits inside the mail window. A panel beside the message, in Gmail or in Outlook, showing you the client record or the invoice next to the thread it belongs to. Under the hood this is usually the fourth shape with a user interface bolted on. In practice it behaves differently. It removes the tab switch rather than the typing.
Plenty of products do two or three of these at once. What matters is which one does the work you’re paying for.
Does it save you a trip, or add one
One question settles most of it, and you can ask it while you’re still on the pricing page. When this product has something to tell you, or something to be told, does that happen where you already are? Or does it happen somewhere else, and then send you a message about it?
Take signing, because every firm has it and it goes both ways. A signing product in the first shape emails you when a client signs. You read the notification. You open the product, download the executed copy, and put it wherever executed copies go. That’s four steps, on a schedule other people set. The same product in the fourth or fifth shape puts the signed document where you keep documents, and the notification is redundant. The subscription price is identical. The cost is different.
Now count how many of your products sit in the first shape. In most small firms it’s nearly all of them, and the arithmetic is unkind. Every subscription you own is also a subscription to its notifications. They arrive in the one place where your actual work arrives. That’s the real reason a stack of reasonable purchases produces a morning nobody can get through, and it’s a cost that never appears on an invoice.
Two honest qualifications, because the test is easy to over-apply.
The first is that a notification-only product is often exactly right. Payroll should tell you the run went through, and it can do that from outside your mailbox. The nine jobs a firm covers don’t all run their daily traffic through email, and the stack overview is where those nine are set out. Judge a product on the traffic it actually generates. Something that writes to you twice a month is fine where it is.
The second is that a connection has a price. Every product in the fourth or fifth shape is a vendor holding a standing grant on client correspondence, which is more exposure than a vendor that only sends you mail. If the tool would save you two clicks a week, the notification version is the better buy. Volume is the threshold, rather than enthusiasm.
What you are agreeing to on the consent screen
When a product connects to Gmail or Microsoft 365, you land on a page from Google or Microsoft. It lists what the application is asking to reach. Read it. It’s the one description of the arrangement written by somebody other than the vendor. And two lines apart on that screen is the difference between a tool that can read your mail and a tool that can delete it.
Google publishes what each of its Gmail permissions means, and the wording is plain. The gmail.readonly scope is “View your email messages and settings.” The gmail.modify scope is “Read, compose, and send emails from your Gmail account.” Google adds that it “does not allow immediate, permanent deletion of threads and messages, bypassing the trash.” The broadest one, written as https://mail.google.com/, is “Read, compose, send, and permanently delete all your email from Gmail” (Gmail API scopes, checked September 7, 2026). Those first three are what Google calls restricted. A narrower one, gmail.send, is merely sensitive. It’s “Send email on your behalf,” and sending is all it does.
That classification is worth more than it looks, because Google attaches a real obligation to it. An app requesting restricted data that can reach that data from a server has to pass an independent assessment. Google’s rule is that “Every app that requests access to Google users’ restricted data and has the ability to access data from or through a third-party server must go through a security assessment from Google-empanelled security assessors.” And it has to be redone, since apps “must be reverified for compliance and complete a security assessment at least every 12 months” (Google restricted scope verification, checked September 7, 2026). A vendor asking for a restricted Gmail scope has either been through that or is about to lose the ability to ask. Treat it as a floor rather than a guarantee. It’s still more than most of your vendors have done.
Google also binds what any of them may do with what they see. Its Workspace developer policy prohibits “transferring, selling, or using user data for serving ads, including retargeting, personalized or interest-based advertising.” It also prohibits “transferring, selling, or using user data to create, train, or improve a machine learning or artificial intelligence model beyond that specific user’s personalized model for the appropriate use case.” Human eyes are fenced in too. A person at the vendor may look at your mail in narrow cases only. The first is where the vendor “has obtained and documented the user’s explicit consent or affirmative agreement to view specific messages, files, or other data” (Google Workspace API user data and developer policy, checked September 7, 2026). If you’re weighing an AI tool on a mailbox with client work in it, that policy is a floor under the question rather than an answer to it. The longer version is what model training actually means for your clients’ data.
Microsoft describes its permissions in the same style, and one distinction on that side deserves your full attention. Graph permissions come in two forms. The delegated Mail.Read is “Allows the app to read email in user mailboxes,” meaning the mailbox of the person signing in. The application form of the same permission is “Allows the app to read mail in all mailboxes without a signed-in user.” Application Mail.Send is “Allows the app to send mail as any user without a signed-in user” (Microsoft Graph permissions reference, checked September 7, 2026). From a risk point of view those are two different products, even when they’re the same product. So if a vendor asks for the application form, ask why. The answer has a countermeasure. Microsoft states that administrators can configure an application access policy “to limit app access to specific mailboxes and not to all the mailboxes in the organization, even if the app has been granted the Mail.Read or Mail.ReadWrite application permission” (limiting mailbox access, checked September 7, 2026).
Your password stays off the consent screen, by design. You type it into Google or Microsoft, who already have it, and the product receives a revocable token instead. Why an email tool never needs your password takes that apart properly.
Who owns the connection, and what it can reach
A grant belongs to whoever made it. In a firm of eight, that’s a question about people rather than about software.
Start with the default, because it surprises most owners. Microsoft’s own documentation says it plainly. “By default, all users are allowed to consent to applications for permissions that don’t require administrator consent” (Microsoft Entra user consent, checked September 7, 2026). The worked example on that same page is a mailbox. Consenting to an app that reads their own mail sits inside a staff member’s authority. Handing an app the run of the organization’s files sits outside it. So anybody on your team can connect a third-party product to their own work mailbox this afternoon, and nothing will tell you. That’s a deliberate trade, made in favor of people getting work done. It’s worth knowing before you assume your vendor list is your vendor list.
Google gives you a knob for the same problem. In the admin console, third-party apps can be set to Trusted, Limited or Blocked. A Limited app “can access only unrestricted Google services.” Blocked shuts an app out of all of them. Gmail and Drive go further, and let you restrict a predefined list of high-risk OAuth scopes, so those scopes stay beyond any app’s reach whoever trusts it (controlling third-party app access, checked September 7, 2026). Turning that on does something the moment you do it. Google warns that when you restrict a service, “any previously installed apps that you haven’t trusted stop working and tokens are revoked.” That’s both the effect you’re after and the reason to do it on a quiet Tuesday rather than in a busy week.
Then there’s the difference between one person connecting a product and the firm connecting it. Google separates these as an individual install and an admin install. An admin install puts the app in front of everyone in the organization, or a chosen group, under a warning worth quoting as written. “Only grant data access if you trust the app and it’s developer. Providing access to a malicious app can compromise your organization’s data” (installing Marketplace apps, checked September 7, 2026).
The practical consequence lands on your worst day rather than your best one. A product connected by one person under their own grant works because that person’s account works. When they leave and the account closes, the connection closes with it, and whatever it was quietly doing stops. That’s the good case. The other way round is harder. An old grant nobody remembers stays live and stays reachable, because tightening your policy reaches forward only. Microsoft is explicit about this. “Any updates to user consent settings only affect future consent operations for applications. Existing consent grants remain unchanged, and users continue to have access based on the permissions previously granted.”
So the connected apps list belongs on the same page as the subscription list, and the two are best walked at the same time. Cutting overlapping subscriptions is where that inventory gets built, including the free tools that never appear on a card statement. And if your firm handles clients’ financial information, every one of these grants is a service provider you’re required to select, contract with and reassess. The rule itself is what the stack overview works through. The questions to put to any of them are collected in what to ask before you connect a tool to client data.
Why forwarding and BCC keep quietly breaking
The copy-taking shape is the oldest way to make a product talk to your inbox. It’s also the one most likely to fail quietly.
Microsoft has been closing it for years. Automatic forwarding to external recipients is governed by your outbound spam filter policy, where the default value is “Automatic - System-controlled.” Microsoft’s documentation explains what that value quietly became. “In 2021, the value changed to Off - Forwarding is disabled for new organizations and for existing organizations that weren’t actively using the Automatic - System-controlled value.” Because it now means different things in different tenants, Microsoft recommends setting On or Off explicitly instead. When it blocks, it blocks visibly, returning the message with “5.7.520 Access denied, Your organization does not allow external forwarding” (controlling external email forwarding, checked September 7, 2026). Note which forwarding this covers. “Disabling automatic forwarding disables any Inbox rules (users) or mailbox forwarding (admins) that redirect messages to external addresses,” while forwarding between internal users is untouched.
Read that as a rule about what you buy. Any product whose onboarding asks you to create a forwarding rule to an address at their domain is asking for something your platform is configured to prevent, for good reasons. Sometimes the right answer is to allow it deliberately, for that one destination. Opening external forwarding generally, so that one product works, is the answer to avoid.
BCC-based logging has a different failure, and a quieter one. It depends on a person remembering, every time, forever. What it captures is what somebody thought to copy. The record of the relationship is a larger thing. The client’s reply lands there only if somebody forwards that too. There are size limits, and HubSpot’s is 40 MB across body, headers and attachments together. And the copy that arrives is a copy, so anything decided in the thread afterward lives in your mailbox alone.
The last problem with both is one nobody raises on the sales call. Forwarding client mail to a third party is a transfer of client information to a vendor, exactly as much as an API grant is. It happens without a consent screen, without a scope list and without an entry in anybody’s admin console. It’s the least visible integration you can build, and the one most likely to be built by somebody who didn’t think of it as one.
Deadlines running against the tools you already own
Four separate clocks are running on integrations that small firms have already installed and forgotten. Two of them have already gone off.
Passwords stopped working as a way in. Microsoft states that Basic authentication “is now disabled in all tenants” and that nobody, including Microsoft support, can re-enable it. It was removed “for Exchange ActiveSync (EAS), POP, IMAP, Remote PowerShell (RPS), Exchange Web Services (EWS), Offline Address Book (OAB), Autodiscover, Outlook for Windows, and Outlook for Mac” (deprecation of Basic authentication, checked September 7, 2026). Google closed the same door. “Starting March 14, 2025, you and your users must use OAuth with third-party apps to access Gmail, Google Calendar, and Google Contacts.” That covers CalDAV, CardDAV, IMAP, SMTP and POP, with an exception for app passwords (transition from less secure apps to OAuth, checked September 7, 2026). If some device or script in your office still holds a mailbox username and password, it’s either already dead or living on an exception.
Sending with a password is next. Microsoft’s guidance is that “although SMTP AUTH is currently available, Microsoft has announced plans to retire Basic authentication for SMTP AUTH in Exchange Online.” The timeline has been revised, so the current milestones live in the announcement rather than in this article. What it means for you holds whatever the date turns out to be. Anything in your office that sends mail by logging in to a mailbox with a username and password is on a clock. That’s the usual arrangement for a copier that scans to email, an old line-of-business application or a website contact form. The fix is the vendor’s to ship rather than yours to configure.
EWS goes away in two steps. Exchange Web Services is the older interface a great many third-party products used to reach Exchange mailboxes. Microsoft’s timeline is now specific. “October 2026: EWS starts to be disabled globally for all organizations.” Then “April 2027: EWS is fully disabled” (deprecation of EWS, checked September 7, 2026). Backup tools, archiving products, signature managers, CRMs and room-booking systems are the usual holders. This is a question for your vendors, in writing. The useful form of it is whether their product has moved to Microsoft Graph, rather than whether they’re aware of the change.
Old Outlook plug-ins stop at the new Outlook. If a product installed a panel into desktop Outlook years ago, check what happens when your people move to the new client. Microsoft is direct. “Because COM add-ins aren’t supported in new Outlook for Windows, their Office web add-in counterparts are installed instead.” And the substitution “is only supported for some COM add-ins” (installing web add-in counterparts, checked September 7, 2026). Where the product lacks a web version, the panel is gone.
The common thread is that the announcement comes from somewhere other than the product that breaks. The notice goes to the vendor. Whether it reaches you depends on whether they’re still building.
What to ask before you connect anything
Seven questions, in the order they come up. Each one is a support email long.
- Which of the five shapes is this? If the answer is that it emails you, you’re done, and the only cost is more mail.
- What’s on the consent screen? Read the scopes rather than the sales page. Read-only and read-write are different products.
- Does it want my mailbox or everyone’s? A delegated grant is one person’s mail. An application grant reaches all of them, until somebody limits it.
- Who’s clicking connect? A grant made by one person dies with that person’s account, and outlives your policy changes. Decide deliberately whether this is an individual install or a firm one.
- Does it ask for a forwarding rule or a password? Both are the fragile shapes. Forwarding is blocked by default on Microsoft 365, and password-based access to the mailbox is finished on both platforms.
- What’s the vendor allowed to do with what it sees? For a Gmail connection, Google’s developer policy sets a floor on advertising, on transferring your data and on training models with it. Get the vendor’s own answer in writing anyway.
- When it goes, what stays? A tool that wrote into the mailbox leaves its work behind when you cancel. A tool that pulled the mail into itself takes the record with it, subject to whatever export clock it runs.
The last one is the one people skip. It’s also the reason a connected tool is easier to leave than a tool that became your filing system. That whole subject, including which products are safe to stop paying for, belongs to what to keep.
What this changes about the next purchase
Two products can cover the same job, cost the same, and produce completely different weeks. So put the question in the comparison ahead of price. Where does the work land?
Some jobs run their daily traffic through email. In most firms that means the client record, scheduling, signing and anything to do with documents arriving from clients. For those, prefer the product that reads and writes where the work already is. You’re buying back a step you’d otherwise take several times a day.
For everything else, buy the plain product and let it email you. Payroll, the books, credentials. These have their own surfaces, their traffic is low, and the integration would be a connection to maintain for no return.
And count the connections separately from the seats. Each connected product is a consent grant to review, a vendor to assess, something to revoke on somebody’s last day, and one more thing a platform deadline can break. That overhead attaches to the product rather than to the headcount. It’s the same reason the stack overview counts vendors alongside dollars.
How Point connects, and what it writes back
In the vocabulary of this guide, Point is the fourth shape. Point is an AI email client. Your firm already licenses a mailbox on Gmail or Microsoft 365, and Point signs in there and works on the mail itself.
The connection is the ordinary one. You choose Gmail or Microsoft 365. Google’s or Microsoft’s own sign-in page takes it from there, and your password goes to the company that already has it rather than to Point. Back comes a consent screen listing what’s being asked for, in your provider’s words. That same list, with the reasoning attached, is what Point can see and what it cannot, for reading before you’re standing in front of it. There’s no forwarding rule to create, no new address, no export and no import, and the day you connect is an afternoon rather than a project. If your Workspace or Microsoft 365 is administered by somebody other than you, expect the grant to be theirs to approve. By the section above, that’s the arrangement you want.
The judgment gets written back into the mailbox, and that’s what makes Point the fourth shape. Connect Gmail and three labels appear there, Now, Later and Other. Every triaged message carries the one it earned. So you can filter your real inbox down to what needs you from Gmail itself, with Point shut. Connect Outlook and those same three arrive as categories. Put a thread away in Point, and the mailbox agrees a second later, archived rather than deleted, in the place your archived mail already lives. Your provider still holds the mail, still delivers it, still charges you for the seat. Your retention tier and your holds stay as they are. That’s the arrangement where email fits in the stack argues you should want from anything you add at this layer.
The rest is what the connection buys, and all of it rests on Point having the mail rather than a copy of some of it. What each message is worth, and what being late on it costs, is weighed before you open the list. So the thing that matters sits at the top rather than four screens down, and how that ranking works is a subject of its own. A thread arrives with a plain summary on it, short enough to stand in for reading the thread. A commitment buried three paragraphs into a message comes out as a task with a date, still hinged to where it came from. Tell Point once to watch for a signed engagement letter, and the arrival comes to you. Search runs on what you meant rather than on the exact words, which is what you need when the sentence you half remember was written by somebody else. And the meeting arithmetic is done for you. That includes a page clients can book from, against calendars already reconciled. It’s the one place Point lands on a line that may already be on your bill, and what a booking link should do marks out where a separate link is still the better instrument.
Weigh the controls where you put the rest of your vendor answers. What Point does on its own is set per kind of work. Filing, drafting, scheduling and chasing each hold their own level, and each level has three settings. Point suggests only. Point prepares and waits for you. Or Point handles it. New accounts sit in the middle position on every one of them, so Point prepares the work and waits for your go. At the top position Point acts without checking, and the dial is the page to read before you move anything. Work is recorded to a log with times against it, and most entries can be taken back from there. One limit holds for every vendor in this category. A message already on the recipient’s server is beyond anyone’s reach. Home mail and work mail keep to their own lanes. Another business you run stays clear of the first one’s view, and seats come and go with the people. Pricing is private beta and charged per seat.
Say the limits once. Point holds no queues, no assignment between staff and no reporting on how fast the firm answered. A practice whose inbound really is a support line wants a product built for that. Compliance stays with the platform, so retention, holds and discovery stay where the platform keeps them. Your other subscriptions carry on writing to you. That’s true of everything at this layer. What changes is where those messages sit relative to the client who’s waiting. Everything Point does is the full inventory, and the trade-specific version opens closer to your own week.
Common questions
How do I tell if a tool actually integrates with Gmail or Outlook?
Look for the sign-in. A real connection sends you to Google’s or Microsoft’s own page, and shows a consent screen listing what the app can reach. If instead you’re asked to create a forwarding rule, add a BCC address or type a mailbox password into the vendor’s form, what you have is a product receiving copies of things. That’s a weaker arrangement, with more ways to fail.
Can employees connect apps to their work email without telling me?
On Microsoft 365, yes, by default. Microsoft’s documentation states that all users are allowed to consent to applications for permissions that don’t require administrator consent, and gives access to their own mailbox as the example. Google gives administrators a similar default to change, with third-party apps settable to Trusted, Limited or Blocked. Either way, read the list of connected apps in your admin console before you assume you know what your firm has authorized.
What is the difference between delegated and application permissions?
Delegated means the app acts as the person who signed in, and reaches that person’s mailbox. Application means the app acts on its own. Microsoft describes application Mail.Read as reading mail in all mailboxes without a signed-in user, and application Mail.Send as sending as any user. For a small firm, delegated is almost always what you want, and a vendor asking for application permissions should have a specific reason. Microsoft lets administrators scope an application grant down to named mailboxes.
Is it safe to give an app access to my clients’ email?
It’s a decision rather than a yes or no, and it’s the same decision you make about any vendor holding client information. You have made it before. For Gmail, Google puts a floor under it. Apps reaching restricted data from a server must pass an independent security assessment and repeat it at least every 12 months, and Google’s developer policy bars using that data for advertising or for training a general model. Get the vendor’s own answers in writing on retention, deletion and who at their company can read what.
Why did my email forwarding to another app stop working?
Most likely your Microsoft 365 tenant blocks automatic external forwarding, which is the default behavior for organizations that were not already using it. The giveaway is a bounce reading 5.7.520 Access denied, Your organization does not allow external forwarding. An administrator can allow it, ideally for that one destination rather than in general. It’s also worth asking whether a product that depends on forwarding is the right product.
Will my old Outlook plug-in keep working?
Some will. Microsoft states that COM add-ins are not supported in the new Outlook for Windows and that web add-in counterparts are installed instead, but only for some of them. Separately, Exchange Web Services starts being disabled globally in October 2026 and is fully disabled in April 2027, which affects any third-party product still reaching Exchange that way. Both are questions for the vendor, and the useful version is whether their product has moved to Microsoft Graph.
Does connecting a tool to my inbox mean my mail is stored somewhere else?
That depends on the tool, and it’s the right thing to ask. Some products read the mailbox and write back into it, leaving your provider as the place the mail lives. Others copy the mail into their own system. That makes them a second store of client correspondence, with their own retention, their own export clock and their own breach exposure. The answer changes what happens on the day you cancel, so ask before you connect rather than after.
The short version
- Five shapes. It emails you, it sends as you, it takes a copy, it reads and writes in the mailbox, or it sits inside the mail window. Most of your stack is the first one.
- The test is whether the work happens where you already are. Every product you own is also a subscription to its notifications, and that cost never reaches an invoice.
- Read the consent screen rather than the feature page. Google publishes what each Gmail permission means, and read-only, read-write and permanent deletion are three different agreements.
- Delegated access reaches one mailbox; application access reaches all of them. Microsoft lets an administrator scope the second one down to named mailboxes.
- By default, anybody on your team can connect an app to their own Microsoft 365 mailbox. Tightening the setting later reaches forward only. Grants already made stay as they are.
- Forwarding and BCC are the fragile shapes. Microsoft blocks automatic external forwarding by default and returns a 5.7.520 bounce, and BCC logging only ever captures what somebody remembered.
- Four clocks are running. Mailbox passwords are finished on both platforms. Sending with a password is being retired. EWS starts turning off in October 2026 and is gone in April 2027. COM add-ins stop at the new Outlook.
- Buy the connected version for the jobs whose traffic runs through email, and the plain version for everything else. Count connections separately from seats.
Three neighbors carry the rest of this. The nine jobs a small firm covers in software is the frame everything here sorts into, the email layer is what all of these tools are connecting to, and cutting overlapping subscriptions is how you build the list of what you already have.