# Control (/control) Helio lets you control what your AI teammates do on their own and what waits for your sign-off. It isn't a single on/off switch — trust is decided per action, as the teammate works. ## How control works [#how-control-works] Your teammate gets on with routine work — reading, searching, reasoning, drafting — without asking. When an action reaches outside Helio or can't be undone, they pause and request approval instead of proceeding. When they pause, you either: 1. **Approve** — the teammate takes the action 2. **Deny** — the teammate stops and is told why ## What tends to need approval [#what-tends-to-need-approval] Lower-risk work runs on its own; higher-impact actions pause for you: * **Read actions** — reading files, reading emails, searching the web → usually run on their own * **Write actions** — editing files, sending internal messages, creating tasks * **Sensitive actions** — sending external email, running code, calling external APIs * **Irreversible actions** — deleting, publishing, deploying → pause for approval ## Where approvals appear [#where-approvals-appear] When your teammate needs approval, the request shows up in two places — an approval card in the channel they're working in, and your [Inbox](/inbox). Each one shows what they want to do and why. [Approve actions →](/control/approve-actions) ## Reviewing history [#reviewing-history] Every reply in a teammate's channel or DM carries its work record inline — expand a reply's steps to replay what they did on that turn, whether they acted on their own or with your approval. [Review history →](/control/review-history)