PromptPress billing combines subscription plans and credit-based usage. Keep both healthy to avoid disruption during high-volume publishing periods.
How Billing Works
Billing is scoped to the active workspace context and includes:
- Plan access: determines which features and management screens are available.
- Credits: consumed by generation-heavy operations.
- Account context: personal and team billing are handled in different account scopes.
Personal vs Team Billing
- Personal account billing applies to an individual workspace.
- Team account billing applies to a shared workspace and should be managed by designated owners/admins.
Always confirm the active workspace before checkout or plan changes.
Step-by-Step: Validate Correct Billing Context
- Open billing from the workspace where work is blocked.
- Confirm the workspace slug/account name in the header.
- Confirm current plan and role permissions in that workspace.
- Run checkout or plan change from that same page context.
Credits and Usage
Credits are typically consumed by AI generation workflows.
Examples include:
- PromptPress generation tasks.
- Studio workflow runs.
- Other metered automation operations tied to your plan.
If credits are depleted, generation surfaces can remain visible but execution is blocked until credits are restored.
Step-by-Step: Recover from Zero Credits
- Open billing in the affected workspace.
- Add credits or upgrade the plan.
- Return to the blocked module (PromptPress or Studio).
- Retry the exact failed action.
- Confirm run success and document the incident.
Recommended Billing Setup
- Assign a primary billing owner and a backup owner.
- Document your internal monthly credit budget.
- Review usage weekly during active publishing periods.
- Keep payment method and invoice recipients current.
Feature Access and Plan Gating
Plan tier and role both influence access.
Common patterns:
- Advanced content and automation tools may require higher tiers.
- Management pages for prompts, models, and admin operations may be restricted.
- Team-level controls depend on membership role plus plan entitlements.
Common Failure Modes
- Checkout started in the wrong workspace context.
- Plan upgraded but user expects access in a different account.
- Credits exhausted during campaign windows.
- Billing owner left the team without handoff.
Billing Operations Checklist
Before major campaign or launch windows:
- Active subscription confirmed.
- Credit headroom confirmed.
- Payment method valid.
- Billing owners reachable.
- Escalation path documented.
Incident Response
If billing-gated features stop working:
- Confirm current workspace slug/context.
- Confirm active plan state.
- Confirm available credits.
- Confirm role permissions for the affected user.
- Escalate with account ID and UTC timestamps.