Point holds a boundary between the businesses you operate. Each keeps its own mail, its own people and its own record, and nothing from one is visible inside another. The line follows a business rather than a client, and that difference decides whether this is the control you came looking for.
- Two different requests arrive in the same words, and only one of them is about the boundary. The other is about what you would rather not look at this morning.
- What the line stops is a crossing, not a glance. Both businesses can be in front of you at once and still be apart.
- The mistake this actually prevents is an identity slip: the reply that went out under the wrong firm’s name because two windows were open.
- Every other control in this collection is set on one side of the line, so a second business is a second set of answers rather than an inheritance.
Two requests inside one question
Someone who says they need two businesses kept separate usually means one of two things, and the two have different answers.
The first is about attention. You do the accounts on a Tuesday and you would rather the property company’s suppliers were not in the same list while you do it. Nothing is at risk here. You simply do not want to be looking at it yet.
The second is about crossing. Nothing from one business should reach the other: not its mail, not what an assistant learned there, not the people who work in it. This one is not a preference about your morning. It is a line that either holds or does not.
Point answers them separately, and it is worth knowing which one you are asking, because the expensive way to solve an attention problem is to build a boundary you did not need. If the real request is that work and home stop landing in the same pile, that is sorted inside a single business by placing each message in the part of your life it belongs to, and it does not require a second business at all. Set up a second one for that job and you have bought yourself two of every control on this page to solve a problem that a filter already solved.
What the line is drawn around
The unit is a business you operate. Something with mail arriving in its name, people who work in it, obligations that belong to it, and a name at the foot of a reply. The practice and the property company. The consultancy you own and the second firm where you took on a role and now help run the place. Two things that would each have to exist if the other closed tomorrow.
A client is not that unit, and this is the part worth being exact about rather than comfortable about. Point does not put a wall between one of your clients and another. There is no arrangement in which each client’s mail is sealed off inside your own firm, and anyone telling you otherwise about any tool is describing something else, usually storage, and calling it isolation.
That is the right unit rather than a shortfall, for a reason you already know from your own week. A firm’s work does not divide cleanly by client. One thread names two of them. A question about a deadline is about the practice, not about whoever asked it. The thing that has a mailbox, a team and a letterhead is a business, so a business is what a boundary can honestly be drawn around. Draw it around a client instead and you get a line that half your correspondence sits across.
What you do have inside one business is narrower and more useful than a wall: nobody outside that business’s own people is in it, and what your assistant did there is recorded there. The separate question of what you must tell clients about a tool that reads their correspondence is a professional one rather than a setting, and it belongs to what confidentiality means when AI reads client mail.
Both in front of you, and still apart
The intuitive version of separation is hiding, and hiding is the weaker half of it.
Consider how this is done without a boundary, which is two windows. One business per browser tab, or one per app, and you move between them all day. It hides very well. It also produces the specific failure people arrive here with: the thing you missed was in the window you were not looking at, and you found out on Thursday.
So Point shows every business you belong to in one feed, and makes each card say which business it belongs to. That single piece of labelling is what makes one surface safe to use, because the risk of a merged view was never seeing the other business. It was being briefly unsure which one you were reading. When you do want the narrower view, one switch lists the businesses you belong to and one click takes the whole surface down to a single one. Filter to the other and the thread is simply not there, which is the same isolation the two windows gave you, held for as long as you want it and no longer.
Then there is the half that matters more, because it runs outward. Reply from the combined feed and the reply goes out inside the business the thread belongs to. You do not pick an identity, which means you cannot pick the wrong one. That is the real cross-business accident and it has always been a human one, made at speed by somebody with two addresses open who was thinking about the sentence rather than the sender. Taking the choice away is what removes it.
The same holds when Point is working without you. Setting how much your inbox does on its own decides how far it goes on a kind of work, and at the top of a setting it goes ahead unasked. That setting says how far. It never says where. Work done on its own is still done inside the business whose thread it belongs to.
Two businesses means two of everything here
Each control in this collection is set on one side of the line, and the consequence is worth stating plainly because people meet it in week three and read it as a fault.
How far Point goes on a kind of work is answered within a business. A yes you gave belongs to the business you gave it in, which is the boundary in approving anything new before it acts. The record of what happened is kept per business, so the activity log behind every action is two records rather than one merged feed. Even the connection itself sits on one side, since the mailbox a business receives on is that business’s, and where those keys live is the credentials that connect your mailbox.
So filing running on its own in the practice is not filing running on its own in the second business. Nothing was inherited, and nothing should have been, because a setting that spread across the line would itself be a thing crossing it. A permission that leaked from your busiest business into the one you look at on Fridays would be the exact failure this whole arrangement exists to prevent.
What it does mean is that the second business needs the same attention the first one got, and usually does not receive it. The pattern is easy to describe and easy to fall into. You watch the main business closely, raise settings there as you get comfortable, and let the smaller one run on whatever it started with, which is review. That is a safe place for it to sit, so nothing goes wrong, but nothing is handed over either, and a year later you are still clearing a queue in the business you barely think about. The other order is worse and rarer: raising a setting in the business whose record you never open. Raise where you are watching, and watch where you have raised.
Where the separation stops
It does not divide a single mailbox. If both businesses have been running through one address for years, that address is one business as far as any software can tell. The boundary follows the mail, not your sense of which hat you were wearing. Two businesses sharing an address is a bookkeeping arrangement you already live with, and separating them is a job that starts with a second mailbox rather than with a setting.
It does not keep anything from you. You belong to both, so you can reach both, and that is not a leak in the design. The line governs what crosses between the businesses and who else stands on each side. It was never built to hide your own company from you.
It does not survive a person you put on both sides. Invite the same colleague into two businesses and they are in two businesses. That is the answer to the question rather than a hole in it, and it means the guest list is the control here. Deciding who is in a business is the same act as deciding what they can see of it.
It is not a claim about where data is held. Separation inside a product and separation inside a supplier’s systems are two different sentences, and only one of them is answered by anything on your screen. Storage, retention, who at a vendor could reach a record and what happens to it when you leave are things to put to a company in as many words, and the list to put is questions to ask any AI tool about your data.
None of this is an argument for handing anything over. This page describes a boundary for a reader who wants to know its shape. If the reason two businesses are on your mind is that trusting one of them to a tool still feels early, running more than one business through it takes the same ground from the other end, and the benefits page is the inventory of what there is to hand over in the first place.
Common questions
Can I keep each client’s email in its own separate space?
No, and it is better to know that now than to discover it later. The line Point holds runs between the businesses you operate, and a client is not one of those: a client is somebody your business corresponds with, sitting inside it rather than beside it. What you get instead is that the business itself is closed, to other businesses you run and to anyone you have not put in it. If the question underneath is what you are obliged to tell clients about a tool with access to their correspondence, that is a professional question with a professional answer, and it lives in AI and client data for accountants.
If both businesses show up in one feed, in what sense are they separate?
In the sense that matters, which is what crosses rather than what you can see. Every card names the business it came from, one switch narrows the whole surface to a single business, and a reply leaves inside the business its thread belongs to. Keeping them in two windows would hide more and protect less, because hiding is not a boundary. It is just a smaller view, and the thing you missed was usually in the half you had closed.
Could a reply go out from the wrong business?
The choice is not yours to make, which is what takes the mistake away. The thread already belongs to a business, and the reply is sent inside it without you selecting an account. That holds at every position of the dial for replies. Where the setting is at review, you are releasing words that were already addressed to the right side of the line. Where you have raised it and Point acts without asking, the acting still happens inside the thread’s business. The setting changes how far, never where.
Do the people in one business see the other one?
Only if you put them in both. Membership belongs to a business, so someone invited into one is in one, and someone in two is in two by a decision you made rather than by drift. It is worth treating the invite list of each business as part of this control rather than as administration, because it is the single place where the boundary is decided by a person instead of by the software.
Do I have to set the controls up twice?
Yes, and it is the boundary being real rather than a step somebody forgot to build. Settings that copied themselves across would be information moving between two businesses that are supposed to be closed to each other. The practical version is that a second business begins where the first one began, on review, and reaches wherever you take it, which is the same fortnight of watching and raising you did the first time. Assuming it arrived already configured like the other one is how a queue quietly builds in the business you think about least.
The short version
The boundary runs between businesses you operate, and it holds on crossings rather than on visibility. Both can be in one feed, each card saying whose it is, with a switch that narrows to one when you want the narrower view, and a reply that leaves inside the business its thread came from without you choosing. What that line cannot do is sit between two of your clients, divide a single shared address, or hide either company from the person who runs both. Everything else here is set on one side of it, which is why a second business is a second set of decisions and never an inherited one. Point is where the switch lives.