How to Enable Social Networks in Stackposts v9 (Admin & Plans Guide)
Use this owner guide to configure the workspace and confirm the customer-facing result.
Use this guide
- Open the owner area and confirm that you have the required permission.
- Apply the settings described below and save the change.
- Check one customer-facing workflow before rolling the change out.
Detailed steps
Step 1: Enable Social Networks & Configure APIs in Admin Panel
Go to:
For each social network, you must:
1️⃣ Enable the Network
-
Toggle Enable / Active status to ON
2️⃣ Configure API Credentials
Each social network requires valid API information, for example:
| Social Network | Required Configuration |
|---|---|
| Facebook / Instagram | App ID, App Secret, Webhook, Valid Permissions |
| TikTok | Client Key, Client Secret, App Approval |
| YouTube | Google OAuth Client ID, Client Secret, API Key |
| Client ID, Client Secret, OAuth Scopes | |
| X (Twitter) | API Key, API Secret, Access Level |
| Google Business Profile | OAuth Client, Approved Scopes |
📌 Important:
-
If API credentials are missing or invalid, the network may not appear in the User Dashboard.
-
Some networks will only appear after successful API configuration.
Step 2 (MOST IMPORTANT): Enable Social Networks in Plan Permissions
Go to:
For each Plan:
-
Click Edit
-
Open the Permissions tab
-
Enable the required social networks:
-
Facebook
-
Instagram
-
TikTok
-
YouTube
-
LinkedIn
-
Threads, etc.
-
-
Save the Plan
📌 If a social network is not enabled in the Plan, users on that plan will never see it, even if Admin + API are configured correctly.
Step 3: Re-login User Account
After completing Admin + API + Plan configuration:
-
Log out from the user account
-
Log in again
-
Go to Add Channels
✅ All enabled and permitted social networks should now be visible.
⚠️ Important Notes
-
Admin → API Integration = system-level configuration
-
Plan Permissions = user-level access control
-
Both are mandatory
-
This behavior is by design in Stackposts v9
-
X (Unofficial) appears by default because it does not require official API approval
Quick check
- The save or publish action completes without an error.
- The visible status, preview, or connected account matches the change.
- If the result differs, capture the exact message and review the troubleshooting guidance before retrying.