Permissions on your tasks
Your assistant can look up your tasks and create new ones without asking. But it doesn't run or change one of your tasks without your confirmation, unless you've already allowed it.
What asks for confirmation and what doesn't
| What your assistant wants to do | Does it ask you? |
|---|---|
| Look up your tasks, read them and see their runs | No |
| Create a new task (it's created paused) | No |
| Run one of your tasks | Yes |
| Edit one of your tasks: modify, pause, activate or reschedule it | Yes |
| Run loose steps that aren't saved in any task | Yes, every time |
It doesn't ask when you've already allowed it another way:
- Tasks that same connection created. What your assistant creates, it can run and edit without asking. Permissions are per connection: a task created from Claude asks you to confirm if your ChatGPT connection wants to run it.
- Tasks you've approved for this connection, when your assistant runs them with that task's own tool. Changing them does ask you. How to approve one
- Tasks you've already answered "Yes, always" to on that connection.
The connection has no tool to delete tasks: you do that yourself from the dashboard.
Run and edit are separate permissions
- Run really does what the task does: send, publish, write…
- Edit means changing, pausing, activating or rescheduling the task.
Allowing one doesn't allow the other.
How you confirm
- You ask your assistant for something that means running or changing one of your tasks.
- Botize doesn't do it yet. It tells your assistant it needs your confirmation and gives it a link to MCP connections, which your assistant will pass on to you. If you connected before 15 September 2026, the link may open the panel in Spanish: use botize.com/en/mcps, or reconnect.
- Open the link signed in to Botize. In the connection you'll see Waiting for your confirmation, with "Your agent wants to run" or "Your agent wants to change".
- Answer:
- No: nothing happens.
- Yes, just this once: allows that exact action, with the same data, a single time.
- Yes, always: it won't ask again for that task and that permission on that connection.
- Go back to your assistant and tell it you've confirmed, so it repeats the action. Your assistant doesn't find out by itself that you've answered.
Do it right away. The pending request and the "Yes, just this once" expire after about an hour. If you take longer, or if your assistant repeats the action with different data, it will ask you again.
If your assistant wants to run loose steps, you'll also see it under Waiting for your confirmation, but only with No and Yes, just this once. Every list of steps is different, and an "always" would be a blank cheque.
Remove a "Yes, always"
In MCP connections, under Task permissions, you'll find the tasks that connection can run or edit without asking you, including the ones it created. Click Remove on any of them: next time it will ask you first.
Your assistant's own confirmation is separate
Some assistants also ask for their own confirmation before using tools that change things. In ChatGPT, for example, it depends on the plugin's permission setting. It's independent of Botize's, so you may see both.
Tasks created before mid-September 2026
Tasks an assistant created before mid-September 2026, including some from the 15th itself, weren't recorded as its own. The first time it wants to run or edit them, it will ask you to confirm.