Plan, review and publish social content

Take one post from an idea to a reviewed outcome#

Save the idea first, choose the actual destination, and review the exact text and link. Obtain the required approval before deliberately queuing or scheduling. Afterward, follow the original attempt and any later publication observation rather than assuming a calendar entry means a live post.

This app combines editorial work with a bounded Facebook Page connection. A manual channel supports planning and a clearly labelled record of work performed elsewhere; its name in the channel list does not make it an API connection.

1. Confirm the shared business and choose the working and approval arrangements.
2. Save a draft, with or without a destination where your scope permits.
3. Choose a Page or manual channel and preview the actual content.
4. Request review, address feedback and approve the saved revision.
5. Queue or schedule deliberately, or record an actual manual publication.
6. Follow the original outcome, handle uncertainty and preserve correction history.

Set the working arrangements for this business#

The current owner starts with the confirmed shared corporate business identity. Review the business country, timezone, content language, rights and personal-data arrangements, claims and disclosures, provider processing and review date. Correct an incorrect legal identity in Business setup rather than replacing it with a local channel label.

Choose managers or team working and owner or separate-approver review. Setup explains who may prepare and approve; it does not create a Meta account, pass App Review, grant a Page token or prove a post reached its audience.

Use the app without silently adding other services#

Social Publishing is a standalone corporate app. It uses the shared Business setup but does not require Email Marketing, SMS and WhatsApp, CRM or an Automation app. Installing it does not share another app’s contacts, credentials, consent or private records.

Local drafts can be prepared before provider readiness, including an unassigned draft where your scope allows. API publication additionally needs the supported business-country case, actual Page access, current source approval, publishing authority and available allowance. No dependency or provider account is installed automatically.

Review the actual business-country publishing case#

The first API cases cover ordinary owned-Page organic publishing by an Australian or New Zealand business. These are business-country controls. Page content can be seen globally; there is no domestic recipient-country pairing, recipient import or audience-location guarantee.

Other business countries retain local preparation and manual editorial work, with API publication unavailable until a supported case is implemented. Language, currency, IP location and a channel name do not select a legal country. Regulated claims, political or election advertising, paid targeting and specialist financial or health advice are outside this ordinary first scope.

A saved review or successful connection is not legal certification, Meta account approval or a promise of audience reach. Review the applicable obligations and the actual provider arrangements for your business.

Official references: ACCC: social media promotions ↗ · New Zealand Commerce Commission: business obligations ↗

Check the rights, claims and disclosures in the actual post#

Before approval, confirm that the business may publish the words, linked material and any identifiable story or testimonial. Check factual claims, endorsements, required disclosures and the destination. A preview cannot establish copyright permission, a person’s authority or the truth of a promotion.

Record a meaningful current setup review and revisit it when the purpose or arrangements change. This app does not automatically assess regulated content or turn an owner’s confirmation into a legal opinion.

Keep public content and personal information proportionate#

Treat publication as disclosure to a public platform whose audience, processing and retention may extend beyond your country. Review whether identifiable information belongs in the post at all. The app does not collect followers, commenters, direct messages or engagement profiles, and public visibility does not establish permission to reuse a person’s information.

Keep local descriptions and review comments limited to what the work needs. Local redaction cannot recall copies held by Meta, other people, caches or screenshots. There is no universal retention period for every post; review the applicable purpose and retention obligations.

Official references: OAIC: overseas disclosure ↗ · OAIC: security and disposal ↗ · New Zealand: retention principle ↗ · New Zealand: indirect collection notification ↗

Grant each job explicitly within its channel scope#

The owner chooses workspace-wide or selected-channel scope and the actual permissions: view posts, prepare posts, approve posts, publish posts, manage schedules, record manual publication, view safe channel state and export posts. Select required prerequisites deliberately; the interface does not add permissions silently.

Preparing, approving, publishing, recording manual publication and exporting each require post viewing. Managing schedules also requires publishing. Safe channel-state viewing is independent and exposes only permitted labels and readiness reasons, not owner-only account proof or credentials. An administrator title alone supplies no implicit Social grant or secret access.

Viewers can receive post viewing, safe channel-state viewing and explicit export, never write permissions. Revocation, membership changes and app reinstall end the corresponding old authority. The owner reviews the actual current member before a new grant; missing private counts mean unavailable, not zero.

Choose one actual destination for each post#

A channel represents either one explicitly configured Facebook Page or a manual editorial destination. Give it a useful label that distinguishes the business account and intended use. One post targets one channel; publishing to another channel requires a deliberate independent draft and review.

Choose only a current destination offered within your authority. A familiar name, public profile URL or similar account does not prove ownership. An unavailable channel can still be useful for permitted preparation, but cannot be treated as ready for API publication.

Plan editorial work for other platforms truthfully#

Use a manual channel for destinations such as Instagram, LinkedIn, X, Bluesky, YouTube, TikTok or Mastodon when the API connection is unavailable here. Save the platform, a readable label and the actual profile URL. The URL is an ordinary external link, not a connection test or imported account proof.

The first scope does not upload media, publish to personal profiles or groups, manage ads, read comments or direct messages, scrape audiences or provide social listening. A manual record remains manual even when its URL opens a real public post.

Save Page credentials without putting them in ordinary history#

The current owner enters the exact Meta app ID, Page ID, Page access token and app secret for the supported connection. Complete any required provider setup and access approval in Meta’s own tools. This release does not provide automatic OAuth onboarding, Page discovery through a copied user token or automatic token renewal.

Secrets are write-only and clear after dispatch. For an existing Page connection, deliberately keep stored credentials or enter an explicit replacement for that same account. The app and Page identity stay fixed; another app or Page needs a new channel so original attempts retain their true destination.

If the acknowledgement is missing, check the original save receipt first. Cleared secrets cannot be reconstructed from a masked page or replaced with placeholder text. Do not paste a bearer token, app secret or full provider response into notes, screenshots or a support message.

Request a current read-only Page connection check#

Review the current connection-check request and follow its original task. The check observes the subject Page token’s actual identity and supported access; it does not publish a test post. Saved configuration, a queued check, observed proof and unavailable proof are separate states.

Read the observation time and reason. A configured ID echoed in a form, a public Page that anyone can read or a locally saved label cannot establish the identity of the token. Missing required facts keep publishing unavailable; no successful outcome is invented while a task is waiting.

Understand the Page identity and access facts#

Check that the observed Page matches the selected Page and that the token belongs to the configured app. The supported Page access needs the actual pages_manage_posts and pages_read_engagement grants for that selected Page. Token validity alone does not prove all of those facts, and an unfamiliar task label is not silently translated into equivalent permission.

Expiry and data-access expiry are separate provider facts. A missing expiry is not interpreted as unlimited access. Account restrictions, app mode and actual customer access approval remain separate from the local connection implementation. Current proof is rechecked before a new publication starts; old proof or another Page’s permission does not transfer.

Official references: Meta: official token diagnostic source ↗ · Meta: official Page field and edge source ↗

Save a useful draft before the destination is ready#

Start with a title and original text. The owner or a person with workspace preparation scope can leave the destination unassigned. An author limited to selected channels chooses one of their actual saved channels, including an unready channel, rather than creating work outside that scope.

A draft does not create approval or publication work. Later selection of a channel, replacement of content or change of source needs a fresh save and review. Each save preserves the original wording and a new revision; another person’s current change is not silently overwritten.

Write the original text that will be published#

Enter the actual post text, including the intended punctuation and line breaks. This release supports organic text with one optional explicit HTTPS link for the Page API. It has no media upload, raw HTML, automatic template expansion, recursive variables or generated promotional claims.

The initial local limits are a 200-character title and 10,000-character text, measured as Unicode characters. These are Emnaro controls, not a statement of Meta’s maximum post length. Validate the actual destination and wording through the current preview and review.

Review one explicit HTTPS link as post content#

Use the intended HTTPS destination without embedded credentials or control characters. The local URL limit is 2,048 bytes. The entered link becomes post content; it is not an address where Emnaro may send provider credentials.

Emnaro does not fetch an external article or image preview for this workflow. Inspect the displayed host and open the destination deliberately when needed. A readable preview does not certify the linked site, and no automatic substitute URL is selected if the link is unavailable.

Preserve the saved language and direction independently#

Choose the saved content language and its intended left-to-right or right-to-left direction explicitly. They are independent choices. Arabic text can retain an explicitly chosen left-to-right document direction; the interface does not rewrite the original because of its language.

Changing interface preferences does not translate saved copy, legal review or feedback and does not choose a business country. Check mixed-direction Page IDs, dates and URLs in the actual preview. No English fallback is published in place of an unavailable translation.

Organise the portfolio without changing publication authority#

Use short labels to group a campaign, purpose or editorial stream. Filter the post portfolio and calendar by the current channel, state and label to find both undated drafts and scheduled work.

The first local allowance is 20 labels per post, each up to 60 Unicode characters. A label does not grant channel access, create an audience, select a country or authorise a publication.

Inspect an inert preview of the saved revision#

Open the preview after saving. Check the original text, link, language, direction, destination and validation messages. Preview reads the existing saved revision; opening it does not approve, publish or create a provider task.

Preview links are inert and external assets are not fetched. The presentation helps review the content supported by this app; it does not promise Facebook’s final layout, link card, moderation, audience reach or continued visibility.

Review the exact destination and saved source#

The current review brings together the saved revision, actual destination, country case, connection facts, approval arrangement and currently allowed actions. Resolve each unavailable reason rather than assuming that a previous check still applies.

Content, destination, business review, approval policy, credentials or current authority can change after a page was opened. Reload the current source and review again when it is stale. A read of the review or preview never creates an approval by itself.

Keep preparation, approval and publication separate#

Request review for the actual saved revision and let the authorised reviewer inspect its original text, destination and current setup. Approval requires the configured policy and a deliberate confirmation that rights and claims were reviewed.

With separate approval, both the original creator and latest content editor are excluded from approving, including an owner who performed either job. Use another current authorised reviewer. The original preparer and approver labels remain attached to the history; approval does not automatically queue or schedule a post.

Return clear feedback and review the corrected revision#

Use Request changes with a concrete comment about the selected revision. Authors can read the recorded feedback before any publication attempt exists. Review history distinguishes a review request, changes requested, approval and an invalidated approval.

Save the correction deliberately and request a fresh review. A changed title, text, link, channel or relevant setup cannot borrow the old approval. Review comments have a local 2,000-character limit; do not include credentials or unnecessary personal information.

Use the calendar alongside undated editorial work#

The calendar groups current authorised posts by the selected month and date, with filters and visible counts. Undated drafts remain discoverable separately; putting an idea in the portfolio does not assign a publication time.

Open the relevant current post to inspect its review and original attempt. Where a day has more records than its preview, use the offered page or more-records action. A calendar card is a local plan, not evidence of remote publication.

Resolve the intended local time and daylight-saving offset#

Review the selected wall time, IANA timezone, resolved UTC instant and chosen signed UTC offset together. A nonexistent daylight-saving time is rejected. When a local time occurs twice, deliberately choose the intended occurrence rather than accepting a hidden default.

Scheduling creates the local plan for one approved original. It does not delegate scheduling to Facebook. Current source and authority still apply when work becomes due. An overdue unapproved, cancelled or expired item is not automatically made publishable.

Queue one approved original deliberately#

After approval, open the current review and deliberately queue or schedule. Queuing binds the approved revision, destination and current authority to one original publication attempt. A waiting or prepared task is not a published post.

Current membership, channel scope, setup, rights review, country case, Page access and allowance are checked again before publication starts. A stale source is blocked rather than silently changed. There is no automatic cross-post to other channels or fallback to a manual publication record.

Follow local processing without confusing it with visibility#

Read the post’s original attempts and safe reasons: queued, prepared, started, accepted, rejected, not submitted, skipped, cancelled or unknown. Each describes that original operation; later read observations are separate facts.

Completed means no pending local publication work remains. It does not certify that Meta displayed the content, approved its claims or continued to make it available. Missing permission or private counts stay unavailable instead of appearing as zero.

Distinguish provider acceptance from an observed live post#

Provider accepted means a complete supported response established the original post reference. It is not a promise of moderation approval, visibility, reach, engagement or delivery to particular viewers.

A later authorised read may observe the exact post as published, not published, unavailable or conflicting. Keep that observation time and its meaning beside the original submission outcome. A manually entered URL cannot turn a failed or unknown API attempt into provider acceptance.

Read only the retained exact original provider post#

When the current action is available, request a read of the original known Page post. This is a separate read task, not another publish attempt. It needs the correct original reference, current permitted account access and an exact Page match.

A permission error or missing response is unavailable, not proof of remote deletion. A content comparison is shown only when the provider actually returned the required exact fields. Missing text or link coverage is unknown; the app does not search the Page feed for a similar post to recover an uncertain write.

Protect an uncertain original from another copy#

Unknown means the original write may have reached the provider without a trustworthy complete acknowledgement. Keep its original reference and current history. Do not infer failure from a missing post ID, an empty receipt, a timeout or a later unavailable read.

The app does not automatically resend an unknown original. Later exact-ID evidence can corroborate it but cannot rewrite the original uncertainty or authorise another copy. Use the offered investigation workflow and current account evidence; neither a manual URL nor a local note resolves the native outcome.

Check the original operation before repeating an action#

If a command loses its acknowledgement, keep the entered state and use Check original request with the exact saved operation reference. Controls remain locked while the original is pending or unknown. A completed receipt must identify that original action and result before the page moves on.

There is no automatic new request ID or reconstructed retry. An explicit original replay is possible only if the exact original body remains held and the server permits it. Cleared secret inputs cannot be recreated from a masked connection page; checking the receipt comes first. Never store secret bodies or capability URLs in ordinary notes or browser history.

Make a fresh draft instead of rewriting publication history#

An unqueued editable draft can be corrected through a new save and review. Once original work has been queued, started, completed or become uncertain, retain that history. Deliberate duplication creates an independent draft for the selected destination and needs its own review and approval.

Remote edit and delete are unavailable in this first scope. Make any necessary change at the platform under your own current authority, then use an available original read to understand what was actually observed. Local redaction is a different action and does not claim a provider edit or deletion.

Record only work actually published outside the API#

For a manual editorial channel, publish in the chosen platform yourself, then record the actual public URL, publication time, reference and a proportionate note through the reviewed manual action. A scheduled editorial plan does not perform that external step.

The result is labelled manual record only, with the recorder and recorded time. It is not API acceptance or independent verification of the URL, account ownership or continued availability. No automatic manual record is created when an API attempt is rejected or unknown.

Pause, resume or cancel only the appropriate original work#

Pause can hold still-pending local publication work. Review the current resume action before continuing; it rechecks the original approval and sources. Cancellation ends eligible pending work and preserves its history. Neither action recalls a post already sent to the provider.

A reviewed reschedule applies only to the existing unstarted plan and requires scheduling and publishing authority. Inspect both prior and new times. Started, terminal, skipped or cancelled originals cannot be revived or moved into a new attempt by changing a date. Content or destination changes require a fresh draft.

Retry only a clear supported failure with current review#

A deliberate retry is offered only for an eligible known failure where the original did not create an accepted remote resource. Current source, approval, country, permissions and allowance are checked again. Unknown, accepted and ambiguous originals do not qualify.

The local cap is three attempts for one approved post: the original plus at most two deliberate known-failure replacements. This is not an automatic retry queue. Check the original receipt first, retain the earlier attempt and read the actual unavailable reason when another attempt is blocked.

Preview a draft-only CSV before committing it#

Download the current sample and use its exact columns: title, channel_id, text, link, language, direction and labels. The first scope accepts up to 500 draft rows in a 5 MiB file. An unassigned channel is allowed only where current workspace preparation authority permits it.

Inspect the original cells, selected destinations, row errors and any explicitly described spreadsheet prefix normalization. Ordinary mentions and legitimate leading apostrophes are not silently discarded. An invalid preview cannot commit; a valid preview still creates only drafts, with no approval, schedule or publication result.

A preview lasts 30 minutes and is bound to the current source and authority. Commit the exact reviewed preview with its original request. After an uncertain commit, check its receipt rather than uploading another file as a replacement for the unresolved original. No automatic translation or truncated first-page import is performed.

Download the permitted portfolio in explicit segments#

Export requires explicit post viewing and export permission for the current channel scope. The export distinguishes approved local content, original provider outcomes, later observations and manual provenance; it includes no credentials or raw provider errors.

Each download is a segment of up to 500 rows. Read the actual complete or next-segment indication and deliberately continue while the current cursor remains valid. The first 500 rows are not presented as the entire portfolio. Keep downloaded personal or confidential content under your own access and retention controls.

Read local allowances separately from provider limits#

Initial local controls allow up to 10 channels, of which at most five are API channels, 10,000 posts, 100 starts per UTC day, 1,000 aggregate unstarted reservations and one active publication operation per workspace. Current screens show the applicable used and maximum values where your authority allows.

These limits do not buy Meta access, reserve provider capacity or guarantee publishing speed. Storage and current subscription or licence also matter. Queued work and retained history count according to their actual purpose; a quota does not erase originals or convert an uncertain attempt into a new allowance.

Read review, attempt and manual histories independently#

Use the original post detail to follow versioned review comments, publication attempts, manual records and later provider observations. Their pages are independent so moving through one history does not silently skip another.

Attribution and original outcomes are retained even when a person’s current role changes. Current permission still governs what may be opened now. A historical actor label is evidence of a past action, not a present grant.

Remove local content without promising remote erasure#

Review the exact scope before redacting a post copy. The action cancels eligible pending work and erases the protected local content and prepared copies covered by that decision, while retaining minimal original outcome, attribution and receipt metadata.

It does not delete the post at Meta, erase other people’s shares or revoke provider credentials. A removed local copy is not reconstructed from a later provider read or a retained preview. Handle any required provider-side removal separately under the current provider controls.

Use retained owner recovery for protection and original readback#

After the app is disabled, the current original owner can use the dedicated retained recovery area to inspect permitted original records and receipts, pause or cancel eligible pending work, erase local copies or secrets and download permitted retained metadata.

Recovery cannot approve, queue, resume, retry, record a new manual publication or request a fresh account probe. Removing local secrets does not revoke a token at Meta. Reinstalling does not revive old staff grants, expired authority or terminal original work; current setup and permissions must be reviewed deliberately.

Keep simulated publication inside the normal Demo lifetime#

Demo follows the same preparation, review, scheduling and outcome workflows with explicitly simulated provider work. Use its actual offered simulation and private original documents; do not paste real production tokens or publish to a real Page to complete a Demo step.

Simulated acceptance, a Demo preview or a synthetic public link does not establish a production Page connection, real publication or provider approval. The normal configured Demo lifetime starts through the platform’s ordinary provisioning flow, defaults to 180 minutes and ends access at expiry. Installing or reinstalling this app does not extend it.

Choose the next action from the original current state#

For a saved draft with no publishing action, check the selected destination, supported country case, current setup, required approval and actual Page proof. For a stale review, reload the source and review the changed revision. For waiting work, inspect its original task and due time rather than creating a second post.

For a missing acknowledgement, check the original operation receipt. For unknown publication, investigate that original and avoid another copy. For an unavailable read, retain the distinction between missing evidence and confirmed deletion. If access was removed or Demo expired, the interface cannot restore it through a retry or another browser tab.