Soku AIAutopilot is enabled per organization and configured per brand. It has three autonomy levels: L0, L1, and L2. These levels control how Autopilot handles proposals; they are not team roles or four general permission levels.
Turn on Autopilot
- Switch to the Brand where you want to use Autopilot.
- Open Settings → Labs.
- Turn on Autopilot. Only an Organization Admin can change this organization-level Labs switch.
- Open Autopilot from the left sidebar.
- In Runtime controls, turn on Autopilot, confirm Emergency stop is off, choose an autonomy level, and save the runtime limits.
If the Labs switch is on but the Autopilot entry is unavailable for this Brand, the Brand is not currently enabled for the feature. Use the in-app Feedback button or contact Soku support rather than looking for a hidden setting.
Choose an autonomy level
| Level | Product label | What happens |
|---|---|---|
| L0 | Review only | Autopilot can record findings and submit proposals, but it does not automatically approve them. Proposals wait for a person in Needs You. |
| L1 | Approval required | A proposal waits for a person to approve or reject it in Needs You. |
| L2 | Opt-in automation | A submitted proposal is checked again by the approval guardrail. If it passes, Soku can approve and queue it automatically; if it fails, it is blocked. |
In the current runtime, L0 and L1 share the same pending-proposal and manual-approval behavior. L2 is the level with a separate automatic-approval path.
L2 is the highest autonomy level currently available in the product. If you have seen the phrase “Full autopilot,” it refers to the destination of increasing autonomy rather than a separate L3 or fourth customer setting. To use the current highest level, choose L2 opt-in automation; proposal validation, guardrails, execution controls, and the activity log still apply.
Autonomy does not bypass safety controls. Emergency stop, wake budgets, monitor limits, proposal validation, cooldowns, and execution safeguards still apply at L2.
Team roles are separate
Soku customer organizations have two team roles:
- Admin — can invite members, change roles, manage integrations, and enable organization-level Labs features such as Autopilot.
- Member — can use the Brands made available to them, including chat, dashboards, and enabled product features, but cannot perform Admin-only setup.
If someone asks about “four permission levels,” first determine whether they mean team roles or Autopilot autonomy. For customer organizations, the role model is Admin / Member, while the Autopilot autonomy model is L0 / L1 / L2.
Other runtime controls
- Enable Autopilot controls whether future Autopilot evaluation runs for this Brand.
- Emergency stop prevents new Autopilot evaluations and new proposals from being auto-approved while it is on. It does not cancel work that was already approved or queued; check Needs You and Activity for existing work that may still run.
- Daily wake budget limits monitor-triggered wakes per day. Scheduled routines and planned goal reviews do not consume this monitor budget.
- Monitor cap limits how many monitors the Brand can keep.
Changing an autonomy level does not itself create a campaign, change a budget, or enable a scheduled routine. Review the Runtime controls and Activity timeline after saving.