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.
- Keep internal requests private unless a separate authorized publication workflow explicitly approves public wording.
Before you continue
Public roadmap availability is separately controlled. Internal feedback is not automatically public.
Questions and troubleshooting
Does voting 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.