The bot does the work. You decide what goes out.
Reading and drafting run on their own. Anything that changes something outside BusyBee.Day waits for your OK, and you can tighten or loosen that per action.
BusyBee.Day bots ask before they act. An approval card shows exactly what the bot wants to do, and nothing happens until you approve it. Deleting tasks, recurring changes and actions in connected apps that are not read-only ask first by default. You can set each connected action to run on its own, ask first or off, and pause all bots in a project at once.
What asks first by default
| Action | Default | Why |
|---|---|---|
| Reading tasks, documents and web pages | Runs on its own | Nothing changes |
| Creating tasks, comments and documents in BusyBee.Day | Runs on its own | You see it and can undo it |
| Moving a task to the trash | Asks first | It removes work from view |
| Making a task recurring, some schedule changes | Asks first | It repeats without you |
| Read-only actions in a connected app | Runs on its own | The service marks them as read-only |
| Any other action in a connected app | Asks first | It changes something outside BusyBee.Day |
| Saving memory from an email or web page | Asks first | Outside text could carry hidden instructions |
More ways to stay in control
- Review: a task result waits for you to approve and complete it.
- Stop: end any running work from the task or chat.
- Pause: switch off all bots in a project at once; nothing new starts.
- Budget: set a monthly credit limit per project. When it is used up, bots there stop until next month.
- Labelled output: everything a bot writes is shown as coming from the bot.
Why outside content is treated with care
A web page or an email can contain text written to trick an AI into doing something you never asked for. This is called prompt injection. BusyBee.Day keeps the risky steps behind your approval, checks what bots save into memory for hidden instructions, and keeps the bot's computer away from its internal network.