Choose the correct channel

Sign-in or permission

Contact your organization administrator or the person responsible for your Alæc environment.

Unexpected Studio behaviour

Use Report a bug from the profile Help menu when that command is available; otherwise, follow your organization’s established support channel.

Sensitive information shared incorrectly

Immediately follow your organization’s security or incident procedure. A bug report does not replace that procedure.

Useful information to provide

• The date, approximate time, and your time zone.
• The page or feature in use and the action performed immediately before the problem.
• The expected result and what actually happened.
• The exact error message without confidential information.
• The browser, device type, and Studio version when known.
• Short steps that reproduce the problem.
• An anonymized screenshot only when it reveals no information you are not authorized to share.

Never include

• Passwords, verification codes, or access tokens.
• Cookies, browser-storage contents, or authorization headers.
• Secret keys, sensitive technical identifiers, or confidential configuration.
• Client documents, personal information, or complete project content when an anonymized example is sufficient.

Structure a reproducible report

1. 01

   Give the report a short title describing the feature and observed behaviour.

2. 02

   State the environment, language, browser, and device type.

3. 03

   Number the exact actions performed before the problem.

4. 04

   Clearly separate the expected result from the actual result.

5. 05

   Copy the exact error message after removing sensitive information.

6. 06

   State whether the issue is constant, intermittent, or limited to a project, account, or organization.

Practical guidance

Use a concise reproduction with the affected page, language, action and exact visible error. Explain whether the action failed completely or left a partial result. If a screenshot is useful, remove account details, client material and unrelated notifications before submitting it through the approved reporting channel.

Advanced tips

For intermittent issues, add the last successful attempt and the condition that changed, such as selected project or file type. Keep subsequent observations with the same report so the sequence remains understandable without exposing complete conversation histories.