Skip to content

Governance

Every script has an owner, the person who created it. The script’s owner or a workspace owner or admin controls who can use the script and which runs need approval. Both are on the script’s page, under Settings.

  • Everyone in the workspace. This is the default.
  • Only these teams, chosen from the workspace’s teams (Settings → Members). Members outside those teams don’t see the script anywhere: not in the app, through the API, as an agent’s tool or in the runs list. Workspace owners and admins always see everything.

Guests see only what’s shared with a team they’re in.

To change access from your code, use reminix.scripts.update(slug, { access: "teams", teamIds: [...] }) in TypeScript or reminix.scripts.update(slug, access="teams", team_ids=[...]) in Python. To share the script with the whole workspace again, set access: "workspace". See Change a script.

Policy What waits for a person
No approval (the default) Nothing. Runs start right away.
Agents need approval Runs that an AI agent starts through the MCP server, and runs a webhook trigger starts.
Every run needs approval (Business) Every run, except runs that workspace owners, admins and API keys start themselves. An agent’s run, and a webhook trigger’s, always waits.

For example, with Agents need approval on refund-customer, an agent’s refund waits for a person. A refund that someone on your team starts from the app runs right away.

A run that needs approval shows as Awaiting approval. Reminix notifies the workspace’s owners and admins in the app, by email and by push. Each of them chooses how in Account › Notifications › Settings. Push needs turning on for each device. They decide on the run’s approval page, which shows the run’s inputs in full. If one of them approves it, the run uses the version and inputs the request named. If they deny it, or nobody decides within a day, the run ends as Cancelled.

From your code, reminix.run(...) waits for the decision. It gives you the approval link through onApproval in TypeScript or on_approval in Python. When an agent starts the run, the tool’s reply says the run is waiting and includes the link.

Each environment has its own approval rule, and a run follows the stricter of the environment’s rule and the script’s policy. In an environment where every run needs approval, a member’s run of a script with no approval still waits for a person. The approval page says which environment the run is for.

The policy is a setting on the script, not part of its code, so publishing new code can’t loosen it. If a workspace moves to a plan without every-run approval, a script that has it keeps it.

The script’s owner or a workspace owner or admin can publish a version. In two cases, the publish becomes a request that a workspace owner or admin approves:

Who publishes When the publish needs approval Who can approve
An AI agent connected through MCP Always Any workspace owner or admin
Anyone When the workspace turns on “Publishing needs a second person” under Settings → Scripts → Publishing (Business) Another workspace owner or admin, not the person who asked

If the person who asked approves their own request, Reminix refuses it and the request fails. Ask again, and have someone else approve it.

Settings, Publishing: the checkbox 'Publishing needs a second person', not ticked. Settings, Publishing: the checkbox 'Publishing needs a second person', not ticked. Settings, Publishing: the checkbox 'Publishing needs a second person', not ticked. Settings, Publishing: the checkbox 'Publishing needs a second person', not ticked.

The workspace’s audit log records every change to access, policies and settings, and every approval.