# Scheduled-task permissions

A schedule runs without someone watching the composer, so authority must be explicit before it becomes active.

![Scheduled-task permissions](https://www.foxora.ai/docs/images/v5.0.8/reference/workflows.webp)

*Studio interface in English. Sample data.*

## Bound the automation

1. Give the schedule only the project, account, and connected apps it needs.
2. Assign agent steps to a compatible agent or crew with narrow capabilities.
3. Add an approval step before external writes, sends, deletes, purchases, or irreversible actions.
4. Test with safe sample data and inspect every tool result.
5. Publish only after the run succeeds without requesting missing interactive context.

## Expected result

Routine reads and transformations can complete unattended, while protected actions wait for approval or are refused by policy. Task modes and `Full Access` do not override hard policy, operating-system permission, plugin scope, or channel allow-lists.