Schedule LinkedIn, on autopilot.

Every native LinkedIn post type.

BAT does not flatten LinkedIn into a single text box. It schedules and publishes the formats LinkedIn actually rewards: text, single image, document/PDF carousel, video, article, poll.

How the scheduled-publish worker works.

A LinkedIn scheduler is only as good as the thing that fires the post when the clock hits. BAT runs a background worker so a queued post goes out whether or not anyone has the app open.

• Queue a post for a time. An approved LinkedIn post lands in the schedule with a target time, in its native format (a document carousel, a poll, an article, a video, an image, or text).
• The worker claims it atomically. When the post is due, the worker atomically claims it before publishing. That claim is what prevents a retry or a race from posting the same thing to LinkedIn twice.
• It fires through LinkedIn's real API. LinkedIn has its own OAuth connection and publisher code in BAT, so the post goes out through the network's real API, not a lowest-common-denominator bridge that strips native formatting.
• Status flows back to one calendar. Scheduled, published, and failed posts all land on a single calendar that spans every connected platform, so LinkedIn sits next to the rest of your week in one view.

AI send times from your own LinkedIn history.

BAT does not guess at generic best times. It reads your own engagement-by-hour history and suggests when to post, falling back to a platform-canonical default only when there is not enough of your own data yet.

Review before it ships, not after.

Scheduling without review is how the wrong draft goes live on a company page. BAT puts a real approval gate in front of the scheduler, so only signed-off LinkedIn posts ever reach the worker.

• Post drafts move DRAFT → PENDING_REVIEW → APPROVED/REJECTED, with rejection notes and resubmit; approved posts go to the scheduler.
• Five brand roles (Owner, Admin, Manager, Creator, Member) with a fine-grained capability matrix.
• Role hierarchy with privilege-escalation guards: you can only grant roles below your own.

LinkedIn is also BAT's deepest analytics surface.

Scheduling and measurement live in the same workspace. LinkedIn carries the richest, first-party analytics of any network in BAT, so you can schedule against what actually performed.

LinkedIn is one of eight networks.

Schedule LinkedIn alongside Instagram, Facebook, X, TikTok, YouTube, Threads, and Pinterest, each with its own connection and native post types. Plan one idea and let it fan out across all 8.

One idea, eight platforms.

A LinkedIn document deck rarely belongs only on LinkedIn. BAT drafts from one brand brain, then adapts a single idea into each network's native format, so the LinkedIn scheduler is one face of a whole social workflow.

Where this is honest about the limits.

Publishing to LinkedIn needs the LinkedIn app credentials configured for your workspace. Each platform needs its own app credentials configured; Pinterest in particular is pending app approval.

There is no post-publish recall. Approval and cancellation happen before a LinkedIn post goes live, never after. If you need to stop something, you stop it in review, not by pulling it back once it is on the feed.

LinkedIn analytics can run on imported datasets, so reported numbers are not always live first-party API data. BAT is explicit about which view you are looking at rather than implying everything is real-time.

Frequently asked questions.