Understanding the approval workflow

Every post in Misar Social moves through a defined approval state machine before it can be published. STATES - Draft: The post has been generated but not reviewed. - Pending Review: The post has been submitted for approval (manual or via GitHub trigger). - Approved: A team member has approved the post. It can now be scheduled or published. - Rejected: The post was reviewed and declined. It moves to the archive. - Scheduled: The post is approved and queued for publishing at a specific time. - Published: The post has been successfully sent to the platform. - Failed: Publishing failed (e.g., token expired). The post stays in Failed state for retry. WHO CAN APPROVE - Org admins can approve any post. - Members can approve their own posts if the org setting "Member self-approval" is enabled. AUTO-PUBLISH If you set AUTO_PUBLISH = true in Settings → EchoForge, posts from GitHub triggers are approved and scheduled automatically. This skips the Pending Review step. Use with caution on production accounts.