Where to manage preferences
Brand owners and admins set defaults per brand:
These defaults apply across connected social accounts and integrations for that brand. Individual users cannot make approval behavior more permissive than the brand default.
Policy types
| Policy | What it covers |
|---|---|
| Scheduled social posts | Queueing and scheduling posts across connected social accounts. |
| Provider write actions | Non-destructive writes through connected commerce, website, and work integrations. |
Approval modes
| Mode | Behavior |
|---|---|
| Always ask | Matching actions always pause for your approval. |
| Learn after 3 | After you approve the same action shape three times, daoco can auto-allow similar actions for 14 days. The next matching action after that window asks again. Rejecting an action resets the learning counter. |
| Auto when connected | Non-destructive writes can run without an extra prompt when the brand policy allows it and the connection is healthy. |
Automations and chat
Scheduled automations follow the same approval rules. If a run needs approval and no policy allows bypass, the automation pauses until someone approves or denies the action. Run history can show approval audit events with the decision, action type, and policy that applied. See Automations preview.Related guides
- Brand chat — when daoco asks before publishing, scheduling, or applying brand updates.
- Create posts — review previews before publish or schedule actions run.
- Integrations — how
/integrationuses approval gates for provider writes. - Workspace settings — open brand settings from the Brands tab.