How to Submit a Feature Request (Guidelines)

Feature Requests — Guidelines

We actively read every request here. High-quality, well-explained requests have a real impact on the roadmap.

What makes a request actionable?

1. Lead with the problem, not the solution. Write "I can't do X without manually doing Y every time" before proposing a fix. Understanding the pain point first helps us find the right solution.
2. Be specific. "Better permissions" is hard to act on. "Allow per-module permission granularity so an Editor can manage Blog posts but not CRM contacts" is something we can actually build.
3. Describe your use case. Real-world context (client project, SaaS, multi-tenant app) helps us prioritise correctly.
4. One request per topic. Multiple requests in one post get lost. Create separate topics so each can be voted on independently.

How requests get prioritised

• Community upvotes (likes on the topic) signal demand
• We tag popular requests with a milestone when they're planned
• Requests that align with the current roadmap move faster

Check the GitHub issues too — some features are tracked there directly.

— The Lara Dashboard Team