Authenticated customers
Use the portal feature-request flow when you have tenant access. That keeps tenant context, user identity, and product area attached to the request.
Feature Requests
Send product feedback with the context needed to act.
TvRMM tracks feature requests against tenant scope, platform support, endpoint type, role gates, and operational workflows so the public roadmap does not overpromise partial support.
Public questions
Use the public contact form for pre-signup questions, platform-fit requests, security-review questions, or feedback when you cannot access the portal.
What to include
Name the workflow, endpoint operating system, affected organization, expected outcome, current blocker, and whether the request affects patching, scripts, terminal, logs, performance, packages, reboot, or guest visibility.
How requests are evaluated
Requests are checked for hosted SaaS fit, tenant isolation, role gates, endpoint parity, docs impact, tests, and whether unsupported lanes need explicit UI copy.
Good feature-request examples
- Specific platform gap: "Add package inventory support for OpenMediaVault hosts enrolled through the NAS lane."
- Workflow gap: "Bulk archive endpoints should preserve the same uninstall and cert-revocation behavior as single-endpoint delete."
- Docs gap: "The install guide should explain why Proxmox VE guest rows need a parent host or linked in-guest agent."