Documentation

Documentation

Everything you need to install, configure, and run WISKO STUDIO -- organized by module.

Getting Started

A quick orientation to WISKO STUDIO: brands, roles, and where each module lives in the dashboard, before you touch a single setting.

Installation

How to install and activate the WISKO STUDIO plugin, and what happens automatically on first activation -- database tables, default roles, and capabilities.

Brands

Creating brand profiles, setting brand status, and understanding how every other module scopes its data to a brand.

Users

Inviting team members, assigning them to brands, and managing the six built-in roles without ever sharing a login.

Content

Drafting, reviewing, and approving content through the Draft, Pending Review, Approved, Published status path.

Publishing

Connecting destinations, queuing content for release, and reading retries and publishing history.

Social

Composing and scheduling social posts across connected platforms from the same publishing queue as everything else.

Notifications

How in-app notifications work, what triggers them, and how to manage your read/unread history.

Workflow

Assignments, due dates, priorities, and the Approve / Reject / Request Changes cycle that ties every module together.

API Coming Soon

A full REST API reference for building custom integrations against your own WISKO STUDIO installation.

Questions

Documentation FAQ

Where do I start after installing the plugin?

Activate the plugin, create your first brand, then invite your team. The dashboard will guide you toward Content once a brand exists.

Do I need this theme to use WISKO STUDIO?

No. WISKO STUDIO runs entirely inside wp-admin regardless of which theme is active. This theme exists to give the platform a public-facing marketing site.

Is there a REST API?

Yes -- WISKO STUDIO registers REST routes for every module today. A public, documented API reference for building your own integrations is on the roadmap.

How do brand permissions work?

Each of the six roles is scoped per brand, not account-wide -- someone can be a Manager on one brand and have no access at all to another.

Still need help?

Full step-by-step guides are on the roadmap. Until then, our team is happy to answer questions directly.

Contact support