Members with feedback access and permitted administrators

Feedback and report instructions

Record product needs and maintain reviewed report guidance.

What to do

Open Feedback and describe the real problem, present workaround, frequency and benefit. Avoid credentials or unnecessary personal information.
Review the recorded status and decision explanation. A request records a need; it is not a delivery contract.
Administrators can review report instruction versions through the available report configuration screen. Read the current text before proposing a change.
Save a new instruction version with a reason. When restoring older wording, the system records a new version rather than erasing intervening history.
Feedback remains private within your organization.

Before you continue

Feedback remains private within your organization.

Feedback is visible to authorized members of your organization. This view does not publish to customers or the public. A planned request does not promise a delivery date.

Retry repeats the same submission. A deliberately separate request remains separate, even when its text is identical.

This tab keeps only a random recovery key when browser storage is available. Feedback text is not stored in the browser after reload. Check the outcome before starting another request.

Stopping does not undo saved feedback. Check the list before starting a separate request.

Questions and troubleshooting

Does a planned status guarantee implementation?

No. Prioritization and decisions remain explicit.

Can I add custom scripts to a report template?

No. Report instructions are reviewed configuration, not a place to run customer-supplied code.

Send feedback to the team

Saving a feature request keeps it internal. Only Send submits the message you have explicitly reviewed to the recipient shown in the app.

Write your message
Open your feature request and its sending section. Enter a subject and message separately. The internal proposal is not automatically copied into the message.
Review the preview
Check the recipient, sender, message and displayed references to your feature request. Select the checkbox to confirm that this exact preview should be sent.
Send and check the status
Select Send. View the current status and previous attempts in the sending history. Each workspace can start at most ten new sends per hour.

What does outgoing server acceptance mean?

The outgoing mail server accepted the message. This does not confirm arrival in the recipient’s inbox or that anyone has read it.

The connection dropped or the outcome is unclear

Check the sending status and history first. Use the offered status check or recovery option. Do not start a new send or copy the message into a new attempt while the outcome is unclear.

The feature request changed

Create and review a new preview, then confirm it again. Approval of an older version does not apply to the changed version.

The hourly limit was reached

This message was not queued for sending. Wait one hour, then try again.