Getting Started with Social OS
The Getting Started domain tests whether you can build and govern a workspace before anyone publishes a single post. Questions here are structural: how organizations, social accounts, users and permissions fit together, and how the Social OS modules - Perch, Nest, Parliament and Lumen by Talkwalker - sit on one shared foundation.
What "Social OS" means
- An operating system for social: publishing, customer care, advocacy, listening and AI running on shared account connections, shared assets and shared permissions.
- The modules are separate surfaces over the same data. A mention surfaced in Lumen can be handled in Nest; a post approved in Perch can be amplified in Parliament.
- Because the layers are shared, a mistake at setup (wrong account, missing permission) propagates everywhere downstream.
Structure and access
- The organization is the top-level container. Social networks are connected to the organization, not to an individual's login.
- Organization roles (admin-level) and per-social-account permissions (view, edit, message, full) are separate controls. Someone can hold an admin role and still be read-only on a specific profile.
- Approval workflows, default UTM parameters and the content library are configured once at organization level and inherited by teams.
Connecting and securing
- Connect business pages through native authentication. Invite people as users rather than sharing a page password - shared credentials destroy attribution and audit trails.
- Enable two-factor or SSO where available, and offboard by removing user access, not by rotating the page password.
Worked example
An agency onboards a café chain: three networks (Instagram, Facebook, X), two publishers, one compliance reviewer. Correct order: (1) create the organization; (2) connect the client's business accounts with the client's own credentials; (3) invite publishers with edit rights; (4) invite the reviewer with approval rights; (5) switch on a Perch approval step; (6) standardise UTMs. Reasoning: approvals and permissions are inherited, so they must exist before content is loaded - retrofitting an approval step leaves already-scheduled posts ungoverned.
Traps
- Connecting a personal profile when only a business page was authorised.
- Confusing organization admin rights with per-account message permissions.
- Skipping UTM defaults; retro-tagging breaks reporting continuity.
- Assuming Lumen sees your connected accounts' data - listening coverage depends on source, not connection.