System Overview

PromptPress is a multi-tenant content platform for teams that need to plan, create, review, and publish faster without losing editorial control.

Who This Is For

This documentation is for:

• Editorial teams launching or scaling a publication.
• Operators managing workflows, access, and billing.
• Team admins responsible for publishing quality and safety.

Platform Areas

1. Workspace and Access

Your workspace is the boundary for people, permissions, content, and billing.

Core capabilities:

• Team workspace setup and member invitations.
• Role-based access for owners, admins, and members.
• Account-scoped data and route access.

2. Content and Publishing

PromptPress offers multiple surfaces for different stages of work:

• Studio (Article Studio): launch article workflows and manual drafts.
• PromptPress: generate and refine text, images, and video.
• ContentVault: manage drafts, review, and published content.
• ReleaseDeck: review campaign artifacts before final publish.

3. Workflows, Campaigns, and Agents

Automation is built around reusable workflow definitions:

• Campaigns: plan and track ongoing publishing initiatives.
• Workflows: define steps, transitions, and run lifecycle behavior.
• AgentBase: execute agents and inspect recent execution history.
• Agent Forge: future agent creation flow surfaced from AgentBase. The current Add Agent action shows a coming-soon dialog.
• PromptSpace: manage reusable prompts and model sources through Prompt Center and ModelSource.

Model defaults are workspace-scoped. PromptPress stores them in accounts.public_data.ai_defaults; the canonical model catalog is prompt_models.

4. Site and Delivery

Site controls are separated from content authoring:

• Site Settings: branding, domain, language, and tenant configuration.
• Site Builder: templates, blocks, navigation, and publish-to-live flow.
• Advertiser Portal: advertiser-side campaign setup, creative upload, preview, and same-origin article/category browsing on the advertiser host.
• Commerce: product catalog, orders, and storefront management.
• Site Modes: news, ecommerce, and hybrid.

The advertiser portal uses the shared i18n stack, so the header language switcher can toggle English and Nepali while keeping the current route and host context intact.

5. Billing and Usage

Billing controls plan access and metered operations:

• Personal and team billing flows.
• Credit-based usage for generation-heavy operations.
• Plan-based feature availability.

How Work Usually Flows

1. Create workspace and assign roles.
2. Configure personas, guard rails, and categories.
3. Create or update workflows.
4. Launch campaigns and workflow runs.
5. Review outputs in Studio, ContentVault, or ReleaseDeck.
6. Publish approved content.
7. Update site presentation in Site Builder.
8. Monitor credits, plan status, and team activity.

Important First-Time Journeys

If you are starting fresh, prioritize these journeys in order:

1. Workspace setup and role assignment.
2. First draft to publish in PromptPress + ContentVault.
3. First campaign workflow run in Studio + ReleaseDeck.
4. First site update and publish in Site Builder.
5. Billing and credit recovery drill.

Plan and Role Gating

Some areas are intentionally gated by plan and role.

Common examples:

• Advanced creation and management tools are often Pro or Enterprise only.
• Prompt and model management screens can be admin-restricted.
• Billing and membership operations are limited to authorized roles.

Read This Next

1. Getting Started
2. Workspaces and Roles
3. Content Creation
4. Workflows and Agents
5. Site Builder
6. Billing and Plans