Documentation

Everything you need to run your agency delivery loop in Markt OS.

1. Getting started

1. Create your agency account. The first user becomes the organization owner.
2. Add your first client workspace from the dashboard or Clients page.
3. Fill the client context questionnaire so strategy and AI stay grounded in facts.
4. Create a campaign, then create content linked to it.
5. Connect at least one social channel under Settings, then schedule from the calendar.

2. Client workspaces

Each client is fully isolated: campaigns, media, approvals, channels and reports live inside their own workspace. Team members only see workspaces assigned to them.

3. Content production

Write one master concept, pick target platforms, then use AI adapt to generate platform-native variants. Every variant keeps its own version history and constraint checks (length, hashtags).

4. Approvals

Send any item for internal review or client review. Client links are tokenized, expiring pages that need no login. Comments attach to the exact item and every decision is recorded in the audit trail.

5. Scheduling and publishing

Open a client calendar, drag posts between days to reschedule. Publishing jobs are queued with retries and idempotency keys so a retry never duplicates a post. Failed posts surface clearly instead of pretending.

6. Media hub

Drag and drop files to upload. Files are scanned, then stored in internal storage; the database keeps a link to each file. Share links support expiry, passwords and download limits.

7. Settings

• Organization: agency details, company logo, SMTP and POP3 mail servers with connection tests.
• AI providers: bring your own OpenAI, Anthropic, Google or custom endpoint keys.
• Social channels: connect accounts with your own API credentials.
• Security: optional two-factor authentication with QR code setup.
• Webhooks: signed event delivery to external systems.

8. Roles

Owner, security administrator, agency administrator, account manager, strategist, content manager, analyst, contributor, client reviewer, read-only. Permissions are enforced server-side on every request.