Login, reset, and verification come first
If access itself is failing, do not over-diagnose a Studio, profile, or publishing bug yet. Start with the auth guide and recovery paths first.
Troubleshooting help
When something feels broken, the fastest fix usually starts with diagnosing the right kind of problem.
Use this page when you need shorter, support-oriented guidance for account entry issues, context confusion, publishing blockers, incomplete setup, permissions problems, or the point where a clean bug report becomes the right move.
Best first move
Name the failure clearly
Broken, blocked, and unclear are not the same thing. The faster you label the problem, the faster the right fix shows up.
Most common false alarm
Permission or context confusion
A lot of apparent product failures are actually caused by the wrong active context, incomplete setup, or missing collaboration permissions.
Escalate when
A route is repeatably broken
If the same steps fail consistently and the issue is not explained by access, context, or settings, it is time to report the problem clearly.
Start here
First checks before you spiral
Troubleshooting works better when you slow the situation down, label the failure clearly, and rule out the most common context mistakes first.
Ask whether the problem is broken, blocked, or just unclear. Those three paths have different fixes.
Re-open the exact route you intended to use instead of guessing from memory or following an outdated tab.
Check whether you are signed in, in the right account, and in the right personal or Group context before assuming the product failed.
Reduce the problem to one sentence. If you cannot describe the failure clearly, start with the auth or account guides first.
Access
Account access and recovery issues
If you cannot enter the account consistently, or can only reach part of the platform, start here before diagnosing deeper creator workflow surfaces.
Wrong email and wrong inbox cause a lot of panic
Many access problems feel severe until you realize the account email, reset inbox, or verification message path was simply not the one you thought it was.
Partial access is still a useful clue
If some features work and others do not, the issue may be permissions, setup state, or workflow context rather than a total account failure.
Workflow
Publishing and context problems
When uploads, Studio, or publishing actions feel blocked, the root cause is often context or permissions rather than a total platform failure.
Personal vs Group context changes what you can do
Publishing problems often come from being in the wrong context or expecting personal access to behave like Group access.
Missing permission is not always a bug
If a Group role or shared workflow blocks an action, the fix usually lives in permissions guidance rather than product failure reporting.
Studio confusion often starts upstream
When Studio feels wrong, check whether the real issue is authentication, onboarding state, or the route you expected to open.
Settings
Profile and account-settings confusion
Some problems feel technical when they are really profile maintenance, settings drift, or identity confusion that belongs in a guide instead of a support ticket.
Incomplete profile is usually a settings task
When the profile looks thin, inconsistent, or outdated, the answer usually lives in profile or account settings rather than troubleshooting a broken surface.
Identity confusion can feel like a feature issue
If the page feels wrong because personal and Group identity are blurred together, use profile and Groups help before filing a bug.
Notification or preference issues belong in settings
If the platform feels too noisy, too quiet, or out of sync with what you expect, the account settings guide is usually the better first stop.
Escalation
When to contact support or report a bug
Escalation works best when the problem is already described clearly enough that another person can follow it without guessing.
Report a bug when you can reproduce the same failure on the same route with the same steps.
Contact support when ownership, account identity, or a sensitive account question needs a human response instead of a pure product diagnosis.
Include the route, what you expected, what actually happened, and whether the issue is personal-only or also affects Group workflows.
Mention what you already checked so support does not have to restart from the most obvious first steps.
FAQ
Troubleshooting FAQ
These are the fast answers for the moment when a problem exists, but the category of the problem still feels uncertain.
Check whether the same route works after confirming login state, account identity, and personal-versus-Group context. If the failure disappears when context is corrected, it was not a product bug.
Use auth help when the core problem is account entry, recovery, or verification. Use troubleshooting help when the failure is broader or less clearly labeled.
Use account help when access already works and the question is really about settings, profile maintenance, passwords, email care, or preferences.
Include the route, the exact steps, what you expected, what happened instead, and whether the issue repeats consistently. Clear reproduction details save the most time.