Managed Service (Done-for-You)

In the Managed model the Duaba team runs your social presence — strategy, content, community, and paid. You never log into Postiz. Instead you get a read-only-friendly surface inside DuabaConnect where you request content, review drafts, and approve (or reject) work before anything ships.

Want to run it yourself instead? See Self-Serve.

How it differs from Self-Serve

A client’s SocialLink.mode is set to managed. Under the hood Duaba operates Postiz under one operator account, with one Postiz “Customer”/group per client. The Connect server’s own database is the source of truth for content requests and drafts; the Postiz public API is driven best-effort by the operator and degrades gracefully if it’s unreachable.

1. Social overview

The managed overview pulls your group’s recent posts and analytics through the operator’s Postiz key and shows them as a monitoring view — recent posts (content, platform, state, publish date) plus KPI tiles (impressions, engagement, followers). When Postiz is unreachable the view degrades gracefully.

2. Content requests

You ask for content through a simple request form. Each request captures:

• a content type (defaults to post);
• a description (required) of what you want;
• optional reference images.

Requests are stored on the Connect server and move through statuses (new → in production → delivered as drafts). You can list your own requests at any time.

3. Draft generation & the approval interface

The Duaba team (or an automation) produces draft posts for you. A draft carries a caption, media, a target platform, an optional schedule time, and a recurring flag. Drafts you need to act on appear in your pending approvals list.

For each pending draft you can:

• Approve — Connect marks it approved and pushes it to Postiz (queuing an existing Postiz post, or creating one from the caption + media). If Postiz accepts it, the draft becomes scheduled; if Postiz is unreachable it stays approved with a “our team will schedule it shortly” note.
• Reject — Connect marks it rejected and stores your reason so the team can revise.

Content request → team/AI drafts a post → pending_approval
      → you Approve → pushed to Postiz → scheduled → published
      → you Reject (with reason) → team revises

Campaign scheduling

Managed content rides the same campaign scheduler as Self-Serve: active campaigns emit review-ready batches on a cadence, and approved/scheduled posts auto-publish when due. The scheduler runs about every 15 minutes (wired to the DPS job scheduler or a cron hitting the internal run-scheduler route).