Correct account
Content must belong to the selected connected account.
Elaryx Smart Scheduling organizes eligible, approved posts in a LinkedIn content calendar with date, time, timezone and publishing-status controls. When a supported LinkedIn account and required permissions are available, scheduled content can move through the configured publishing workflow.
Approval-aware · Timezone-visible · Rescheduling control
Scheduling should explain why a post can or cannot enter the queue.
Content must belong to the selected connected account.
Copy and media rules must be satisfied where configured.
Review or approval may be required before scheduling.
Connection, queue and plan limits can affect availability.
The calendar should show account timezone, local preview and scheduled timestamp clearly so users understand when content will publish.
Show the timezone used by the schedule.
Keep storage and conversion behavior consistent with implementation.
Explain what changes and what stays fixed.
Treat recommendations as guidance, not guaranteed reach.
Use clear statuses so users know the next supported action.
Content is not ready for publishing.
A user needs to approve or adjust the post.
A valid date and time have been assigned.
Show a user-safe reason and recovery path when publishing fails.
Common causes include expired connections, missing permissions, provider rejection, invalid media or temporary processing errors. Never expose raw tokens or sensitive provider responses.
Smart Scheduling works best when the user can see what goes in, what Elaryx produces and where human review remains required.
Keep a manageable posting rhythm.
Separate review, approval and publishing.
Avoid scheduling to the wrong client account.
Keep campaign cadence visible.
It organizes planned or approved posts by date and status so users can see the publishing rhythm, identify gaps and manage upcoming content.
Requirements can include an approved post, a supported connected LinkedIn account, the necessary permissions, valid media and compliance with plan or queue limits.
The product should display the account timezone and the scheduled time clearly. Exact storage and conversion behavior must match the implementation and be tested around timezone changes.
No. Elaryx may offer timing guidance when that feature is enabled, but recommendations cannot guarantee reach or engagement.
Elaryx should show a clear failure state, a user-safe reason when available and the next supported action, such as reconnecting the account, correcting the post or retrying.
Review readiness, confirm timing and follow publishing status from one calendar.