Where does this permissions list come from?

From the same registry (PLATFORM_CAPABILITIES.oauthScopes, mirrored on the per-platform integration pages) that builds the actual consent screen you see when connecting an account — it is drift-tested against the live connect flow, not typed by hand.

Does SkedCast ever request a permission not listed here?

No — a dedicated test locks this disclosure to exactly what the connect flow requests, in both directions, so nothing here is unrequested and nothing requested is left off.

Why do some platforms need more permissions than others?

It depends on what SkedCast does for that platform — publishing alone needs fewer scopes than publishing plus reading back analytics plus posting an optional first comment.

Do all 10 platforms use OAuth?

No — 8 platforms use OAuth; Bluesky uses an app password and Telegram uses a bot token, and both are disclosed here using the credential they actually use.

Can I revoke a permission after connecting?

Yes — disconnecting the account in SkedCast removes its stored tokens or credential, and you can also revoke access from the platform’s own app-permissions settings.

Is this the same list as the per-platform integration pages?

Yes — this page shows every platform’s permissions together in one place, while each platform’s own integration page shows the same list alongside its full feature detail.

Free tool

Instagram API permissions, and every other platform's

Instagram API permissions, and every other platform’s: exactly which OAuth scopes (or credential, for the two platforms that don’t use OAuth) SkedCast requests when you connect each of the 10 platforms, and a plain-English reason for every one — pulled directly from the same registry that builds the live consent screen, so this page can never advertise a permission the connect flow does not actually ask for.

Instagram API permissions and 9 more platforms

X (Twitter)

tweet.write: Publish the posts and threads you schedule to your X account.
media.write: Upload the images, GIFs and videos attached to those posts.
tweet.read: Read back the posts SkedCast published so your analytics are accurate — and so a post that X reports ambiguously is never published twice.
users.read: Read your basic account info to confirm the connected account and label it in your dashboard.
offline.access: Keep the connection alive (refresh tokens) so scheduled posts publish without re-authorizing.

Full X (Twitter) integration detail

w_member_social: Publish posts to your personal profile or the Company Pages you administer.
openid: Sign you in via LinkedIn to confirm the connected member.
profile: Read your basic profile (name, picture) to label the connected account.
email: Read the email on your LinkedIn account so the connected member can be matched to your SkedCast login.

Full LinkedIn integration detail

Instagram

instagram_business_basic: Read your professional account’s basic profile to confirm and label the connected account.
instagram_business_content_publish: Publish the feed posts, carousels, and Reels you schedule to your Instagram account.
instagram_business_manage_insights: Read the insights (reach, impressions, saves) for the posts SkedCast published so the analytics you see are accurate.
instagram_business_manage_comments: Post the optional first comment you add to a scheduled post (only if you use it).

Full Instagram integration detail

Facebook

pages_show_list: List the Facebook Pages you administer so you can pick which of them to connect.
pages_manage_posts: Create and publish the posts you schedule to the Facebook Pages you manage.
pages_read_engagement: Read your Pages and their basic engagement so we can list them and report performance.
business_management: Confirm the Pages you administer through Business Manager so we connect the right assets.
read_insights: Read your Page insights (reach, impressions, engagement) so the analytics for the posts SkedCast published are accurate.

Full Facebook integration detail

TikTok

video.publish: Upload and publish the videos and photo posts you schedule, with the disclosures TikTok requires.
user.info.basic: Read your basic creator info to confirm the connected account and label it in your dashboard.
user.info.stats: Read your follower and total-likes counts so SkedCast can show TikTok account analytics on your dashboard.
user.info.profile: Read your @username, bio and verified badge so the connected account is labelled the way TikTok shows it.
video.list: Read the view, like, comment, and share counts on your published videos so TikTok analytics for posts SkedCast published are accurate.

Full TikTok integration detail

YouTube

https://www.googleapis.com/auth/youtube: Upload, schedule, and manage videos on the YouTube channel you connect.
https://www.googleapis.com/auth/userinfo.email: Read the connected Google account’s email to identify which login a channel belongs to.

Full YouTube integration detail

Threads

threads_basic: Read your basic Threads profile to confirm and label the connected account.
threads_content_publish: Publish the text and media posts you schedule to Threads.
threads_manage_insights: Read the insights for the Threads posts SkedCast published so the analytics you see are accurate.

Full Threads integration detail

pins:write: Create the Pins you schedule on the boards you choose.
boards:write: Required by Pinterest to create a Pin at all — a Pin is created onto one of your boards.
boards:read: Read your boards so you can pick where each Pin is published.
pins:read: Read back the Pins SkedCast created so your Pin analytics (impressions, clicks, saves) are accurate.
user_accounts:read: Read your basic account info to confirm the connected account, label it in your dashboard, and report your account analytics.

Full Pinterest integration detail

Bluesky

App password (AT Protocol): Bluesky uses an app password rather than OAuth scopes. The app-password session lets us create posts on your behalf; it is stored encrypted and erased on disconnect.

Full Bluesky integration detail

Bot token (Telegram Bot API): Telegram uses a bot token rather than OAuth scopes. The token lets SkedCast post to the channel where your bot is an administrator and read its member count; it is stored encrypted and erased when you disconnect.

Full Telegram integration detail

How to read the permissions list

Find your platform. Each of the 10 platforms has its own section listing exactly what it requests to connect.
Read the scope and its purpose. Every permission is paired with a plain-English reason SkedCast needs it — publishing, reading back analytics, or confirming the connected account.
Check the connection method. Most platforms use OAuth; Bluesky uses an app password and Telegram uses a bot token instead — both are named here, not hidden behind an "OAuth scopes" label that would not apply.
Compare against what you see at connect time. The consent screen you see when connecting a platform asks for exactly this list — nothing more, nothing less.
Check the connection matrix for the bigger picture. The platform connection & feature support matrix shows the connection method and account type required for every platform at a glance.

Worked examples

Why Instagram asks for four permissions

The 4 scopes split cleanly: instagram_business_basic confirms the account, instagram_business_content_publish publishes scheduled posts, instagram_business_manage_insights reads back analytics, and instagram_business_manage_comments only applies if you use the optional first-comment feature.

A credential instead of OAuth scopes

The other 2 of the 10 platforms skip OAuth entirely — Bluesky connects with an app password and Telegram with a bot token, both stored encrypted and erased on disconnect, which this page states plainly instead of forcing them into an OAuth-scope format that would not fit.

Platform permissions FAQ

Where does this permissions list come from?: From the same registry (PLATFORM_CAPABILITIES.oauthScopes, mirrored on the per-platform integration pages) that builds the actual consent screen you see when connecting an account — it is drift-tested against the live connect flow, not typed by hand.
Does SkedCast ever request a permission not listed here?: No — a dedicated test locks this disclosure to exactly what the connect flow requests, in both directions, so nothing here is unrequested and nothing requested is left off.
Why do some platforms need more permissions than others?: It depends on what SkedCast does for that platform — publishing alone needs fewer scopes than publishing plus reading back analytics plus posting an optional first comment.
Do all 10 platforms use OAuth?: No — 8 platforms use OAuth; Bluesky uses an app password and Telegram uses a bot token, and both are disclosed here using the credential they actually use.
Can I revoke a permission after connecting?: Yes — disconnecting the account in SkedCast removes its stored tokens or credential, and you can also revoke access from the platform’s own app-permissions settings.
Is this the same list as the per-platform integration pages?: Yes — this page shows every platform’s permissions together in one place, while each platform’s own integration page shows the same list alongside its full feature detail.

Ready to broadcast everywhere?

Sign up free — no credit card. You land on the Free plan, and you can start a one-time 7-day Studio trial from your workspace whenever you are ready. Connect your first accounts, import a batch, and watch one post fan out across every platform.

Start free Log in to your console