Feature Request

Most Yardi feature request tickets resolve through an existing workaround, an admin configuration change, or confirmation that the requested change is not supported by Yardi.

• Check for an existing template or workaround first — some layout or workflow limitations in Yardi (e.g., document address formatting) are known and have pre-built email templates or manual steps already in place. Review available templates in the system before submitting a new request.
• Check your spam folder if you are expecting an invitation to an external platform (e.g., a social media business account). Invitations can be re-sent by an admin if they do not arrive.
• Contact an admin to adjust applicant-facing settings (admin only) — options such as disabling self-selection of rentable items or modifying what applicants can access during the application process require a backend configuration change in Yardi.
• Request a spreadsheet or report modification (admin only) — if a standard Yardi report or spreadsheet is missing a data field (such as parking), an admin can update the template internally without a Yardi support case.
• Confirm with Yardi support whether the change is configurable (admin only) — some layout and formatting requests are not supported by Yardi at all. If a similar request has been submitted before, check past resolution notes before escalating to Yardi, as the answer may already be documented.

If none of these solve it, file a ticket and include: the specific Yardi screen or report name involved, a description of the current vs. desired behavior, whether applicants or staff are affected, and any error messages or Yardi module names relevant to the request. This helps the admin team assess whether a workaround, configuration change, or Yardi support case is needed.