Skip to main content
Approval preferences control when daoco must pause and ask before sensitive actions run in brand chat, post workflows, automations, and connected integrations.

Where to manage preferences

Brand owners and admins set defaults per brand:
1

Open Settings

Choose Settings from the manage sidebar.
2

Open the Brands tab

Select the brand you want to configure.
3

Find Approval gate

Use the Approval gate card to set brand-wide defaults.
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

PolicyWhat it covers
Scheduled social postsQueueing and scheduling posts across connected social accounts.
Provider write actionsNon-destructive writes through connected commerce, website, and work integrations.
Both policies default to Auto when connected for new brands.

Approval modes

ModeBehavior
Always askMatching actions always pause for your approval.
Learn after 3After 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 connectedNon-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.
  • Brand chat — when daoco asks before publishing, scheduling, or applying brand updates.
  • Create posts — review previews before publish or schedule actions run.
  • Integrations — how /integration uses approval gates for provider writes.
  • Workspace settings — open brand settings from the Brands tab.