Octo Autonomy and Approvals
The approval model behind every step: each kind of change runs at ask every time, do and report, or off. Approvals become standing rules you can revoke, and every action is logged with the approval that allowed it.
Octo does the work in Brand Control Center (BCC), and you approve it. Autonomy sets, for each kind of change, whether Octo asks first, acts and reports back, or stays off. Nothing Octo does becomes public, paid, or sent without an approval you gave, on the item or as a standing rule.
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 change follows.
When to use it
Set it once at launch. Widen it as you trust Octo with routine changes, and keep public, paid, and sent changes on ask every time.
| Level | What Octo does |
|---|---|
| Ask every time | Drafts the change and waits for your approval; the default for anything public, paid, or sent |
| Do and report | Makes the change and reports it; for changes you approved before and marked as trusted |
| Off | Doesn't make this kind of change |
Routine work suits do and report: classifying new videos, refreshing feeds, keeping ads.txt and sellers.json current, clearing moderation items inside the baseline, and re-issuing keys.
How it works
- Approvals you give repeatedly are offered as standing rules. A rule is always one click to revoke.
- Each change type has a named approver, such as the Developer for code changes and Revenue for agreements.
- Where you connect a repository or CMS, Octo opens code changes as pull requests for your developer to approve. Octo never deploys on its own.
- Spend and reach ceilings force an ask, even for a change type set to do and report.
- Support fixes Octo makes without a person, such as re-running verification, also run under the autonomy you set. 24/7 Octo-enabled support lists them.
- The audit log records every Octo action with the approval or rule that allowed it.
Set it up
Octo proposes your autonomy settings with these steps already done. You review the result and confirm it.
- Open Octo > Autonomy. By default, anything public, paid, or sent is set to ask every time.
- Promote a repeated approval to a standing rule when Octo offers it, or set a level per change type. Octo Act shows how approvals work on a single change.
- Name the approver per change type, such as the Developer for code changes and Revenue for agreements. Roles come from Invite your team and assign roles.
Settings
| Setting | What it controls |
|---|---|
| Level per change type | Ask every time, do and report, or off |
| Approvers | The person or role who approves each change type |
| Quiet hours | The hours you set as quiet for Octo's changes |
| Spend and reach ceilings | The limits above which Octo must ask, whatever the level |
Change all four under Octo > Autonomy. Roles that can serve as approvers are set under Settings > Team.
What it reports
Every Octo action is in the audit log under Settings > Audit. Audit Log, Two-Factor, and SSO for BCC explains the log and its export.
- Actions by level: what Octo did at each autonomy level.
- Approvals by person: who approved what.
- Rules in force: the standing rules active now.
- Actions held for approval: changes Octo drafted and is waiting on you to approve.
Build on it
Autonomy runs in Brand Control Center and needs no code. Your developers approve the code changes Octo opens in a connected repository.
The autonomy and proposal 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.
