Octo Act
Instructions that Octo turns into drafted actions across products (packages, groups, floors, Quests), executed on your approval or within Canvas guardrails.
Octo Act turns a plain-language instruction into a drafted change. Octo shows you the draft, rendered as the result rather than as a form, and runs it when you approve. Inside the guardrails you set in Canvas, it can run approved kinds of change without asking each time.
This capability arrives as a proposal when your network needs it, filled in from your brand context, and goes live when you confirm it. It's part of Octo, and Octo operates your Brand Control Center: Octo proposes, you approve explains the loop every action follows.
When to use it
Any Brand Control Center (BCC) user with the role to perform the action can use it. Octo can't do more than the person asking.
| You ask | Octo drafts |
|---|---|
| "Create a Paid Partner package for the running group for next month and list it." | The package and its listing, shown before anything is sold |
| Raise the floor on a placement | The new floor for that placement, under your floor and yield rules |
| Run a Quest in a group | The Quest with its brief, deadline, reward, and target group |
| Add a group to a community | The group with its keywords, topics, and categories |
How it works
- You give Octo an instruction in the Octo panel. It drafts the change and shows you the result.
- You approve it, edit it inline, or decline it. Every decision teaches Octo.
- Octo acts only with the permissions of the role using it. It never acts outside your brand safety profile, set in Set moderation, roles, and brand safety.
- Inside Canvas guardrails, an approved kind of change runs without a separate approval. Canvas offers three approval modes: auto, review, or review-only-for-paid.
- Nothing Octo does becomes public, paid, or sent without an approval you gave, on the item or as a standing rule. Octo Autonomy and Approvals sets those levels per change type.
- Where you connect a repository or CMS, code changes arrive as pull requests for your developer to approve. Octo never deploys on its own.
- Every action is logged with the approval or rule that allowed it.
Set it up
Octo proposes Act with these steps already done. You review the result and confirm it.
- Ask Octo to do something, review the draft, and approve it. Octo: the orchestration and generative commerce layer shows how Act fits with Ask and Resolve.
- Set auto-approval bounds in Canvas. Learn how in Canvas: run your network with growth and monetization agents.
Settings
| Setting | What it controls |
|---|---|
| Role scope | Which actions Octo can take for each person, matching that person's role |
| Guardrails | The Canvas bounds inside which approved changes run without asking: brand safety profile, topics to avoid, partner exclusions, and approval mode |
| Audit | The record of every Octo action, kept under Settings > Audit |
Roles are set under Settings > Team, and guardrails in Canvas. Per-change-type levels sit under Octo > Autonomy.
What it reports
Octo Act keeps one record, under Settings > Audit. Audit Log, Two-Factor, and SSO for BCC explains the log and its export.
- Audit log of Octo actions: every action Octo took, by user and time, with the approval or rule that allowed it.
Build on it
Octo Act runs in Brand Control Center and needs no code. Your developer only steps in to approve code changes Octo opens in a connected repository.
The Octo calls in the Business Account API are proposed, not live. Live API today and the Business Account API roadmap maps what you can call now to what's planned.
