Search the canon
Start with reviewed articles mapped to Probe products, roles, and support paths.

Start with reviewed product answers, move into guided troubleshooting, and escalate with page context when an article cannot finish the job.
Billing help should be clear, account-aware, and careful. Public articles can explain how plans, credits, and billing concepts work at a high level...
...ewing a different workspace or plan context. ## Related articles Read Plans, credits, and billing for the broader account billing model. ## Escalation guidance For credit questions, include the approximate time, action name, product surf...
...Short answer Good support context explains the problem without exposing secrets, private billing data, access tokens, or unrelated user data. ## When to use this Use this article before sharing screenshots, logs, AI prompts, payment con...
...ort answer Subscription and invoice questions need account context, plan context, and the billing surface where the issue appeared. ## When to use this Use this article before escalating a payment, invoice, plan, or subscription question...
...p with login, reset, or account recovery. - Signed-in users may need profile, privacy, or billing help. - Workspace members may need an internal admin to change permissions. - Admins may need support for workspace, billing, or security c...
...prompts produce vague help. Sensitive prompts can create privacy risk. If a task involves billing, security, or account access, keep the context minimal and safe. ## Related articles Read Data controls and trust before sharing private wo...
...Community discussion is good for general learning. Private support is better for account, billing, security, workspace, or user-specific issues. ## When to use this Use this article before posting a question that might include private or...
...ize ProDrive files with Projects? ## Use private support instead Do not use community for billing, account access, private workspace data, security incidents, or anything involving payment details.
...What actually happened. 5. Any error message or request ID. 6. Whether the issue affects billing, account access, security, or a workspace. ## When to use community Use community for non-sensitive how-to questions, examples, and learnin...
...ugh Probe. ## Requirements Use public examples for learning. Do not use private customer, billing, or workspace data as training material. ## Suggested path Start with What is Probe, then Navigation basics, then the relevant collection....
...ormation requires sign-in. Public profile content should not include private credentials, billing details, or support-only information. ## What to review Check your display name, username, avatar, bio, links, products, programs, and any...
...en to use this Use this article when Prodigi gives an answer that affects public content, billing, permissions, data, or operational decisions. ## Requirements Keep sensitive details out of prompts unless the surface explicitly needs the...
...Center mental model The Help Center starts with practical questions like account access, billing, agents, ProTools, privacy, and troubleshooting. Underneath that practical structure, each article also maps to Probe's deeper taxonomy. Th...
...t. 2. **Route:** It can help users find the right area of the platform, such as ProTools, billing, privacy, or account help. 3. **Triage:** When Help Center content does not resolve an issue, Prodigi should collect context before a suppo...
Start with reviewed articles mapped to Probe products, roles, and support paths.
When an answer needs context, open triage from the page you are already reading.
Support tickets carry attempted articles, category, severity, and safe diagnostics.
Collections follow Probe product surfaces, account states, trust needs, and support workflows.
Probe
Understand what Probe is, how the platform is organized, and what to do first.
Probers
Sign-in, profiles, roles, workspaces, account security, and identity controls.
Prosperity
Plans, credits, billing states, subscriptions, and payment expectations.
Power
How Prodigi and specialist agents route work, answer questions, and execute tasks.
Product
Studios, managers, ProDrive, ProBook, Pinboard, TierList, and workflow surfaces.
Programs
Profiles, posts, products, programs, publishing, and creator economy workflows.
Power
Data controls, verification, trust, security, permissions, and provider transparency.
Plan
Fix common access, upload, search, billing, and AI response issues.
Power
API, model providers, connected apps, and integration boundaries.
Programs
Learning paths, public examples, community support, and non-sensitive questions.
Understand how to browse Probe through discovery, rankings, profiles, products, and public content.
Learn how Probe is organized across global pages, Studios, Managers, and contextual panels.
Understand Probe as an AI-powered operating system for creating, organizing, and owning outcomes.
Understand how account, identity, and role questions should be routed in Probe Help.
Understand how your Probe profile represents you across public identity, creator work, and professional context.
Learn how account roles, workspace context, and admin surfaces affect what you can see or change.
Prodigi support
Open Prodigi for interactive help, or start with the troubleshooting path.