Previews and approvals through AI

An assistant connected to Bizisy prepares changes; people decide them. Three things keep it that way: previews before every change, approvals for the changes a company chooses, and Activity for everything.

Previews first#

Every write tool takes dry_run. The servers' instructions tell the assistant to call a write with dry_run: true first, show the person what would happen, and commit only after they agree:

1. The person asks: "Move Ana to the Platform team from 1 November."
2. The assistant reads (org_people_list, org_units_list), then calls org_people_change_job with dry_run: true.
3. Bizisy runs every check and returns the result and a view_url to the preview in Activity. Nothing is saved.
4. The assistant shows the change; the person says yes.
5. The assistant calls the same tool without dry_run. The result's view_url points to the change in Activity.

The skills repeat it for bulk work: org_setup_apply and org_people_import_csv are always previewed, with counts and warnings shown before anything is written.

Approvals still apply#

When the company requires approval for job changes, terminations or pay, a change made through an assistant becomes a request like any other (Approvals): the tool result's approval says who must approve it. The assistant can't approve or reject (those tools refuse machines), and it can't change the approval settings: an assistant can never switch approval off.

Pay is never changed through an assistant: org_pay_add is web app only.

Everything in Activity#

Every change an assistant commits, every preview and every failed attempt is recorded in Activity with the app's name. A person (or HR, for the whole company) can see what the assistant did and what it tried, and follow each view_url to check.

What an assistant never gets#

• Other people's private details or pay (What machines can see).
• Invite links: they're emailed to the person, never returned to an assistant.
• Secrets: API keys and webhook signing secrets are created in the app only.