# PostRout Documentation > Complete, human-readable product documentation for PostRout, an AI publishing platform that turns one Markdown source into reviewed, destination-specific publications. Documentation index: https://postrout.com/docs LLM index: https://postrout.com/llms.txt Last updated: 2026-09-17 # Quickstart URL: https://postrout.com/docs/quickstart Category: Start here Summary: Create your first post, generate channel-ready versions, and prepare them for publishing. Updated: 2026-09-17 ## Before you begin You need a PostRout account and a Markdown draft. You can connect publishing channels before you start, or generate versions first and connect a destination when you are ready to publish. - Use a clear title and descriptive headings in your source. - Keep links, images, and code samples in standard Markdown. - Decide whether the post belongs to your main workspace or to a Studio Brand Profile. ## Create your first post 1. **Open Posts:** Sign in, open Posts, and choose New post. 2. **Add the source:** Upload a .md file or paste your Markdown into the editor. 3. **Choose channels:** Select the destinations you want PostRout to prepare. Only choose channels that fit the subject and audience. 4. **Generate versions:** Generate the post and wait for each selected channel to finish. 5. **Review:** Open every generated version. Check its hook, formatting, links, tags, calls to action, and canonical source. 6. **Publish or schedule:** Publish connected destinations, schedule supported workflows, or copy a manual-channel version into its destination. Note: PostRout generates destination-specific drafts. You remain responsible for reviewing the final wording and complying with each destination's rules. ## What to read next - Markdown and front matter for a reliable source file. - Brand Voice for consistent tone and terminology. - Channels for authentication and destination setup. - Generation and review for quality-control guidance. # Studio overview URL: https://postrout.com/docs/studio Category: Brand system Summary: Run separate brands, products, clients, or regions from one multi-brand publishing workspace. Updated: 2026-09-17 ## What is Studio? Studio is PostRout's multi-brand workspace. It keeps the context and publishing operations for each identity separate while giving a team one place to create, approve, schedule, and publish content. Use one Brand Profile for every brand, product, client, publication, or region that needs its own voice, knowledge, assets, channels, posts, and schedule. Studio availability depends on your plan. ## How Studio works Create one Brand Profile for every identity that needs its own content and publishing setup. 1. **Create a profile:** Add the brand, product, client, or region. 2. **Add context:** Choose its voice and store brand knowledge. 3. **Connect channels:** Link the destinations owned by that brand. 4. **Create and approve:** Generate on-brand versions for each channel. 5. **Schedule and publish:** Manage the queue from the brand workspace. ## How is Studio organized? - Brand Profiles separate identities and their publishing configuration. - Knowledge records important company, product, audience, and positioning context. - A default Brand Voice guides generated writing for the profile. - Assets keep reusable brand media with the profile. - Channels belong to the Brand Profile and do not automatically share credentials with other brands. - Posts and Schedule show the profile's content workflow and publishing queue. ## Studio versus the main workspace Use the main workspace when you publish for one identity and do not need brand-level separation. Use Studio when multiple identities require different context, voices, assets, credentials, approvals, or schedules. Note: Never connect a client's or regional account to the wrong Brand Profile. Channel credentials and generated history should stay with the identity that owns them. # Brand Profiles URL: https://postrout.com/docs/brand-profiles Category: Brand system Summary: Create a dedicated publishing workspace for one brand and everything used to represent it. Updated: 2026-09-17 ## What belongs in a Brand Profile A Brand Profile is the operating boundary for one identity. Its settings should answer who the brand is, who it serves, how it communicates, and where it publishes. - Identity and overview details - Brand knowledge and source material - Default Brand Voice - Brand-owned publishing channels - Reusable assets - Posts, approvals, and scheduled publications ## Create a profile 1. **Open Studio:** Choose Create Brand Profile. 2. **Describe the identity:** Use a recognizable name and add details that distinguish it from your other profiles. 3. **Select a default voice:** Choose an existing global Brand Voice, or create one before returning to Studio. 4. **Save and open the profile:** Review the overview before adding knowledge, assets, and channels. ## Keep profiles separate - Create separate profiles when audiences, products, regions, compliance rules, or publishing accounts differ. - Do not create separate profiles for minor campaign variations; use templates or post-level editing instead. - Review the active Brand Profile before creating a post or connecting a channel. - Use clear profile names so team members can identify the owner at a glance. # Brand Voice URL: https://postrout.com/docs/brand-voice Category: Brand system Summary: Teach PostRout the tone, vocabulary, audience, and writing rules that generated content should follow. Updated: 2026-09-17 ## What does Brand Voice control? Brand Voice is the reusable writing profile PostRout follows while generating and adapting content. It helps outputs remain recognizable even when the format changes between long-form publications and social channels. - Audience and level of technical knowledge - Tone, personality, sentence style, and point of view - Preferred terminology and phrases - Words, claims, and styles to avoid - Industry, positioning, and writing references - SEO and AI-generation guidance when available on your plan ## Create a useful voice 1. **Name the voice:** Use a name that tells the team where it applies, such as Product Education or Founder LinkedIn. 2. **Describe the audience:** Be specific about roles, problems, existing knowledge, and what readers should do next. 3. **Define the tone:** Choose concrete traits and explain what they mean in practice. 'Clear and direct' is more useful with examples. 4. **Add vocabulary rules:** Record product names, capitalization, preferred phrases, prohibited claims, and language to avoid. 5. **Add references:** Use representative writing samples when your plan supports advanced voice controls. 6. **Test and refine:** Generate the same source for two different channels, then adjust the voice where the result is too generic or too rigid. ## Defaults and overrides A workspace default helps ordinary posts start consistently. A Studio Brand Profile can select its own default global Brand Voice. Always confirm the selected voice before generation when a workspace contains multiple voices. Note: Brand Voice guides generation; it does not replace review. Check factual claims, legal language, links, and platform-specific requirements before publishing. # Channels URL: https://postrout.com/docs/channels Category: Distribute Summary: Connect official platforms, configure manual destinations, and keep publishing credentials scoped correctly. Updated: 2026-09-17 ## What does a channel do? A channel tells PostRout where content is going and how that destination accepts it. Channel configuration determines whether PostRout can publish directly, needs an API key or OAuth authorization, or prepares content for manual publishing. ## Channel types - Official channels use a built-in PostRout integration. - OAuth channels send you to the provider to authorize the correct account. - Credential-based channels require a supported API key or token. - Manual channels generate a destination-ready version that you copy and publish yourself. - Custom channels connect another API or webhook when your plan supports them. ## Connect safely 1. **Choose the correct scope:** Use account-level Channels for the main workspace or open a Brand Profile's Publishing Channels for a brand-owned destination. 2. **Select the destination:** Read the connection requirements before entering credentials or starting OAuth. 3. **Authorize the owner account:** Confirm the provider account, publication, organization, or profile is the one you intend to use. 4. **Test the connection:** Use the available test or reconnect action before relying on the channel for a scheduled publication. 5. **Review destination settings:** Check defaults such as publication, canonical URL handling, tags, and automatic posting behavior. ## Connection status - Connected means the destination is authorized and available. - Ready may indicate that PostRout can prepare content but the final publish remains manual. - Reconnect means authorization has expired or changed. - Error means the provider rejected the connection or a required setting is missing. Note: Disconnecting a Brand Profile channel affects that profile only. Existing publication history may remain associated with previously published remote posts. # Markdown and front matter URL: https://postrout.com/docs/markdown-and-front-matter Category: Create Summary: Prepare a clean source file with metadata, headings, links, images, and code blocks. Updated: 2026-09-17 ## Recommended source format Markdown is the source of truth for a PostRout post. A well-structured source gives the generator reliable content boundaries and makes the resulting channel versions easier to review. ```markdown --- title: "A practical guide to content routing" description: "How to adapt one source for several publishing channels." tags: - publishing - markdown canonical_url: "https://example.com/content-routing" --- # A practical guide to content routing Start with a short introduction that states the reader's problem. ## Build one reliable source Use descriptive headings, complete links, and fenced code blocks. ```ts const destination = "dev-community"; ``` ``` ## Formatting guidance - Use one H1 title and organize the body with H2 and H3 headings. - Use fenced code blocks and include a language when known. - Use descriptive link text instead of raw URLs when possible. - Give images useful alt text and verify that their URLs are publicly accessible. - Keep the canonical URL pointed at the preferred original source. - Treat tags as destination suggestions; each platform may enforce its own limits. ## Before generation - Remove private notes, credentials, placeholders, and unpublished customer information. - Check that product names, facts, dates, and links are current. - Make the main takeaway explicit rather than expecting the generator to infer it. - Preserve important qualifications and citations in the source. # Generation and review URL: https://postrout.com/docs/generation-and-review Category: Create Summary: Generate channel-specific versions and apply a consistent quality review before approval. Updated: 2026-09-17 ## How does generation work? PostRout reads the source, selected Brand Voice, available brand context, template, and destination requirements to prepare a version for each selected channel. Different channels may complete at different times or return different statuses. ## Review every version 1. **Compare with the source:** Make sure the central argument, evidence, and required qualifications remain intact. 2. **Check the opening:** Confirm the hook fits the destination without becoming misleading or overly promotional. 3. **Check structure:** Review headings, paragraph length, lists, code, tags, and truncation for the target format. 4. **Check brand consistency:** Verify terminology, capitalization, tone, calls to action, and avoided language. 5. **Check publishing details:** Verify links, mentions, media, canonical source, selected account, and any destination-specific settings. 6. **Approve intentionally:** Only approve a version after the channel preview is ready to represent the brand publicly. ## Generation states - Pending or generating: the channel version is still being prepared. - Generated: a draft is available for review. - Edited or reviewed: changes or checks have been recorded. - Approved: the version is ready for the publishing workflow. - Failed: generation did not complete for that channel; inspect the error before retrying. # Publishing and scheduling URL: https://postrout.com/docs/publishing-and-scheduling Category: Distribute Summary: Publish approved versions now, schedule them for later, and understand publishing states. Updated: 2026-09-17 ## Before publishing - Confirm the active workspace or Brand Profile. - Confirm the destination account and publication. - Review every selected channel version. - Verify links, media, tags, mentions, and canonical URLs. - Check that the channel connection is healthy. ## Publish now 1. **Select approved versions:** Exclude channels that still need editing or authorization. 2. **Start publishing:** Keep the page open while the operation begins and watch each channel status. 3. **Verify the remote result:** Open the published destination and confirm formatting, media, and links. 4. **Handle partial results:** If one destination fails, do not republish successful channels. Retry only the failed destination after resolving its error. ## Schedule a publication When scheduling is available, choose the date and time, confirm the displayed timezone or UTC preview, and select the approved channel versions to include. Recheck channel authorization before an important scheduled campaign. - Scheduled: queued for the selected time. - Publishing: delivery is in progress. - Published: the selected destinations completed successfully. - Partially published: at least one destination succeeded and another failed. - Failed or canceled: inspect the reason or create a new schedule after correcting it. # Custom Channels URL: https://postrout.com/docs/custom-channels Category: Distribute Summary: Send approved content to your own API, webhook, or manual publishing workflow. Updated: 2026-09-17 ## When to use a Custom Channel Use a Custom Channel when a destination does not have a built-in PostRout integration, when your organization publishes through an internal endpoint, or when you need a repeatable manual export format. Availability depends on your plan. ## Configuration checklist - Choose API, webhook, official, or manual behavior as available. - Set the destination name and ownership clearly. - Choose the authorization method required by the endpoint. - Map the title, body, metadata, and other expected fields. - Store secrets only in credential fields—never inside templates or example bodies. - Test with non-sensitive sample content before activation. ## Operate safely 1. **Create as a draft:** Complete the configuration without exposing it to normal publishing yet. 2. **Test the endpoint:** Confirm authentication, request shape, response handling, and error messages. 3. **Activate:** Activate only after a successful test and a review of the destination account. 4. **Monitor the first publish:** Verify the received payload and resulting remote content. 5. **Rotate credentials:** Replace credentials immediately if access changes or a secret may have been exposed. Note: Do not place API keys, bearer tokens, or passwords in Markdown, Brand Knowledge, Brand Voice instructions, templates, or public documentation. # Troubleshooting URL: https://postrout.com/docs/troubleshooting Category: Help Summary: Resolve common source, generation, connection, and publishing problems. Updated: 2026-09-17 ## A version failed to generate - Confirm the source contains readable content and is not only front matter. - Remove malformed Markdown or an unusually large embedded block. - Retry only the failed channel after the other versions finish. - If it fails again, record the post, channel, time, and displayed error for support. ## A channel will not connect - Confirm you are connecting the intended account and Brand Profile. - Check that the provider token or API key has the required publishing permission. - Complete OAuth again if the status says Reconnect. - Disable browser privacy extensions temporarily if they block an OAuth redirect. - Use manual publishing when a provider no longer supports new API connections. ## Published content looks wrong - Compare the published page with the reviewed PostRout version. - Check whether the destination removed unsupported Markdown, media, tags, or links. - Correct the remote post when urgent, then update the PostRout version before republishing. - Do not retry every channel when only one destination is affected. ## Contact support Include your account email, workspace or Brand Profile, post title, destination, approximate time, and the exact error message. Never email channel passwords, API keys, access tokens, or private customer content. # Account and workspace setup URL: https://postrout.com/docs/account-and-workspace Category: Start here Summary: Configure the identity, timezone, and workspace foundations used by every PostRout workflow. Updated: 2026-09-17 ## Understanding account and workspace setup For new workspace owners, the goal is to create a dependable base before connecting channels or inviting collaborators. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - workspace identity - default timezone - support and account details ## Account and workspace setup procedure 1. **Define the account and workspace setup outcome:** For new workspace owners, confirm that the intended result is to create a dependable base before connecting channels or inviting collaborators. Record the owner and the decision this workflow should support. 2. **Prepare workspace identity:** Use workspace identity as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with default timezone:** Run a controlled draft, preview, or connection test using default timezone. Do not expose credentials or rely on an important publication as the first test. 4. **Verify support and account details:** Review support and account details against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals using a personal test identity in production. Track setup completion over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - using a personal test identity in production - choosing the wrong timezone - sharing account access instead of inviting users Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - setup completion - timezone corrections - account-access incidents # Create and manage posts URL: https://postrout.com/docs/creating-posts Category: Create Summary: Create a source post, select destinations, and understand its lifecycle in PostRout. Updated: 2026-09-17 ## Understanding create and manage posts For writers and editors, the goal is to keep the source, generated versions, status, and publishing history together. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - new Markdown uploads - pasted drafts - posts created inside a Brand Profile ## Create and manage posts procedure 1. **Define the create and manage posts outcome:** For writers and editors, confirm that the intended result is to keep the source, generated versions, status, and publishing history together. Record the owner and the decision this workflow should support. 2. **Prepare new Markdown uploads:** Use new Markdown uploads as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with pasted drafts:** Run a controlled draft, preview, or connection test using pasted drafts. Do not expose credentials or rely on an important publication as the first test. 4. **Verify posts created inside a Brand Profile:** Review posts created inside a Brand Profile against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals duplicate sources. Track posts completed over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - duplicate sources - unclear titles - creating content in the wrong workspace Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - posts completed - draft age - versions generated per post # Templates URL: https://postrout.com/docs/templates Category: Create Summary: Use repeatable structures for common content types without turning every article into the same post. Updated: 2026-09-17 ## Understanding templates For teams producing recurring tutorials, launches, and updates, the goal is to capture useful structure while leaving room for subject-specific evidence. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - tutorial outline - launch announcement - weekly product update ## Templates procedure 1. **Define the templates outcome:** For teams producing recurring tutorials, launches, and updates, confirm that the intended result is to capture useful structure while leaving room for subject-specific evidence. Record the owner and the decision this workflow should support. 2. **Prepare tutorial outline:** Use tutorial outline as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with launch announcement:** Run a controlled draft, preview, or connection test using launch announcement. Do not expose credentials or rely on an important publication as the first test. 4. **Verify weekly product update:** Review weekly product update against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals overly prescriptive boilerplate. Track template reuse over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - overly prescriptive boilerplate - outdated required sections - templates containing brand secrets Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - template reuse - sections removed during editing - time to first complete draft # Source word limits URL: https://postrout.com/docs/source-word-limits Category: Create Summary: Understand plan limits and prepare substantial source material that fits the active allowance. Updated: 2026-09-17 ## What the source limit applies to The source is the Markdown you upload or paste before generating channel versions. Its allowance is separate from the length accepted by a destination and from the AI credits available to your workspace. A source that fits does not guarantee that every generated version fits its destination. Use the allowance shown in your current workspace or the validation message returned when submitting a draft. Early-access pricing is still being finalized, so this guide does not promise a fixed word allowance for every account. ## Before uploading a long draft - Keep a copy of the full original before shortening it. - Choose one main topic and identify the audience and intended outcome. - Remove duplicated introductions, repeated appendices, and copied navigation text. - Keep citations, code required for the example, and qualifications that change the meaning. ## If the source is rejected 1. **Read the validation message:** Confirm whether it concerns word count, file type, or another field. A generation failure is not necessarily a source-length problem. 2. **Shorten deliberately:** Remove repetition first. If the document contains independent subjects, create separate sources that each make sense on their own. 3. **Submit the revised source:** Check the active workspace and use its current allowance. If a comfortably shorter source still fails, keep the error message and contact support. ## Preserve meaning when splitting content A setup tutorial should retain its prerequisites and working example. A product announcement should retain the limitations attached to its claims. Splitting either at an arbitrary word boundary can produce a draft that is shorter but misleading. For example, a release note covering three unrelated products may become three sources. Each should name its product, explain the change, include its relevant limitations, and link to the full release note. A single troubleshooting procedure usually needs its complete sequence in one source. ## Check destination versions separately Review generated articles and social posts for the destination’s format and length constraints. Shortening the source is not a substitute for reviewing an output. Keep the source URL or canonical attribution where appropriate, and confirm the selected channel’s publishing method. For allowance questions, contact the team with the workspace, approximate source length, and exact validation message. Do not include credentials or confidential source content in the support request. # AI credits URL: https://postrout.com/docs/ai-credits Category: Create Summary: Understand how generation consumes AI capacity and how to avoid unnecessary retries. Updated: 2026-09-17 ## Understanding ai credits For workspace owners and frequent publishers, the goal is to use available generation capacity intentionally. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - generating selected channels - retrying a failed destination - testing a revised Brand Voice ## AI credits procedure 1. **Define the ai credits outcome:** For workspace owners and frequent publishers, confirm that the intended result is to use available generation capacity intentionally. Record the owner and the decision this workflow should support. 2. **Prepare generating selected channels:** Use generating selected channels as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with retrying a failed destination:** Run a controlled draft, preview, or connection test using retrying a failed destination. Do not expose credentials or rely on an important publication as the first test. 4. **Verify testing a revised Brand Voice:** Review testing a revised Brand Voice against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals regenerating every channel after one edit. Track credits per approved campaign over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - regenerating every channel after one edit - using production credits for placeholder sources - confusing source limits with credit balances Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - credits per approved campaign - failed generation retries - remaining allowance # Brand Knowledge URL: https://postrout.com/docs/brand-knowledge Category: Brand system Summary: Store durable facts, positioning, products, audiences, and constraints for a Brand Profile. Updated: 2026-09-17 ## Understanding brand knowledge For brand managers and editors, the goal is to give generation reliable context without burying instructions in every source. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - product facts - audience problems - approved positioning ## Brand Knowledge procedure 1. **Define the brand knowledge outcome:** For brand managers and editors, confirm that the intended result is to give generation reliable context without burying instructions in every source. Record the owner and the decision this workflow should support. 2. **Prepare product facts:** Use product facts as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with audience problems:** Run a controlled draft, preview, or connection test using audience problems. Do not expose credentials or rely on an important publication as the first test. 4. **Verify approved positioning:** Review approved positioning against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals outdated claims. Track knowledge freshness over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - outdated claims - confidential operational data - contradictory records Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - knowledge freshness - factual corrections - records used per brand # Brand Assets URL: https://postrout.com/docs/brand-assets Category: Brand system Summary: Organize approved logos and reusable media with the Brand Profile identity that owns them. Updated: 2026-09-17 ## Understanding brand assets For multi-brand publishing teams, the goal is to make approved media easy to select without mixing brand ownership. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - primary logos - campaign graphics - approved product screenshots ## Brand Assets procedure 1. **Define the brand assets outcome:** For multi-brand publishing teams, confirm that the intended result is to make approved media easy to select without mixing brand ownership. Record the owner and the decision this workflow should support. 2. **Prepare primary logos:** Use primary logos as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with campaign graphics:** Run a controlled draft, preview, or connection test using campaign graphics. Do not expose credentials or rely on an important publication as the first test. 4. **Verify approved product screenshots:** Review approved product screenshots against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals unclear licensing. Track approved asset reuse over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - unclear licensing - obsolete brand marks - assets uploaded to the wrong profile Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - approved asset reuse - missing-media corrections - outdated assets removed # Channel permissions and credentials URL: https://postrout.com/docs/channel-permissions Category: Distribute Summary: Understand the minimum account authorization required for each publishing destination. Updated: 2026-09-17 ## Understanding channel permissions and credentials For channel owners and administrators, the goal is to connect the correct account with the least privilege needed to publish. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - OAuth scopes - API keys - publication identifiers ## Channel permissions and credentials procedure 1. **Define the channel permissions and credentials outcome:** For channel owners and administrators, confirm that the intended result is to connect the correct account with the least privilege needed to publish. Record the owner and the decision this workflow should support. 2. **Prepare OAuth scopes:** Use OAuth scopes as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with API keys:** Run a controlled draft, preview, or connection test using API keys. Do not expose credentials or rely on an important publication as the first test. 4. **Verify publication identifiers:** Review publication identifiers against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals shared personal credentials. Track healthy connections over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - shared personal credentials - excessive permissions - expired access discovered at publish time Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - healthy connections - reconnect frequency - authorization failures # Connect LinkedIn URL: https://postrout.com/docs/linkedin-connection Category: Distribute Summary: Authorize the intended LinkedIn identity and verify the available publishing format. Updated: 2026-09-17 ## Understanding connect linkedin For professional and company-page publishers, the goal is to connect the right LinkedIn account before approving posts or articles. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - personal posts - LinkedIn articles - organization publishing where permissions allow ## Connect LinkedIn procedure 1. **Define the connect linkedin outcome:** For professional and company-page publishers, confirm that the intended result is to connect the right LinkedIn account before approving posts or articles. Record the owner and the decision this workflow should support. 2. **Prepare personal posts:** Use personal posts as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with LinkedIn articles:** Run a controlled draft, preview, or connection test using LinkedIn articles. Do not expose credentials or rely on an important publication as the first test. 4. **Verify organization publishing where permissions allow:** Review organization publishing where permissions allow against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals authorizing the wrong profile. Track connection health over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - authorizing the wrong profile - missing organization permission - assuming every format uses the same limits Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - connection health - successful LinkedIn publications - permission-related failures # Connect X URL: https://postrout.com/docs/x-connection Category: Distribute Summary: Authorize the intended X account and prepare a reliable, reviewable thread-publishing workflow. Updated: 2026-09-17 ## Understanding connect x For teams distributing concise social versions, the goal is to connect an account with appropriate write and refresh permissions. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - single posts - multi-post threads - launch summaries ## Connect X procedure 1. **Define the connect x outcome:** For teams distributing concise social versions, confirm that the intended result is to connect an account with appropriate write and refresh permissions. Record the owner and the decision this workflow should support. 2. **Prepare single posts:** Use single posts as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with multi-post threads:** Run a controlled draft, preview, or connection test using multi-post threads. Do not expose credentials or rely on an important publication as the first test. 4. **Verify launch summaries:** Review launch summaries against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals expired tokens. Track thread success rate over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - expired tokens - thread order errors - publishing without checking current platform limits Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - thread success rate - reconnections - posts requiring manual correction # Connect DEV Community URL: https://postrout.com/docs/dev-community-connection Category: Distribute Summary: Configure a DEV API key and choose draft or public publishing behavior. Updated: 2026-09-17 ## Understanding connect dev community For technical writers and developer advocates, the goal is to publish accurate DEV editions with deliberate visibility and canonical settings. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - draft articles - public tutorials - canonical cross-posts ## Connect DEV Community procedure 1. **Define the connect dev community outcome:** For technical writers and developer advocates, confirm that the intended result is to publish accurate DEV editions with deliberate visibility and canonical settings. Record the owner and the decision this workflow should support. 2. **Prepare draft articles:** Use draft articles as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with public tutorials:** Run a controlled draft, preview, or connection test using public tutorials. Do not expose credentials or rely on an important publication as the first test. 4. **Verify canonical cross-posts:** Review canonical cross-posts against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals exposed API keys. Track successful DEV deliveries over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - exposed API keys - publishing publicly during a test - missing tags or canonical URL Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - successful DEV deliveries - draft-to-public conversions - connection failures # Connect Hashnode URL: https://postrout.com/docs/hashnode-connection Category: Distribute Summary: Add a Hashnode token and publication identifier for the intended developer blog. Updated: 2026-09-17 ## Understanding connect hashnode For teams publishing to a Hashnode publication, the goal is to route generated articles to the correct publication with valid credentials. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - publication ID - API token - article metadata ## Connect Hashnode procedure 1. **Define the connect hashnode outcome:** For teams publishing to a Hashnode publication, confirm that the intended result is to route generated articles to the correct publication with valid credentials. Record the owner and the decision this workflow should support. 2. **Prepare publication ID:** Use publication ID as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with API token:** Run a controlled draft, preview, or connection test using API token. Do not expose credentials or rely on an important publication as the first test. 4. **Verify article metadata:** Review article metadata against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals wrong publication selection. Track successful articles over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - wrong publication selection - expired token - missing canonical source Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - successful articles - publication-selection errors - credential rotations # Connect Reddit URL: https://postrout.com/docs/reddit-connection Category: Distribute Summary: Authorize Reddit and prepare submissions that respect subreddit context and rules. Updated: 2026-09-17 ## Understanding connect reddit For community-focused publishers, the goal is to combine working authorization with a human review of community fit. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - subreddit selection - title and body - link versus text submission ## Connect Reddit procedure 1. **Define the connect reddit outcome:** For community-focused publishers, confirm that the intended result is to combine working authorization with a human review of community fit. Record the owner and the decision this workflow should support. 2. **Prepare subreddit selection:** Use subreddit selection as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with title and body:** Run a controlled draft, preview, or connection test using title and body. Do not expose credentials or rely on an important publication as the first test. 4. **Verify link versus text submission:** Review link versus text submission against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals posting to the wrong community. Track submission success over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - posting to the wrong community - promotional framing - ignoring subreddit-specific restrictions Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - submission success - moderation removals - community engagement quality # Publish to Medium manually URL: https://postrout.com/docs/medium-manual-publishing Category: Distribute Summary: Generate a Medium-ready edition, publish it manually, and record the resulting URL. Updated: 2026-09-17 ## Understanding publish to medium manually For writers syndicating long-form articles to Medium, the goal is to keep Medium in the campaign even when new API connections are unavailable. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - copying the reviewed edition - setting source attribution - saving the published URL ## Publish to Medium manually procedure 1. **Define the publish to medium manually outcome:** For writers syndicating long-form articles to Medium, confirm that the intended result is to keep Medium in the campaign even when new API connections are unavailable. Record the owner and the decision this workflow should support. 2. **Prepare copying the reviewed edition:** Use copying the reviewed edition as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with setting source attribution:** Run a controlled draft, preview, or connection test using setting source attribution. Do not expose credentials or rely on an important publication as the first test. 4. **Verify saving the published URL:** Review saving the published URL against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals claiming automatic publishing. Track manual completion time over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - claiming automatic publishing - missing canonical settings - marking the channel complete before checking the article Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - manual completion time - saved Medium URLs - formatting corrections # Publishing statuses URL: https://postrout.com/docs/publishing-statuses Category: Distribute Summary: Interpret generated, approved, scheduled, publishing, published, partial, and failed states. Updated: 2026-09-17 ## Understanding publishing statuses For operators monitoring multi-channel campaigns, the goal is to respond to each destination independently without duplicating successful work. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - generated draft - approved version - partially published campaign ## Publishing statuses procedure 1. **Define the publishing statuses outcome:** For operators monitoring multi-channel campaigns, confirm that the intended result is to respond to each destination independently without duplicating successful work. Record the owner and the decision this workflow should support. 2. **Prepare generated draft:** Use generated draft as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with approved version:** Run a controlled draft, preview, or connection test using approved version. Do not expose credentials or rely on an important publication as the first test. 4. **Verify partially published campaign:** Review partially published campaign against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals retrying successful destinations. Track success by channel over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - retrying successful destinations - treating scheduled as published - ignoring remote verification Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - success by channel - partial failures - time spent in each state # Team roles and publishing ownership URL: https://postrout.com/docs/team-roles Category: Brand system Summary: Define who prepares, reviews, approves, connects, and publishes content. Updated: 2026-09-17 ## Understanding team roles and publishing ownership For collaborative workspaces, the goal is to reduce ambiguity without sharing credentials or bypassing review. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - writer - editor - brand owner ## Team roles and publishing ownership procedure 1. **Define the team roles and publishing ownership outcome:** For collaborative workspaces, confirm that the intended result is to reduce ambiguity without sharing credentials or bypassing review. Record the owner and the decision this workflow should support. 2. **Prepare writer:** Use writer as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with editor:** Run a controlled draft, preview, or connection test using editor. Do not expose credentials or rely on an important publication as the first test. 4. **Verify brand owner:** Review brand owner against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals unclear final approval. Track approval turnaround over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - unclear final approval - shared logins - cross-brand access beyond responsibility Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - approval turnaround - ownership escalations - access reviews # Billing and plans URL: https://postrout.com/docs/billing-and-plans Category: Help Summary: Understand plan allowances, usage, upgrades, and the capabilities available to a workspace. Updated: 2026-09-17 ## Understanding billing and plans For workspace owners, the goal is to match publishing volume and governance needs to the appropriate plan. Treat this as an operating workflow rather than a one-time configuration. Clear ownership, reviewed source material, and deliberate destination choices make the result safer and easier to repeat. PostRout keeps the source and its destination versions connected, but it does not replace judgment. Confirm facts, permissions, brand scope, account selection, and the remote result whenever the workflow can publish publicly. ## Prepare the required information Gather the material before changing settings or starting generation. Resolve missing facts and ownership questions at the source instead of expecting a later publishing step to correct them. - AI credit allowance - source-word limit - Studio and Custom Channel availability ## Billing and plans procedure 1. **Define the billing and plans outcome:** For workspace owners, confirm that the intended result is to match publishing volume and governance needs to the appropriate plan. Record the owner and the decision this workflow should support. 2. **Prepare AI credit allowance:** Use AI credit allowance as the primary test case. Verify its facts, permissions, terminology, links, and active workspace or Brand Profile before continuing. 3. **Test with source-word limit:** Run a controlled draft, preview, or connection test using source-word limit. Do not expose credentials or rely on an important publication as the first test. 4. **Verify Studio and Custom Channel availability:** Review Studio and Custom Channel availability against the source and confirm the account, formatting, links, media, status, and remote result where applicable. 5. **Record topic-specific corrections:** Update the workflow when review reveals assuming an upgrade changes past usage. Track allowance usage over subsequent uses to confirm that the correction helped. ## Risks and troubleshooting Most preventable failures come from incorrect scope, incomplete source information, stale authorization, or treating a generated draft as an approved publication. - assuming an upgrade changes past usage - confusing monthly allowance with per-source limits - making purchasing claims from outdated documentation Note: Never place passwords, API keys, OAuth tokens, private customer information, or unreleased confidential material in a source, template, Brand Voice, or public support request. ## Operational checks Measure whether the workflow improves quality and reliability, not only whether it increases output. Review the following signals over multiple campaigns and use them to refine the process. - allowance usage - upgrade events - billing support requests