Approvals and permissions

What Haruno asks your approval for, how to answer a card, and what you can change in the normal view, the Advanced view and scheduled tasks.

How approvals work

In a chat, Haruno checks each step before it takes it. Reading and routine work go ahead; a step that sends, publishes, changes shared data or can't be undone may stop for your approval. The month-end close never asks: you run every step of it yourself with the app's buttons.

The rule is the maker-checker split you already apply to payments: Haruno prepares, and you release anything that leaves your hands. Permission to draft an email to a company is not permission to send it, and permission to prepare an invoice is not permission to record it in a company's books.

What happens to each kind of step

In the normal view, which a new install uses, each kind of step is handled as below. In the Advanced view, the permission mode you choose changes some of these.

StepWhat happens
Reading or searching files in the folder Haruno works in or in the books shown beside it, reading documents, starting a helper taskGoes ahead.
Creating or changing a file in that folderGoes ahead. See the warning below.
Searching the webUsually goes ahead; there is no switch for it. A card, when one asks, notes “Your search text leaves your Mac.”
Running a command, reading a page on a website, other stepsThe automatic safety check lets the step go ahead, asks you, or blocks it.
A connector action a Require confirmation switch covers, such as sending an emailAlways asks.
Mirroring, syncing or uploading to a cloud storage folderAlways asks. There is no switch for it.
Connecting to a site outside the secure sandbox's listA separate prompt: Let Haruno open this website?
An approval card does not guard your books
Haruno is shown your books beside the folder it works in, read-only, so it cannot change them and no card is needed. The exception is a company's mapping, which it may edit in place when you ask; it reports each line it changed. Every other change to the books is made with the app's own controls, such as Close month…, Reopen… and Approve mapping. With Sandboxed Engine turned off, only Haruno's instructions keep it to this.

The close has its own checks too: a changed or deleted copy of an imported file raises an evidence_integrity finding, and a close refuses exports that would change a locked month. Neither catches every possible change. To be asked before each change to a file, use the Advanced view's Ask each time or Ask mode (Approvals in the Advanced view).

What never raises a card

You do these yourself with the app's own controls, so no card is involved: adding companies and exports, syncing a QuickBooks company, drafting and approving the mapping and recording answers, closing and reopening a month, and opening reports and exporting them. The Ask Haruno buttons on a company page only place a question in the chat box; nothing is sent until you press Send.

The approval card

When Haruno needs your approval, the reply stops at a card in the chat, and the elapsed-time line at the bottom of the chat stops and turns grey until you answer. In the normal view the card says in plain words what Haruno wants to do and what it would act on, such as the file, website, recipient or company, and Show details opens the full request. The Haruno says row is Haruno's own description, not the app's, so check it against the other rows.

ButtonWhat it does
Allow onceRuns this one step. The next step of the same kind is judged again, and may ask again.
DenyThe step does not run, and Haruno is told you refused it. Tell it in the chat what you would rather it did.
Allow for this sessionAdvanced view only: also allows every later step of the same kind in this chat.

Pressing Return never answers a card: click a button, or press Space on a focused one. When the safety check or a standing rule such as a Require confirmation switch raised the card, the normal view adds Haruno pauses before anything that sends, publishes, changes shared data, or can't be undone.

What the headline means

HeadlineWhat Haruno wants to do
Haruno wants to run something on your Mac.Run a command, inside the secure sandbox in the normal view. Haruno says describes it.
Haruno wants to change a file.Edit a file. Currently and Will become show the text before and after.
Haruno wants to save a file.Write a file (What Haruno will write), replacing any file with the same name.
Haruno wants to open a file. / Haruno wants to look through your files.Read a file, or search files (Looking for). “Haruno will only read it.”
Haruno wants to read a page on [site].Read one web page (Website).
Haruno wants to search the web.Search for the words under Looking for.
Haruno wants to start a background task.Start a helper task, shown as Working on a subtask.
Haruno wants to update its plan.Change the step-by-step list it keeps for the reply.
Haruno wants to use [connector].Action names the act, such as Gmail send; up to four more rows show the recipient, channel, subject or message.
Haruno wants to add an event to your calendar.Create a Google Calendar event. “Everyone listed will be emailed an invitation.” means Google emails each guest.
Haruno finished planning and is ready to start.On a notification: a plan is ready for your review.
Haruno needs your approval for a technical step.The card says “This step can't be described in plain language. Check the details below, or deny it and ask Haruno what it is trying to do.”

If the safety check blocks a step outright, no card appears and the chat notes “[step] blocked by auto mode” (what to do). If the card comes back with “Couldn't deliver a response to the engine: …”, your answer did not reach Haruno: answer it again. To stop the whole reply instead of answering, click Stop or press ⌘. (Chats ▸ Cancel Turn). The chat, kept in History, is your record of what you allowed, and the Activities panel (⌥⌘0) lists each step Haruno took.

If Haruno is not the front app, a Permission required notification offers the card's buttons, and a website prompt arrives as Allow network access? With notifications off in System Settings ▸ Notifications, a card waits in the chat, but a website prompt refuses that connection after 55 seconds. A question card with Your answer and Send is not an approval (When Haruno asks you something).

Approvals in the normal view

The normal view has no approval settings: every chat works in Automatic mode inside the secure sandbox, and every card offers only Allow once and Deny. You choose only which connector actions always ask, with the Require confirmation switches; the safety check never approves those for you.

SettingIn the normal view
Permission modeAutomatic, fixed, also in a chat reopened from History. Chats ▸ Cycle Permission Mode (⌃⌘P) does nothing.
Secure sandboxAlways on. If it cannot start, the chat does not start: Haruno never runs without it.
Allow for this sessionNever offered: each step is approved on its own, a transaction-level approval rather than a standing authorization.
Custom servers and allowed hostsHidden, but any added in the Advanced view keep applying to new chats.

What the sandbox can see is in Data handling and security. For permission modes and session approvals, turn on the Advanced view (The normal view and the Advanced view); you do not need it to close the month.

Approvals in the Advanced view

Turning on Advanced view in Settings ▸ General adds a Default Permission Mode, a mode menu for each chat, the full card with Allow for this session, more answers on the website prompt, and per-tool settings for custom servers. New chats start in Ask each time unless you change it, so expect more cards.

Default Permission Mode

It sets where new chats start. Ask each time and Automatic also switch the open chat at once, Deny all makes it ask, and Allow all waits for the next new chat (⌘N).

ChoiceWhat it does
Ask each time (the default)Asks before each step that needs approval.
AutomaticThe automatic safety check decides, as in the normal view.
Allow allRuns steps without asking, even actions a Require confirmation switch covers. Use it rarely.
Deny allRefuses every step that would need approval, covered connector actions included.

Change the mode for the chat in front of you

Click + to the left of the chat box and open Permissions; its title names the mode, such as Permissions (Auto). Chats ▸ Cycle Permission Mode (⌃⌘P) steps through the same four modes. The menu changes only this chat, which keeps its mode when you reopen it from History. Allow all and Deny all are not in the menu: to leave either, change the Default Permission Mode and start a new chat.

ModeWhat it does
AutoThe automatic safety check decides.
AskAsks before each step that needs approval.
Accept EditsChanges to files in the folder Haruno works in go ahead; other steps ask.
PlanHaruno looks into the task, with reading and searching going ahead, and writes a plan first. A card then offers Approve plan, Send feedback (What should change?) and Reject; before the plan exists, it says “No plan file has been written yet.”

The full approval card

Here the card shows the request as Haruno sent it, with Allow once, Deny and Allow for this session. It may add a risk badge (Low risk, Medium risk or High risk), Auto mode flagged this action with the safety check's reason, or a line naming the standing rule that made it ask.

Allow for this session

It stops Haruno asking about that kind of step for the rest of the chat. The shield with a count above the chat box lists your Active grants; choose Revoke [rule] to withdraw one. A new chat starts with none.

A session approval outranks a confirmation switch
Allow for this session on an action a Require confirmation switch covers, such as sending an email, stops that switch asking for the rest of the chat. Use Allow once for anything that reaches other people.

The Sandboxed Engine switch

Settings ▸ Advanced ▸ Security holds Sandboxed Engine, on by default. Keep it on: without it, new chats have the same access to your Mac as the app itself, and the website list no longer applies. See Sandboxed Engine, and for what carries over between views, Settings: Advanced view.

Per-tool settings for custom servers

On the Mac, only a custom server's tools are set one by one (Custom servers; later, Edit… on the server's row). Built-in connectors have a Require confirmation switch instead. A custom server receives whatever Haruno sends its tools, including your companies' figures, so add only servers you trust.

SettingWhat Haruno may do
OnUse the tool without asking. For reading and looking things up.
ConfirmUse it only after you approve each use; Automatic mode never approves it for you. For anything that writes, sends or changes data.
OffNot use the tool at all.

Connector confirmation switches

Each built-in connector that sends, posts or changes something in your name has one switch that begins Require confirmation before…, on by default in both views. While it is on, every action it covers asks on a card, in Automatic mode too; reading never asks. Keep them on: they cover actions other people see and you cannot take back.

The switch appears once the connector is connected, on its row in the Connectors window (account menu ▸ Connectors…). A change applies from the next new chat (⌘N), on this Mac only. A note under a switch may say “In Automatic permission mode, writes are checked by an automated safety review instead of prompting you.” A covered action still asks in Automatic mode.

ConnectorSwitchWhat asks
GmailRequire confirmation before sending, replying, and deletingSending, replying, moving a message to Trash.
Google CalendarRequire confirmation before changing eventsCreating, changing, deleting events.
SlackRequire confirmation before posting and writingAnything that writes, such as posting, replying, scheduling a message or reacting.
DiscordRequire confirmation before posting to DiscordSending a message or file.
Cloud storageNo switchAlways asks before mirroring, syncing or uploading.

A covered action asks in every mode except Allow all, which runs it, and Deny all, which refuses it; the same goes for a custom server's Confirm tools. After Allow for this session on a covered action, it stops asking for that chat. Scheduled tasks: see Scheduled runs.

Websites: Let Haruno open this website?

The secure sandbox reaches only a list of sites (Which websites it can reach). For any other site, in every permission mode, the app asks Let Haruno open this website? and names it. Treat an unfamiliar site like an unfamiliar payee: deny it unless you know why Haruno needs it.

AnswerWhat happens
Allow onceHaruno can reach the site for the rest of this chat.
DenyThe site stays blocked for the rest of this chat, without asking again.
No answer within 55 secondsThat connection is refused; the next attempt asks again.
Always allow this website (Advanced view)Adds the site to your allowed hosts, so every new chat reaches it without asking.
Allow all sites for this session (Advanced view)Allows every site for the rest of this chat, and answers prompts still open. The chat notes “Connected to [site] (allowed for this session).”

A new chat (⌘N) asks again. In the Advanced view the prompt reads Allow the sandboxed agent to connect to this site?, and Allowed hosts lists the sites every new chat may reach.

“Haruno wants to read a page on [site].” is a different card: a single page read, judged like any other step, which can reach the page without this prompt. Messages, web searches and connector actions no switch covers also leave your Mac without it (What each action sends).

Scheduled runs

A scheduled task runs with nobody watching, so it shows no cards: every step is approved automatically, whatever your Default Permission Mode, and the Require confirmation switches do not apply. Instead, an email, reply, invitation with guests, Discord post or synced-folder change waits in Waiting on the Scheduled screen (⌘5) until you send or discard it: the approval card, after the fact. Changing or deleting an existing event is refused unless the task may send on its own, sites outside the sandbox's list are refused, and a question gets no answer.

A task is never given Slack or a custom server
A scheduled task can't use Slack or a server you added in the Advanced view, so nothing it does can go out through one. Ask in a chat instead: its confirmations still apply there.

A task's Let this automation send emails, invitations and cloud changes on its own switch is off by default. With it on, Gmail, Calendar, Discord and cloud-folder actions happen at once. See What waits and what happens at once.

On Windows

The Windows app has its own approval controls, and most of them appear only with the Advanced view switch in Settings ▸ General turned on (Normal and Advanced view on Windows).

TopicOn Windows
Permission modeNormal view: Auto, fixed. Advanced view: Settings ▸ Advanced ▸ Default permission mode (Default, Accept Edits, Plan, Auto, Bypass), and the permission chip in a chat, which opens a Permission mode menu with the same five.
Approval cardAllow once, Allow for this session and Deny, in both views. Session approvals are in the chat's Activities panel (Advanced view).
Per-action rulesOn, Off or Confirm for each connector action in Settings ▸ Connectors (Advanced view). Actions that send, post, pay, upload or change outside data start at Confirm.
Plan reviewApprove plan, Request changes, Reject plan.
Scheduled tasks and hooksNo Waiting list: an action set to Confirm is refused. To allow it, set it to On in the Advanced view, which also lets chats take it without asking.
WebsitesAdvanced view: Allow Web Fetch without asking in Settings ▸ Advanced. The built-in browser: Let Haruno use a browser and Sites Haruno may open in Settings ▸ Connectors.

More: Haruno on Windows.

Next steps

Connect the services you use, see what leaves your Mac, or set up work that waits for your review.