For the complete documentation index, see llms.txt. This page is also available as Markdown.

Help and feedback

How to reach the Intangible team when something is wrong, and where the same flow lives inside a project.

The fastest way to reach a human at Intangible. Two surfaces – one on the homepage, one inside any project – that route to the same team.

Help menu open from the top-right help icon, showing the full ordered list - Welcome, First Steps, Keyboard Shortcuts, Updates, Report an issue, Request a feature, General feedback, Discord Community, Help Center

How to reach us

The help icon (question mark) lives in the top-right toolbar of every Intangible page – homepage, project editor, settings. Click it to open the help dropdown.

What's in the menu

Item
What it does

Welcome

The introductory pop-over for new users. Re-opens any time.

First Steps

Relaunches the guided onboarding tour. Useful when a teammate joins and you want to walk them through the basics again.

Keyboard Shortcuts

Opens the in-app shortcuts panel. Mirrors Keyboard shortcuts.

Updates

Opens studio.intangible.ai/updates – the public changelog.

Report an issue

Send a bug report directly to the support queue. Auto-attaches project context.

Request a feature

Submit a feature request. Read every one, ship some.

General feedback

Anything that doesn't fit a bug or feature request.

Discord Community

Jump to the Intangible Discord. Day-to-day questions, peer help, agency-network conversation.

Help Center

This documentation site.

The help menu is the canonical place to start. From inside a project the same menu is available, with the advantage that Report an issue auto-attaches the project ID and last-render context.

Report an issue

Report an issue (from the help menu, or the bug icon directly in the top-right toolbar) opens a structured report panel:

Report an Issue panel docked on the right side of the editor with a "Hey, found a bug?" greeting, a "What went wrong?" textarea, and two action buttons: Mark the bug and Record screen

Two actions support what you describe in the text field:

  • Mark the bug lets you click directly on the part of the UI that's broken so the report carries an annotated screenshot of the exact element.

  • Record screen captures a short video of the issue. Useful when the problem only shows up in a sequence of actions.

The bug icon in the top-right toolbar is a shortcut to the same panel – you don't have to open the help menu first.

Messages

The chat-bubble icon next to the help icon opens Messages, a real-time support thread with the Intangible team:

Messages panel open from the chat-bubble icon, showing recent message threads with team members, plus a "Send us a message" action and Home / Messages / Help / News tabs at the bottom

Use Messages for general support conversation, follow-ups on a previous thread, or quick clarification questions. Use Report an issue for structured bug reports where the team needs to reproduce.

What gets a fast response

Specific reproduction steps and recent context. The team can chase a vague "the visualizer didn't render right" report, but it takes a day; "In project Lambo Commercial, scene Manhattan Street, shot 3, Nano Banana Pro at 2K – the cop car keeps showing up despite the negative-prompt edit" takes ten minutes.

What helps:

  • The project name and a link if the project is shared

  • The exact scene and shot

  • The model and resolution

  • A screenshot of the unexpected behavior

  • What you expected to see instead

What doesn't help:

  • "It's broken"

  • "The AI is wrong"

  • A description of the entire week's work

Reporting a bug

Same form. Pick the Bug tag in the subject. The form auto-uploads a recent renders log so we can correlate against logs on our side.

Suggesting a feature

Same form again. Pick Feature request. We read every one. We don't ship every one.

Last updated

Was this helpful?