Approval is two different moments sharing one word. One is routine: on a setting held at review, the work is finished and waiting for your yes. The other happens once, when a kind of action Point has not taken for you before waits for a yes before it can run on its own at all.
- The routine yes decides one piece of finished work. The first of a kind decides a category, and that is the one worth slowing down for.
- A permission does not spread. A setting you raised covers the kind of work you raised it for, and something genuinely new does not arrive already covered by it.
- There are three answers rather than two: agree, decline, or change it and then agree. Only the third one says what right would have looked like.
- A yes you did not read is worse than no gate at all, because it leaves behind a record saying you agreed.
Two things called approval
The routine one sits in the middle of the dial. Point has done the work, the result is holding, and your yes is what releases it. The unit is a single piece of finished work: this reply, this meeting time, this task. It happens many times a day across the settings you have not raised, and it ought to be quick, because the whole value of that position is that the thinking is already done by the time the decision reaches you.
The rare one is not about a piece of work at all. It is about a kind of work. The first time Point would take an action of a sort it has not taken for you before, that action waits, whatever else is running smoothly around it. Your answer there is not really about the message in front of you. It is about whether that sort of thing is open from now on.
From where you sit the two look identical. Both are something held, waiting on a click. What differs is what the click buys. Agreeing to a reply commits one paragraph to one client, and you will know inside the day whether it was right. Agreeing to a new kind of action commits you to a category, and the evidence about that arrives slowly, in a record, weeks later.
So they deserve different speeds, and the usual way to get this wrong is to give them the same one. Someone working through a queue at a steady pace who meets the unfamiliar one at that same pace has just made the largest decision of the morning at the speed of the smallest.
What a routine yes releases
What you are shown is the outcome rather than the reasoning. The reply as it would go out, the time as it would be booked, the task as it would be written down. That is the reason a decision can honestly be made in a few seconds: reading a finished thing is a different act from auditing a process, and you are doing the first.
There are three answers, and the third is the one that gets forgotten. Agree, and it goes. Decline, and it does not. Or change it first and then agree, which stops the wrong version and puts the right one in its place in a single movement. Declining says no. Changing says what yes would have looked like, and since you had the thing open anyway, that correction is close to the cheapest instruction you will ever give: a preference told to Point once, in a sentence, holds wherever it acts for you next.
There is a fourth thing that can happen, which is nothing, and silence is not agreement. A held action stays held, and work you never got to is work that did not happen. That is the honest cost of a gate and it is worth naming, because it is the part people meet in week three rather than week one: everything waiting on you has moved off Point’s list and onto yours.
Which gives the one reading of your own queue that matters. If you are clearing it without really reading it, the gate has already stopped working, and the answer is not more diligence. It is to raise the setting for that kind of work, so the work moves to a surface built for things nobody is watching in advance. An unread queue is the worst of the arrangements available: you carry the obligation, you get none of the protection, and you have left behind a record saying you agreed to each one. Going through the activity log behind every action afterwards is a smaller job, honestly done. Clearing a queue you are not reading is a larger job, pretended at.
The first time it does something new
New means a new kind of action, not a new person and not a new message. A gate that fired on every unfamiliar sender would fire twenty times a day, and a question asked twenty times a day is not a control. It is a thing you learn to dismiss without reading it, which is how consent screens everywhere became a formality.
So the unit here is the same one the autonomy dial uses, which is deliberate rather than merely tidy. One vocabulary across the whole control surface, a kind of work, means the thing you set and the thing you are asked about are the same object. You never have to hold two models in your head to know what you just agreed to.
And it matters most precisely where you have stopped paying attention. Say filing has been running on its own for a month, which is where filing usually ends up. What you authorised was filing. The gate is what keeps that permission from quietly widening to take in something adjacent that turns up later and merely resembles it. Your yes is bounded by the category you gave it for, and anything outside that category comes back to you rather than inheriting the trust you extended to its neighbour.
Standing requests are the case to watch here. Ask Point to keep an eye out for something and you have set up a thing that acts later, on its own timing, long after the conversation that created it has left your mind. That is the one permission it is genuinely easy to forget you granted, which is why every watch you have running stays visible and can be stopped.
What a yes actually grants
The two yeses grant opposite amounts, and knowing which one is in front of you is most of the skill.
A routine yes grants exactly itself. Approving this reply sends this reply. It sets no precedent and it does not accumulate: forty approved replies still leave replies on review, because the number of times you have said yes is not a setting.
That surprises people, and the surprise deserves to be taken seriously, because the intuition behind it is a sound one. You would expect an assistant to notice you have agreed to the last forty and stop bothering you. A person would. But a person you had waved off that way is also a person whose licence you could not afterwards produce, and the reason to have a dial at all is that how far Point goes should be something you set and can read back, not something that drifted upward because you were agreeable for a month.
The first of a kind grants the other way. It opens a category, and from then on that category runs at whatever setting it already sits at, which on a new account is review. So it hands nothing over by itself. It removes a block, and the setting behind the block is what decides what happens next. Anyone who reads it as handing something over has skipped a step; anyone who reads it as meaningless has skipped the other one.
Both kinds leave a row. The routine ones are receipts, and you will mostly never look at them again. The first of a kind is the row worth being able to find a year later, because it is the one that answers why a whole class of work has been happening without you since March.
What a yes does not cover
The connection itself. The largest permission you have given was given before any of this, when you authorised a tool onto your mailbox. Every action gate in the product sits inside that grant rather than reopening it, and where the keys to it are held is the credentials that connect your mailbox.
Anything already done. A gate runs ahead of an action and has nothing to say behind it. Once something has happened the instrument is a different one, undoing what Point did, which reaches Point’s own moves and stops where a message has left for a server belonging to somebody else.
Whether the judgment underneath was sound. A yes authorises, it does not verify. What you are agreeing to is an output, so a fast approval is worth exactly as much as that output being right on its face. Where you would have had to check a figure or a date to know, the few seconds did not check it, and the approval carries the error forward under your name instead of catching it.
Which business it belongs to. An approval is given inside one of the businesses you operate and does not reach across into another. That line is keeping one business isolated from another.
What arrives in the first place. Mail from a sender Point does not recognise is held at the door rather than read into anything, so a stranger cannot put an instruction in front of your assistant. That guards against somebody else’s initiative rather than your own tool’s, which makes it a different safeguard from this one, and it sits with the rest on the benefits page.
None of the above is an argument that you ought to hand anything over. This page describes a switch, for a reader who came looking for the switch. The case for looking at all is learning to trust AI with client work.
Common questions
Does Point ask before it does something?
For a kind of work it has not done for you before, yes, that waits. After that it stops being a habit and becomes a setting, held separately for each kind of work: at review you are asked every time, and at the top of that setting you are not asked at all. So the accurate answer is that Point asks where you have not answered yet, and stops asking where you have. Which of those you are in is a thing you can look up rather than a thing about the product.
If I never get round to approving something, what happens to it?
It waits, and it stays waiting. Nothing completes because you ran out of Tuesday. The catch is that waiting is not free, since a held action is an unfinished job that has moved onto your list, and a queue that is permanently full is not a backlog to attack harder. It is a setting sitting lower than the work actually needs, and moving it is the fix.
Does approving something teach Point it can do it without me next time?
No, and this is the most common misreading of the whole arrangement. A routine yes releases one finished piece of work and grants nothing past it, however many times you give it. What changes how often you are asked is the setting for that kind of work, and it changes when you move it and not before. That is a feature rather than an oversight: a permission that crept upward because you were in a good mood in April would be one you could never account for later.
Can I turn something down without explaining why?
Yes, and a plain refusal is a complete answer. The cheaper move is usually to change it and then agree, because you already had it open and were already reading it. A refusal stops one thing. A correction made at that moment is an instruction that holds afterwards, which means the same thirty seconds either buys you one avoided mistake or buys you the avoided mistake and its whole class.
How do I know later what I approved?
Both kinds of yes leave a row, and it is the first of a kind you will actually want to find, because that is the row explaining why a category has been running without you ever since. The uncomfortable half is that the record cannot tell a considered yes from an unread one. Both look the same on the page, which is the practical reason not to give the second sort in a profession where you may one day be asked to account for what your software did.
The short version
Two yeses, and they are not the same size. The routine one releases one piece of finished work and grants nothing beyond it, so it should be fast, and the day you find yourself giving it without reading is the day to raise that setting rather than to try harder. The first of a kind releases a category, so it should be slow, and it is the reason a permission you gave for filing never quietly becomes a permission for something else. Agree, decline, or change it and then agree, and hold on to the fact that not answering is not an answer: the thing just waits, on you. Point is the product the gate sits inside.