Responsible scheduling
Avoid repetitive or spam-like posting, bulk publication of identical content, and automation patterns that could put your accounts or Syncra's provider access at risk.
Help Center
Task-based support for troubleshooting, recovery, and escalation.
Quick Actions
Fast routes for common operational tasks.
Home Dashboard
Daily control center with account health, pending work, and next actions.
Onboarding
Guided setup for workspace identity, timezone, and first provider connections.
Posts
Create, edit, filter, and recover post delivery across all connected channels.
Approvals
Decision queue for approve/reject cycles with role-aware communication channels.
Integrations
Provider account connections, reconnection flows, and permission recovery controls.
Reports
Client-ready reporting workspace with snapshots, layout editing, and share links.
Profile & Personal Settings
User-level identity and preferences, including profile details and account linking context.
Feedback
In-app feedback submission channel for product issues, suggestions, and UX friction.
Popular Questions
Answers to frequent product and workflow questions.
Approved posts are not automatically scheduled. Move them to Scheduled from Calendar or post actions.
Approver, Admin, and Owner can approve and publish. Creator can draft and submit; Viewer is read-only.
Open the post, read the failure reason, reconnect the affected account in Integrations, and retry from Posts or Calendar.
After OAuth callback, choose the desired account in the selection step before finalizing connection.
AI Studio is gated by plan feature and role capability. Team/Studio plans with creation permission can access it.
In Report Builder, create a share link, optionally set expiry, and revoke links any time from the same panel.
Planning article
Fair use policy for social media scheduling
Team and Studio plans include unlimited monthly scheduled posts when scheduling follows responsible usage, platform rules, and Syncra account-protection limits.
Content standards
Do not schedule illegal, hateful, abusive, deceptive, explicit sexual, or regulated-content advertising that violates platform rules or applicable law.
Platform enforcement
Syncra may pause or block scheduling when usage appears unsafe, violates provider policies, or risks account suspension. Platform-imposed limits are outside Syncra's control.
Scheduling window
Posts can be scheduled up to 30 days ahead so Syncra can reliably queue publication through supported provider and infrastructure limits.
Onboarding Recovery
Use the matching path below when onboarding is blocked by workspace setup, billing confirmation, or social account connection.
A workspace is a separate environment in Syncra. It keeps billing, permissions, connected accounts, assets, and reporting organized together.
One login can belong to multiple workspaces, so use a new workspace only when you need separate billing, separate permissions, separate assets, or a cleaner client boundary.
Workspace is still syncing
Your workspace was created, but Syncra has not finished loading it into the app yet.
- Wait a few seconds, then retry loading onboarding.
- Hard refresh if the workspace step still shows an outdated state.
- Contact support if the workspace does not appear after a short wait.
Trial or billing is not active yet
Checkout may be complete, but Syncra is still waiting for Polar to confirm the trial state.
- Return to onboarding and refresh billing status once.
- If you already finished checkout, give webhook sync a short moment to complete.
- Open billing recovery if the workspace still shows inactive or past due.
Social account connection did not complete
A provider callback or account-selection step was interrupted before the connection was finalized.
- Retry the provider connection and complete any account selection step.
- Verify your browser is not blocking the callback redirect.
- Reconnect from Integrations if onboarding dropped you out of the flow.
Troubleshooting Playbooks
Follow these checks first to resolve most day-to-day issues quickly.
Profile & Personal Settings
User troubleshooting
Profile updates do not persist.
- Retry save after re-authentication.
- Confirm browser session is still valid.
- Check if identity provider controls locked fields.
/app/settings/profile
Feedback
User troubleshooting
Feedback submission appears to fail silently.
- Confirm required fields are complete.
- Retry submission with stable network.
- Use support contact if confirmation never appears.
/app/feedback
Posts
User troubleshooting
Post remains failed after retry.
- Inspect failure reason in post detail.
- Reconnect affected provider account.
- Retry from post actions after permissions are restored.
/app/settings/integrations
Integrations
User troubleshooting
Publishing fails due to provider authorization.
- Reconnect account and grant all required scopes.
- Remove stale disconnected connection entries.
- Retry failed post after reconnection.
/app/posts
Reports
User troubleshooting
Share link or snapshot output is outdated.
- Open report builder and regenerate snapshot.
- Verify link token is active and not revoked.
- Create a new link when access scope changed.
/app/reports
Data Export
User troubleshooting
Export job remains pending or failed.
- Retry with narrower dataset scope.
- Delete stale failed requests and re-run.
- Check workspace permissions for export access.
/app/settings/data-export
Admin Operations Playbooks
Dedicated queue-management playbooks for administrative feedback and contact intake.
Admin Feedback Queue
Admin operation
Queue grows without clear ownership.
- Apply triage labels for severity and area.
- Assign accountable owner per item.
- Escalate platform-impacting issues immediately.
/app/admin/feedback
Admin Contact Queue
Admin operation
Critical contact requests are missed.
- Sort by newest and unresolved first.
- Flag high-impact incidents for immediate escalation.
- Track resolution notes before closure.
/app/admin/contact
Before You Contact Support
Provide this context so support can reproduce and resolve faster.
- Workspace name and affected module (Posts, Approvals, Reports, etc.).
- Exact route where issue happened and timestamp/timezone.
- Post/report/export IDs involved, when available.
- Error message text and what changed immediately before the issue.
- Screenshots or short recording for UI-level problems.
Feature-specific context examples
- Onboarding: Include provider, callback time, and whether account selection completed.
- Admin feedback queue: Include queue item ID, severity label, and ownership status.
- Admin contact queue: Include contact submission ID, customer impact, and current SLA state.