All ideas

Show suggestions and descriptions for standard metadata keys in object renderer sets

Admins want to see available standard metadata keys with short descriptions when configuring object renderer sets, so they can work independently without needing to consult support or documentation for every configuration step. Problem / Pain: When configuring object renderer sets, admins need to know which standard metadata keys are available and what each one does. This information is not surfaced in the interface itself, and the existing documentation does not provide enough detail to make confident, independent decisions. As a result, admins frequently need to contact support or a consultant to find out which key to use, slowing down configuration work and creating unnecessary dependencies. Impact / Benefit: Showing available standard metadata keys as suggestions, along with short descriptions explaining what each key controls, would allow admins to configure object renderer sets independently and with confidence. It would reduce the need for external support, speed up configuration work, and lower the barrier for customers who want to manage their own setup. Example use case: An admin is setting up a new object renderer set and needs to enter a metadata key. Without any suggestions or context in the interface, they do not know which keys are available or what they affect. With inline suggestions and descriptions, they can browse the available keys, read a short explanation for each, and select the right one without opening a ticket or calling a consultant. Idea source: Internal suggestion Voting note: Vote for this idea if this need is relevant to you as well.