The Suite
Fourteen modules. One login per brand.
Every brand (tenant) gets its own accounts with roles: owner, editor, viewer. The operator manages tenants, users and API keys centrally.
The modules
Strategy
Strategy & goals
Business goals, positioning, tone of voice, KPIs, do's & don'ts per campaign year.
Audiences
Personas with pains/gains, languages, platforms and weight.
Ad objectives
Objectives per channel in platform naming, KPI target, budget.
Topics
Content pillars with kind, keywords, source reference and weight.
Marketing
Dashboard
KPIs, status distribution, next 14 days, channel overview.
Calendar
Monthly grid with filters, post detail with rescheduling and status transitions.
Approval queue
Review with slide preview, caption editing, approve/skip.
Channels
Platform, language, handle, posting windows, cadence, auto-publish.
Templates
Formats, slide ranges, versions, default CTA per template.
Media
Asset pool with approval, © attribution, tags and AI labeling.
Music
License-safe tracks with mood and default mapping.
CTAs
Calls to action per brand: text, target URL, voiceover line.
Overview API: the status inside your admin
Every tenant has an API key. Any external system (your platform admin, a client dashboard) uses it to fetch the current social status as JSON: KPIs, channels, next posts, recently published, log. The functions stay in the suite; the plugin shows the status.
- Read-only: the plugin can't change anything. Functions live in the suite only.
- Integrate server-side: the API key belongs in your server environment, not the browser.
- Rotate keys any time in the operator admin. Old integrations lose access instantly.
- Already running in the admins of studyonline.now, ki-ins-unternehmen.de and jobs-in-wiesbaden.de.
One GET, one bearer token:
GET https://social-marketingsuite.com/api/v1/overview
Authorization: Bearer smk_...
→ { client, kpis: { posts_total, review_pending, ... },
channels: [...], next_posts: [...], recent_published: [...] }Tenants, roles, operator
Every brand is its own tenant: its own strategy, channels, posts and users. Roles govern access: owners and editors write, viewers read. The operator creates tenants, manages accounts, rotates API keys and can open any suite in the tenant's context. All data lives in one central Baserow database with row-level client separation.
Request access