Set up Postly
Confirm your account, organization, workspace, timezone, and who needs access before campaigns begin.
Getting Started
Postly Starter Pack
Understand workspaces, team seats, and shared limits. Set up one brand or client, invite the right people, and publish your first post.
Understand your workspace and team
Start with one brand or client. You can add accounts, workspaces, and collaborators as you need them within your plan allowances.
What is the difference between a workspace, a team seat, and a social account?
A workspace is a separate area for a brand or client, with its own connected accounts, posts, and publishing calendar. A team seat is a person you invite to collaborate. A social account, also called a publishing channel, is a connected destination such as a Facebook Page or YouTube channel. For example, one client workspace could contain five social accounts and have three team members working on its posts.
Does each team member get a separate social-account allowance?
No. Social-account capacity is shared across the plan owner’s workspaces. Inviting a team member does not add social-account slots or give that person a separate copy of the plan. Team seats control how many people can collaborate; their roles and workspace access control what they can do. Check the plan owner’s billing page for the account’s actual allowances.
Are my social accounts divided equally between team members?
No. Social-account slots are not automatically divided between people. You choose which accounts to connect in each workspace and which teammates can work there. Several teammates can collaborate on the same connected accounts within their permissions; a seat does not reserve a fixed share of the social-account allowance.
How would I use a plan showing 500 social accounts, 200 seats, and 200 workspaces?
Those are three separate capacities, not 500 social accounts for each of 200 people. For example, ten client workspaces with five social accounts each use 50 of the 500 social-account slots and ten of the 200 workspaces. Invite collaborators to the relevant workspaces and assign their roles. You do not need to use every seat or workspace. This is an illustrative example; use the allowances displayed on your own billing page.
Can a team member see every workspace or manage billing?
An Admin or Editor works within assigned workspace access and permissions. Owner is different: it grants full access to the invited account, including billing and all its workspaces. Choose Admin or Editor for a client or teammate who should only work in selected workspaces, and review permissions before sending the invitation.
How do I get started without using all my seats or workspaces?
Start with one workspace for your business or first client. Confirm its timezone, connect one social account, and prepare a draft. Invite only the people who need access and review their roles. Schedule or publish the reviewed post, then check its delivery result. Add more workspaces, accounts, and teammates as you need them within your plan allowances.
Your first-post checklist
- Check the plan owner's billing page for social-account, team-seat, and workspace allowances. These are separate capacities.
- Choose one workspace for your business or first client. Confirm its name and publishing timezone before connecting an account.
- Connect one social account and confirm the selected page, profile, or channel belongs to the intended brand.
- Invite collaborators if needed. Review workspace access and roles; Owner includes billing and all the account's workspaces. Choose team roles.
- Create a draft, review the text and media for the selected destination, and confirm the date, time, and timezone before scheduling or publishing.
- Check the delivery result for each destination. Scheduled does not mean published. If the result is uncertain, check the destination and post status before retrying to avoid duplicates. Check publishing outcomes.
Your first Postly workflow
Connect → Create → Customize → Schedule → Publish → Measure
Connect your channels
Connect the pages, profiles, channels, and supported blog destinations you plan to publish to. Reconnect expired permissions from the same area.
Create your first post
Open the composer, choose destination accounts, add text and media, and keep the first campaign simple enough to verify easily.
Customize by platform
Start with one campaign, then adjust the resulting text, media, format, and settings for each network before it goes live.
Schedule or publish
Publish now, schedule a date and time, or save a draft. Use the calendar and publishing notifications to confirm what happens next.
If setup does not look right
- Wrong page or channel connected? Check the provider account and destination you authorized. Follow the connection guide.
- Missing workspace? Check the workspace picker and ask the person who invited you to confirm your access. Find and switch workspaces.
- Cannot perform an action? Ask an Owner or authorized Admin to check your roles and permissions, then check the workspace owner's plan allowances. Review team access.
Choose what to learn next
Each path introduces the workflow, then sends you to the existing detailed guide or product page.
Content creation
Build posts with reusable media and adapt the final campaign for each destination.
Publishing
Choose the right workflow for one post, a calendar, a CSV batch, or evergreen content.
Collaboration
Organize workspaces, invite teammates, define permissions, and route posts through review.
Engagement and CRM
Bring supported conversations and contacts into one operating flow for replies and follow-up.
Analytics
Review post and channel performance, compare outcomes, and decide what to publish next.
Ecommerce
Use the ecommerce workflows that are currently available for product-led content distribution.
Email and owned channels
Extend distribution beyond social channels with supported email and Bio Page workflows.
Advanced and developer
Connect Postly to apps, automations, and scoped AI-agent workflows using the public developer surfaces.
Need a specific answer?
Use Docs for detailed setup and developer guidance, or FAQ for concise answers and troubleshooting.