Core concepts
ReachFlow becomes easier to operate when every team member uses the same vocabulary. These concepts appear throughout the product and establish where data belongs and which controls apply.
On this page
Organization
An organization is the primary workspace and isolation boundary for a brand, business, or client. It owns the AI Brain, social connections, media, schedules, activity, usage, and related settings used by that brand.
Agencies normally create a separate organization for each client. A company with distinct brands may also separate them when their knowledge, permissions, audiences, or channels should not mix.
AI Brain
The AI Brain is the prepared organization context ReachFlow uses during generation. It can include audience information, brand voice, goals, approved source knowledge, memories, visual direction, and other rules that shape output.
Treat the AI Brain as maintained operational context. Review changes before they influence future content, especially when knowledge or memory can affect claims, positioning, tone, or visual direction.
Platform connection
A platform connection authorizes ReachFlow to work with a specific social provider and publishing identity. It represents real provider permissions, not only a saved platform name.
Connections can expire, lose permissions, or require reauthorization. Publishing readiness therefore depends on both the saved ReachFlow configuration and the current provider state.
Schedules, drafts, and calendar items
A reusable schedule describes a recurring publishing rule, while a daily schedule or calendar item represents planned work at a particular time. A draft contains content that is not yet released.
These objects are related but not interchangeable: the reusable rule defines rhythm, the dated item represents execution, and the draft holds the content and media that will be reviewed or published.
| Concept | Purpose |
|---|---|
| Weekday schedule | A reusable rule for recurring content on selected days and channels. |
| Daily schedule | The actual work prepared for a specific date, destination, and time. |
| Calendar item | A visible planning record placed in the content calendar. |
| Draft | Editable content and media that has not yet been published. |
Media
Media includes uploaded or generated images and other supported assets associated with an organization. Media should be attached to the correct draft and checked against the selected provider's requirements before publishing.
The organization media library helps teams reuse approved assets without mixing files between clients or rebuilding the same creative context.
Publishing state
Publishing state explains where work currently sits in the operational lifecycle. Exact labels can vary by workflow, but teams should be able to distinguish preparation, review, scheduling, processing, success, and failure.
- Draft or preparing: content is still being created or edited.
- Ready: required content, media, connection, and checks are available.
- Scheduled: the work is waiting for its configured publishing time.
- Processing: ReachFlow or the provider is handling the request.
- Published: the provider accepted the publishing action.
- Failed or needs attention: something must be corrected or authorized before completion.
AI credits and usage
AI credits represent usage of eligible generation operations. Plans can include different credit allowances and organization, platform, or storage limits. Usage visibility helps teams understand consumption before it interrupts planned work.
Publishing through a connected provider and generating AI content are separate operations, so a provider publishing failure does not automatically mean AI credits or generation were unavailable.
ChatGPT MCP connection
The ReachFlow MCP server exposes selected product capabilities to an authorized ChatGPT connection. OAuth identifies the user, scopes limit available actions, and the selected organization determines which ReachFlow context the conversation can use.
Publishing and destructive actions require explicit confirmation. Never paste secret API keys into a normal prompt; use the secure MCP connection and ReachFlow authorization flow.