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.
...tions. - When a support issue should be treated as security-sensitive. ## Support routing Privacy, security, account ownership, and workspace access issues should not be routed to community support. They require authenticated context and...
Know what to include and what to hide when asking for help with account, billing, AI, or workspace issues.
Learn what belongs in community discussion and what should go through private support.
...ers need help 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, o...
...u need. ## Common problems Vague 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 an...
...lp 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. This keeps the system organiz...
...oute:** 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 support ticket...
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.