# Get support

Start with this documentation for setup instructions, project configuration, authoring guidance, and CLI reference. If you need more help, choose a private or public channel based on the information you need to share.

## Private support

### Product support

Email support@devjetsoftware.com when your question involves private installation details, activation, licensing, diagnostic logs, or source code. In the Delphi IDE, you can also choose DocInsight > Help > Email Support.

### License and orders

Use the secure FastSpring customer portal to manage purchases, invoices, payment details, and renewals. Open the portal from the account link in your order or renewal email. You may be asked to verify the email address used for the purchase.

For purchase and order questions, email sales@devjetsoftware.com.

## Public channels

Use the DocInsight issue tracker to report bugs or documentation problems, or to request features that can be discussed publicly.

Use the DocInsight community forum to ask public questions, share workflows, and discuss product usage.

Warning

Do not post license keys, private source code, confidential logs, or customer data in public channels.

## Report a problem

When reporting a problem, include:

- The DocInsight version.

- The Delphi version, when the problem involves Delphi source or the IDE extension.

- The command you ran and relevant diagnostic output.

- A diagnostic log when available.

Use the issue tracker only when this information can be shared publicly. Otherwise, send the report to product support. In the Delphi IDE, you can also choose DocInsight > Help > Report Issue.

## Collect diagnostic logs

Create a CLI log file while reproducing the problem:

shell

    docinsight check --log-file logs/docinsight.log --log-level debug

For an IDE extension problem, choose DocInsight > Tools > Debug Logging, reproduce the problem, and then choose DocInsight > Tools > Show Logs.

Logs can contain local paths, project details, command-line arguments, source excerpts, or documentation content. Review them and remove proprietary source, customer data, credentials, license keys, and other private information before sharing them.